Hi,
> This is one of the commit which causes build fail. What's the plan to fix
> that ?
That commit wasn’t the issue it was the one after that. I’ve pushed a fix and
things should be back to normal.
Thanks,
Justin
Hi,
> This is one of the commit which causes build fail. What's the plan to fix
> that ?
Odd that change is working fine locally and I can’t see how that would break
the build i.e. adding new target that isn’t used.
I’ll look into it.
Thanks,
Justin
This is one of the commit which causes build fail. What's the plan to fix
that ?
2017-12-30 7:26 GMT+01:00 :
> Repository: flex-sdk
> Updated Branches:
> refs/heads/develop eeb68fcc4 -> 35214ffd3
>
>
> testing if we can make a release build target without running the
On 2/17/17, 5:54 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>2017-02-17 12:36 GMT+01:00 Harbs :
>
>> Simply specifying strings instead of the constants would be the most
>> efficient currently.
>>
>
>But that's what we try to avoid in order to support type safe code
>
>I pu
2017-02-17 12:36 GMT+01:00 Harbs :
> Simply specifying strings instead of the constants would be the most
> efficient currently.
>
But that's what we try to avoid in order to support type safe code
I put on my plate to break the class in 16 classes, but as I'm working on
other things I invite pe
he binding not doing its work.
>> Maybe
>>> some latest changes in binding caused this?
>>>
>>> Thanks
>>>
>>>
>>> 2017-02-16 11:03 GMT+01:00 Harbs :
>>>
>>>> 1. Go here: http://apacheflexbuild.cloudapp.net:80
>> bin/js-release/index.html <http://apacheflexbuild.
> cloudapp.net:8080/job/
> >> MDLExample/lastSuccessfulBuild/artifact/examples/flexjs/MDLExample/
> >> bin/js-release/index.html>
> >>
> >> 2. Click on Toggles
> >>
> >> Yo
On 2/16/17, 12:34 PM, "Harbs" wrote:
>When I’ve had these kinds of issues in my app, it’s because of minified
>renaming.
Yep, and there is code in one of the Binding classes that does some
trickery to look up a constant when minified. That code might need to be
used in this scenario.
-Alex
ttp://apacheflexbuild.cloudapp.net:8080/job/
>> MDLExample/lastSuccessfulBuild/artifact/examples/flexjs/MDLExample/
>> bin/js-release/index.html>
>>
>> 2. Click on Toggles
>>
>> You will see that the two IconToggles have no content. It
pache-flex-development.247.n4.nabble.com/FlexJS-MDL-release-build-broken-tp59537p59564.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
tml <http://apacheflexbuild.cloudapp.net:8080/job/
> MDLExample/lastSuccessfulBuild/artifact/examples/flexjs/MDLExample/
> bin/js-release/index.html>
>
> 2. Click on Toggles
>
> You will see that the two IconToggles have no content. It seems like the
> Material Design font is not beiing used fo
gt;
2. Click on Toggles
You will see that the two IconToggles have no content. It seems like the
Material Design font is not beiing used for some reason in the release build.
The same thing works in the debug build.
Harbs
Yeah. That seemed to work.
The problem in Flash Builder was that -remove-circulars was not being used.
Adding that argument fixed the release build.
Now comes the hard part of trying to make my app compile… ;-)
On Jul 18, 2016, at 10:40 PM, Alex Harui wrote:
> Looks like another spaces
Looks like another spaces-in-path problem. Can you try using folders
without spaces in the path?
Thanks,
-Alex
On 7/18/16, 12:38 PM, "Harbs" wrote:
>Here’s what I get from the DataBindingExample:
>Harbss-MacBook-Pro:DataBindingExample harbs$ ant
>Buildfile: /Users/harbs/Documents/Apache Flex
>
Here’s what I get from the DataBindingExample:
Harbss-MacBook-Pro:DataBindingExample harbs$ ant
Buildfile: /Users/harbs/Documents/Apache Flex
Dist/FlexJSNightly/examples/flexjs/DataBindingExample/build.xml
clean:
[delete] Deleting directory /Users/harbs/Documents/Apache Flex
Dist/FlexJSNightl
On 7/18/16, 12:12 PM, "Harbs" wrote:
>The JS is totally blank with the exception of the comment about Falcon.
Could you post your ant console output? There might be clues in there.
Thanks,
-Alex
The JS is totally blank with the exception of the comment about Falcon.
On Jul 18, 2016, at 10:07 PM, Alex Harui wrote:
>
>
> On 7/18/16, 12:38 AM, "Harbs" wrote:
>
>> I can’t seem to get a release build in FlaconJX to work.
>>
>> I was not sure if
On 7/18/16, 12:38 AM, "Harbs" wrote:
>I can’t seem to get a release build in FlaconJX to work.
>
>I was not sure if it’s my project, so I tried a couple of the examples
>and they do not seem to work either.
>
>I just created a new Flash Builder project for ToDoLi
I can’t seem to get a release build in FlaconJX to work.
I was not sure if it’s my project, so I tried a couple of the examples and they
do not seem to work either.
I just created a new Flash Builder project for ToDoListSampleApp. The debug
runs (although it looks messed up), but the release
= "hello";
In a release build, the setter wouldn't get called unless I changed it to
emit @expose.
- Josh
On May 28, 2016 9:35 PM, "Alex Harui" wrote:
> Is there a simple test case?
>
> On 5/28/16, 2:18 PM, "Josh Tynjala" wrote:
>
> >Does anyone k
Is there a simple test case?
On 5/28/16, 2:18 PM, "Josh Tynjala" wrote:
>Does anyone know a better solution to this?
>
>For some reason, static getters and setters weren't being called properly
>in a release build with ADVANCED_OPTIMIZATIONS. We included @export
Does anyone know a better solution to this?
For some reason, static getters and setters weren't being called properly
in a release build with ADVANCED_OPTIMIZATIONS. We included @export for the
static properties, which seems to work fine for non-static getters and
setters. However, for s
Thanks.
On Apr 13, 2016, at 11:34 PM, Alex Harui wrote:
>
>
> On 4/13/16, 1:08 PM, "Harbs" wrote:
>
>> I’m confused about the options here.
>>
>> If I’m reading this right, there’s 3 scenarios:
>> 1. Generate js-debug and js-release
>
> -debug=false
>
>> 2. Only generate js-debug
>
> -de
On Wed, Apr 13, 2016 at 1:34 PM, Alex Harui wrote:
>
>
> On 4/13/16, 1:08 PM, "Harbs" wrote:
>
> >I’m confused about the options here.
> >
> >If I’m reading this right, there’s 3 scenarios:
> >1. Generate js-debug and js-release
>
> -debug=false
>
> >2. Only generate js-debug
>
> -debug=true
>
>
On 4/13/16, 1:08 PM, "Harbs" wrote:
>I’m confused about the options here.
>
>If I’m reading this right, there’s 3 scenarios:
>1. Generate js-debug and js-release
-debug=false
>2. Only generate js-debug
-debug=true
>3. Only generate js-release from an existing js-debug.
-debug=false -skip-t
, at 10:08 PM, aha...@apache.org wrote:
> FalconJX now checks debug flag to determine whether to generate the release
> build via Google Closure Compiler. Also added -skip-transpile option so when
> debug==false, you can skip the debug-mode transpilation. By default, when
> debug
Hi Guys,
Im using flashbuilder to create a desktop air app with eccentric database
connection php.
How do i change the server settings after i make a build (exe/.air)
application?
Thanks
cation is installed
> > on
> > the devices tested. I can not say why
> >
> >
> >
> >
> > 2014-05-26 9:31 GMT+02:00 Swen van Zanten :
> >
> > > An AppStore release build is installable on your device but not
> > > executable. This is normal behavio
ed the app on the store and I do not have problems of submission.
>
>
> I can assure you that with the first option, the application is installed
> on
> the devices tested. I can not say why
>
>
>
>
> 2014-05-26 9:31 GMT+02:00 Swen van Zanten :
>
> > A
I released the app on the store and I do not have problems of submission.
I can assure you that with the first option, the application is installed on
the devices tested. I can not say why
2014-05-26 9:31 GMT+02:00 Swen van Zanten :
> An AppStore release build is installable on your dev
An AppStore release build is installable on your device but not executable.
This is normal behavior.
This kind of release build is only for app submission.
You can test the app with the second option.
If that one works... the first option will also on Apple's side.
Met vriendelijke groet
during submission to the store.
Any support and / or feed would be greatly appreciated
Il mercoledì 21 maggio 2014, Swen van Zanten ha scritto:
> If I understand you correctly..
> There are 2 options on the release build wizard.
> One being for creating an ipa for the AppStore and the
If I understand you correctly..
There are 2 options on the release build wizard.
One being for creating an ipa for the AppStore and the other for ad-hoc
(in-house) release.
The first option does not work on any device because it has not been submitted
and approved in the AppStore by Apple.
The
hello
some time ago my app in ios environment with certified appstore, created an
ipa file that was installed via itunes but did not execute on a test device.
Today the same app with the same production certificates on ios7.1.1 nstall
and run the app without difference with certificates of develop
Fixed and committed.
Should be good now.
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : samedi 22 février 2014 09:43
À : dev@flex.apache.org
Objet : RE: Mobile grid skin warnings while making a release build
> Looks pointless isn't i
di 22 février 2014 03:00
À : dev@flex.apache.org
Objet : Re: Mobile grid skin warnings while making a release build
On Feb 21, 2014 5:22 PM, "Justin Mclean" wrote:
>
> Hi,
>
> May or may not be a concern but just in case no one has noticed and it's
important.
>
On Feb 21, 2014 5:22 PM, "Justin Mclean" wrote:
>
> Hi,
>
> May or may not be a concern but just in case no one has noticed and it's
important.
>
> [asdoc]
/Users/justinmclean/Documents/ApacheFlex4.12.0/frameworks/projects/experimental_mobile/src/spark/skins/MobileGridSkin.as(44):
col: 19 Warning
Hi,
May or may not be a concern but just in case no one has noticed and it's
important.
[asdoc]
/Users/justinmclean/Documents/ApacheFlex4.12.0/frameworks/projects/experimental_mobile/src/spark/skins/MobileGridSkin.as(44):
col: 19 Warning: The constant was not initialized.
[asdoc]
[as
On 9/11/13 4:50 PM, "Alessandro Palombaro" wrote:
>Thanks Alex! Do you know why some of the swcs have their source
>attachments automatically setup correctly and some others don't? Is it FB
>doing its own thing or is there somewhere in the SDK these links are
>defined?
I have not found a way fo
Thanks Alex! Do you know why some of the swcs have their source
attachments automatically setup correctly and some others don't? Is it FB
doing its own thing or is there somewhere in the SDK these links are
defined?
On Wed, Sep 11, 2013 at 10:51 PM, Alex Harui wrote:
> You should be able to go
You should be able to go to Project Properties/Build Paths/Library Paths
Expand the SDK and you should see all SWCs, expand a SWC and you should be
able to set a source attachment for it.
On 9/11/13 1:31 AM, "Alessandro Palombaro" wrote:
>Does anyone know how to setup Flash Builder 4.6 to proper
Does anyone know how to setup Flash Builder 4.6 to properly jump to Flex
source files when hitting F3 (open declaration) on a class reference?
It seems I can jump to classes that existed in older versions (most of the
time it jumps to the wrong line in the class but still opens the source
file) bu
Hi,
Just tried in FB 4.6 (on OSX) with -advanced-telemetry and release build and
there's no issues, so it may be a FB 4.7 only issue.
Thanks,
Justin
Hi,
Although I tried to create the Release Build in Flash Builder 4.7, the
error occurred.
Compiler options: -advanced-telemetry
Best Regards,
[
https://issues.apache.org/jira/browse/FLEX-33451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik de Bruin resolved FLEX-33451.
--
Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0
> The release build due to
l to the DEV list ("ASDoc ant target
issues/solutions"), the release build runs fine and creates viable artefacts.
> The release build due to the Git migration is broken
>
>
> Key: FLEX-3
you are seeing wrt. TLF_HOME? I ran a
couple of 'ant release' and didn't get any TLF related errors or warnings...
> The release build due to the Git migration is broken
>
>
> Key: F
some minor issues with TLF_HOME.
> The release build due to the Git migration is broken
>
>
> Key: FLEX-33451
> URL: https://issues.apache.org/jira/browse/FLEX-33451
>
.. Tried against Apache Flex 4.9.1.
> Spark DataGrid skin produces Stack overflow in release build
>
>
> Key: FLEX-27585
> URL: https://issues.apache.org/jira/br
[
https://issues.apache.org/jira/browse/FLEX-27585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrill Zadra updated FLEX-27585:
Attachment: FLEX-27585.zip
> Spark DataGrid skin produces Stack overflow in release bu
[
https://issues.apache.org/jira/browse/FLEX-27585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrill Zadra updated FLEX-27585:
Assignee: Cyrill Zadra
> Spark DataGrid skin produces Stack overflow in release bu
ing in versions of AIR. AIR 3.7 should be out this week.
>> 4. There's a fair number of bug fixes that have been checked in.
>> 5. There's new experimental components for people to play with.
>> 6. Move to git have broken making a release and should be fixed and the
>> documentation updated.
>> 7. Need to fix CI as well as it did tell up when the release build was
>> broken.
>>
>> Thanks,
>> Justin
>
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
. AIR 3.7 should be out this week.
> 4. There's a fair number of bug fixes that have been checked in.
> 5. There's new experimental components for people to play with.
> 6. Move to git have broken making a release and should be fixed and the
> documentation updated.
&
eople to play with.
6. Move to git have broken making a release and should be fixed and the
documentation updated.
7. Need to fix CI as well as it did tell up when the release build was broken.
Thanks,
Justin
n.system.issuetabpanels:all-tabpanel ]
>
> Justin Mclean reassigned FLEX-33451:
>
>
> Assignee: (was: Justin Mclean)
>
>> The release build due to the Git migration is broken
>> --
[
https://issues.apache.org/jira/browse/FLEX-33451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean reassigned FLEX-33451:
Assignee: (was: Justin Mclean)
> The release build due to the Git migration
but need more testing.
Ant in the asdoc directory fails and I have no idea how to fix. This stops up
creating asdocs to include in the release. Can someone take a look at this?
> The release build due to the Git mi
HI,
The one minor down side is that it's now it harder to tell exactly where a SDK
was build from (no revision number n flex-describtion.xml). There would be a
branch with the same version number so it's a minor annoyance.
Justin
>Can any Git experts please comment if there an alternative to doing this this
>way.
If you have a moment, take a look at git describe as an idea. It basically
gives you the latest tag and a number of commits since then and a hash. Its not
a simple sequence, but see if it helps.
This one is ok
Hi,
When we were using SVN the SVN revision number was used in various places. This
needs to be a number (so hashes are out) and may need to be numerically
increasing ie current number bigger than last number (not 100% on that).
This effects:
- Version numbers in framework XML description files
[
https://issues.apache.org/jira/browse/FLEX-33451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean reassigned FLEX-33451:
Assignee: Justin Mclean
> The release build due to the Git migration is bro
7 PM:
---
Not completed yet. No need to open new issue it's better to keep all info in
one issue.
was (Author: jmclean):
Not completed yet. No need to open new issue better if it's keep all in
issue.
> The release build due to the Git mi
it's keep all in issue.
> The release build due to the Git migration is broken
>
>
> Key: FLEX-33451
> URL: https://issues.apache.org/jira/browse/FLEX-33451
>
[
https://issues.apache.org/jira/browse/FLEX-33451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frédéric THOMAS closed FLEX-33451.
--
> The release build due to the Git migration is bro
[
https://issues.apache.org/jira/browse/FLEX-33451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frédéric THOMAS resolved FLEX-33451.
Resolution: Fixed
> The release build due to the Git migration is bro
(Not fixed, just commented at the moment
- Build Number (Not fixed)
Please, open a new issue for those 2 remaining ones, the branch relative to
this one had been merged
> The release build due to the Git migration is
and delete the 3.0.33 link if you have it too.
-Fred
-Message d'origine-
From: Frédéric THOMAS
Sent: Thursday, March 28, 2013 6:31 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
It has been fixed in the build.xml, how did you
It has been fixed in the build.xml, how did you call your flex-tlf repo ?
It should be ${FLEX_HOME}/../flex-tlf or ${FLEX_HOME}/../tlf
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Thursday, March 28, 2013 6:23 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release
Hi
Also doesn't look like the TLF issue is fixed in that branch:
git branch
* FLEX-33451
develop
master
ompile:
[compc] Loading configuration file
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml
[compc] Apache Flex compc (Compone
From: Frédéric THOMAS
Sent: Thursday, March 28, 2013 5:42 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
You right, I had to do that but didn't do it, feel free to open other
tickets.
There're no needs to open a new branch, the mother one
t the new issue ids.
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Thursday, March 28, 2013 5:37 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
You right, I just filled the jira accordingly.
Thanks that's a lot clea
Hi,
> You right, I just filled the jira accordingly.
Thanks that's a lot clearer.
There still a minor workflow issue here in that unless we make each of those
sub tasks real JIRA subtasks how do I know who's working on each one (or if
anyone is). I can't assign the entire bug to myself as I wou
7;origine-
From: Justin Mclean
Sent: Thursday, March 28, 2013 5:20 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
It's not a silly question, the answer is because, I opened a jira ticket
[1] in which there are few sub-issues/tasks
FLEX-33451
- TLF: Fixed
- Building process (.gitignore, empty.properties): Fixed
> The release build due to the Git migration is broken
>
>
> Key: FLEX-33451
> URL: https://issues.apa
; doesn't show remotes you
don't know about). Every little bit of info helps. :-)
> merge it to the develop branch as a set of commit to fix the release build.
Does that remove the history of each fix? I'd rather see how each issue/sub
task was fixed not just a generic single comment and one set of changes.
Justin
It's not a silly question, the answer is because, I opened a jira ticket [1]
in which there are few sub-issues/tasks :
The release build due to the Git migration is broken:
- TLF external build
- Build Number
- ASDoc for the experimental lib
- Building process (.gitignore, empty.prope
Hi,
> You can see the fix in the branch I did
Perhaps a silly question but if you have a fix in a branch why hasn't it been
merged into develop? Especially if it fixes an issue. Other people may have
this issue but they wouldn't know that your branch fixes it.
Thanks,
Justin
You can see the fix in the branch I did
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Thursday, March 28, 2013 2:33 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
Ok files the compiler issue but still getting an error
Hi,
Ok files the compiler issue but still getting an error to do with TLF. Assume
this is to do with the recent TLF changes.
Can you remind me how the SDK build files now knows where TLF is? There
nothing in the README that I can see.
compile:
[compc] Loading configuration file
/Users/j
On 3/27/13 12:43 AM, "Justin Mclean" wrote:
> Hi,
>
>> For me, it is using the one in lib, not in ant/lib.
>
> Mine was using the one in ant/lib and issue was fixed my moving the lib one to
> this location. However I'd still like to know why it was using the one in
> ant/lib and not lib - an
humm... weird, I'ld like to see the others result then.
Thanks Erik,
-Fred
-Message d'origine-
From: Erik de Bruin
Sent: Wednesday, March 27, 2013 10:51 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
I ran 'ant
>
> Thanks,
> -Fred
>
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 27, 2013 10:29 AM
>
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broken)
>
> Running 'ant asdoc' gives me:
>
Well, sorry, I meant 'ant doc' from the experimental lib.
Thanks,
-Fred
-Message d'origine-
From: Erik de Bruin
Sent: Wednesday, March 27, 2013 10:29 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Running '
ed
>
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 27, 2013 10:06 AM
>
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broken)
>
> I just did this (OS X) and the build was successful both times (on
>
27;origine-
From: Erik de Bruin
Sent: Wednesday, March 27, 2013 10:06 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
I just did this (OS X) and the build was successful both times (on
develop with 'main', on FLEX-33451 with 'relea
branch,
> checkout the 'FLEX-33451' and build release on it ?
>
> -Fred
>
> -Message d'origine- From: Justin Mclean
> Sent: Wednesday, March 27, 2013 8:11 AM
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broke
Ok, so I'm curious to know where the issue you have comes from as we don't
have it, keep us in touch.
Thanks,
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Wednesday, March 27, 2013 8:44 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was
Hi,
> Couldn't you simply clone again the sdk, build on the develop branch,
> checkout the 'FLEX-33451' and build release on it ?
Tried that it failed as well.
Justin
Hi,
> For me, it is using the one in lib, not in ant/lib.
Mine was using the one in ant/lib and issue was fixed my moving the lib one to
this location. However I'd still like to know why it was using the one in
ant/lib and not lib - anyone know where this is specified?
As far as I know I only
Hi Justin,
Couldn't you simply clone again the sdk, build on the develop branch,
checkout the 'FLEX-33451' and build release on it ?
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Wednesday, March 27, 2013 8:11 AM
To: dev@flex.apache.org
Subject: Re: a
Hi,
> For me, it is using the one in lib, not in ant/lib. Is it possible you have
> a Falcon flexTasks.jar in ant/lib?
Is there an easy way to tell which one it's using? I have flexTasks.jar in both
places.
Thanks,
Justin
ependancy hasn't accidentally got into the SDK release
> build - that's the only reference to compiler.jar I could find.
>
> Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Hi,
> If Justin doesn't help you with asdoc, I will try to find time tomorrow.
My build is still broken (unable to build the themes) so unable to help. Are
you sure a falcon dependancy hasn't accidentally got into the SDK release build
- that's the only reference to compile
I had to pull before I could see your branch. Once I checked it out, the
build script ran fine on my Mac. If Justin doesn't help you with asdoc, I
will try to find time tomorrow.
On 3/26/13 10:50 AM, "Frédéric THOMAS" wrote:
> Ok, I double checked, all good for the release except the build nu
Ok, I double checked, all good for the release except the build number and
the asdoc, so, TLF, empty.properties and .gitignore are ok.
If someone wants to give a hand for the asdoc, run the asdoc target of the
experimental build after you built the sdk.
Once fixed, uncomment in framework.build.
dev@flex.apache.org
Subject: Re: Release build broken
I'm sure you'll be ok too ;-)
Thanks,
-Fred
-Message d'origine-
From: Alex Harui
Sent: Tuesday, March 26, 2013 5:58 PM
To: dev@flex.apache.org
Subject: Re: Release build broken
I'm sure I'll be ok, I
I'm sure you'll be ok too ;-)
Thanks,
-Fred
-Message d'origine-
From: Alex Harui
Sent: Tuesday, March 26, 2013 5:58 PM
To: dev@flex.apache.org
Subject: Re: Release build broken
I'm sure I'll be ok, I don't have any changes in flex-sdk so it will be much
mmands to well start working on
> it.
>
> Thanks,
> -Fred
>
> -Message d'origine-
> From: Alex Harui
> Sent: Tuesday, March 26, 2013 5:51 PM
> To: dev@flex.apache.org
> Subject: Re: Release build broken
>
> OK, I will try to run it in a few hours.
>
&g
files
which you can check with git status)
git checkout
git stash apply "my current work"
Thanks,
-Fred
-Message d'origine-
From: Frédéric THOMAS
Sent: Tuesday, March 26, 2013 1:44 PM
To: dev@flex.apache.org
Subject: Re: Release build broken
Just created https://issues
ush
>
> To go back on the branch you was before and the same working tree / index:
> git stash -u "release" (if you've got uncommitted files/untracked files
> which you can check with git status)
> git checkout
> git stash apply "my current work"
>
> T
1 - 100 of 119 matches
Mail list logo
