Flash/Flex Developer

Good morning, I am interested in subscribing to your mailing list for developers. I would like to contribute in so many ways. I am a long time adobe flash and flex developer and think Apache Flex is the future. The world has somehow managed to focus on lesser architectures that provide little cons

RE: Error compiling SDK

My FLEX_HOME points to C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.9.0 which is a release copy of Apache Flex SDK 4.9.0 installed in my Flash Builder. Tried setting FLEX_HOME to D:\WORK\My Experiments\ApacheFlex\sdk which is the Apache Flex SDK directory I am trying to compile but

Re: asdoc - Release build broken (was: Release build broken)

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 call your

Re: asdoc - Release build broken (was: Release build broken)

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 build broken

Re: asdoc - Release build broken (was: Release build broken)

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

Re: asdoc - Release build broken (was: Release build broken)

Note: If the resolution of some of the sub-issues would have required more than one commit, opening a sub-branch would have been a good practice because the set of commits done in the sub-branch would has been merged into the mother branch first. -Fred -Message d'origine- From: Frédé

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 exists already, just prepend the commit messages with the real issue ids, I'll modify the commit messages of the others before merging to reflect the new issue id

Re: asdoc - Release build broken (was: Release build broken)

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

Re: asdoc - Release build broken (was: Release build broken)

You right, I just filled the jira accordingly. 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 No but I'll re-organize the commits to make it clean, example, at the moment, there's still the a

[jira] [Commented] (FLEX-33451) 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:comment-tabpanel&focusedCommentId=13616038#comment-13616038 ] Frédéric THOMAS commented on FLEX-33451: A remote branch has been created FLEX-334

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. I guess that one way of doing it - but IMO would be better if they were either merged into develop as each sub task was fixed. As that JIRA issue is unassigned I'd assum

Re: asdoc - Release build broken (was: Release build broken)

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.properties) S

Re: asdoc - Release build broken (was: Release build broken)

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

[jira] [Updated] (FLEX-33454) Application with TextInput and flash.media.Video with cause black screen on Android device.

[ https://issues.apache.org/jira/browse/FLEX-33454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenjie Xiong updated FLEX-33454: Attachment: VideoTextInputBUG.fxp Try this attachment project on android tablet device.

[jira] [Updated] (FLEX-33454) Application with TextInput and flash.media.Video with cause black screen on Android device.

[ https://issues.apache.org/jira/browse/FLEX-33454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenjie Xiong updated FLEX-33454: Description: Create mobile application with TextInput control. new a flash.media.Video object, aft

[jira] [Updated] (FLEX-33454) Application with TextInput and flash.media.Video with cause black screen on Android device.

[ https://issues.apache.org/jira/browse/FLEX-33454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenjie Xiong updated FLEX-33454: Description: Create mobile application with TextInput control. new a flash.media.Video object, aft

[jira] [Commented] (FLEX-33454) Application with TextInput and flash.media.Video with cause black screen on Android device.

[ https://issues.apache.org/jira/browse/FLEX-33454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616012#comment-13616012 ] Wenjie Xiong commented on FLEX-33454: - I forgot this clue, must set TextInput skin to

[jira] [Updated] (FLEX-33454) Application with TextInput and flash.media.Video with cause black screen on Android device.

[ https://issues.apache.org/jira/browse/FLEX-33454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenjie Xiong updated FLEX-33454: Description: Create mobile application with TextInput control. new a flash.media.Video object, afte

[jira] [Created] (FLEX-33454) Application with TextInput and flash.media.Video with cause black screen on Android device.

Wenjie Xiong created FLEX-33454: --- Summary: Application with TextInput and flash.media.Video with cause black screen on Android device. Key: FLEX-33454 URL: https://issues.apache.org/jira/browse/FLEX-33454

Re: asdoc - Release build broken (was: Release build broken)

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 to do

Re: Air 3.7 in Apache Flex

Hi, > Mind undoing that as that I believe has closed the discussion and I'm not > able to add anything. Sorry must of been having a senior moment and couldn't see the "reply" button. No need to change anything. Thanks, Justin

Re: Air 3.7 in Apache Flex

Hi, > I just changed Chris' response to Correct (from Helpful) so it shows > immediately below the question. (One of the perks of being a moderator on > Adobe's forums…) ;-) Mind undoing that as that I believe has closed the discussion and I'm not able to add anything. There's a new version o

Re: asdoc - Release build broken (was: Release build broken)

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

[jira] [Assigned] (FLEX-33453) Compilers have wrong copyright year

[ https://issues.apache.org/jira/browse/FLEX-33453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reassigned FLEX-33453: Assignee: Justin Mclean > Compilers have wrong copyright year > ---

[jira] [Created] (FLEX-33453) Compilers have wrong copyright year

Justin Mclean created FLEX-33453: Summary: Compilers have wrong copyright year Key: FLEX-33453 URL: https://issues.apache.org/jira/browse/FLEX-33453 Project: Apache Flex Issue Type: Bug

Re: git commit: FlexJS application now shows in browser

Awesome! Any chance you can put up the working demo onto your people.a.o site? Makes it easier for folks to see what's happening. Thanks, Om On Mar 27, 2013 4:15 PM, "Erik de Bruin" wrote: > Forgot to mention this in the commit message: this goes only for the > 'js-debug' code. The 'js-release

Re: git commit: FlexJS application now shows in browser

Forgot to mention this in the commit message: this goes only for the 'js-debug' code. The 'js-release' code has some more issues that currently prevent it from showing the view in the browser. EdB On Thu, Mar 28, 2013 at 12:07 AM, wrote: > Updated Branches: > refs/heads/develop d8bb65f1e ->

Re: [FalconJx] asm.js

For now, we're using the Google Closure Tools (mainly the GCC with JSDoc annotation). This gives use the benefit of having our output (structured but human readable JavaScript) recompiled into highly optimised and minified 'release' JavaScript. Having said that, given the flexible way FalconJx is

[FalconJx] asm.js

Any thoughts on compiling AS3 into the asm.js subset for super fast execution? http://asmjs.org/spec/latest/ I'm not clear to me what is required for memory management (is it required to simulate the heap, or is that optional?). Kevin N.

Re: [FalconJx] progress update

I'd have to look into it for specifics, but of the top of my head it seems that this most depends on the implementation in the FlexJS JS framework. Emitting the strings required by that framework should really be easy enough. If needed we can "look forward" into AST to look for binding information.

Re: [FalconJx] progress update

[Bindable] results in extra codegen. Binding expressions with {} is a whole other ball of work. I think in FalconJX you might have to modify the node tree in several places when you hit a [Bindable] node. It isn't working correctly in FalconJS either, but my "customer" needs it so I'm hacking a

Re: [FalconJx] progress update

No, not yet. How is this set up in FlexJS? I'm sure I can read Metadata and Databinding information, so I guess it depends on the requirements for the emitted JS if I can easily implement this ;-) EdB On Wednesday, March 27, 2013, Alex Harui wrote: > Does FalconJX handle [Bindable]? My "custo

Re: [FalconJx] progress update

Does FalconJX handle [Bindable]? My "customer" is using it. On 3/27/13 11:56 AM, "Michael Schmalle" wrote: > > Quoting Erik de Bruin : > >> Another one popped into my head just now: I have a gut feeling there >> is a bit of circular logic going on in the whole 'backend', >> 'blockwalker' and

Re: [FalconJx] progress update

Quoting Erik de Bruin : Another one popped into my head just now: I have a gut feeling there is a bit of circular logic going on in the whole 'backend', 'blockwalker' and 'emitter' construct. More specifically in the way the references to them are passed around as arguments in the constructors

Re: [FalconJx] progress update

Another one popped into my head just now: I have a gut feeling there is a bit of circular logic going on in the whole 'backend', 'blockwalker' and 'emitter' construct. More specifically in the way the references to them are passed around as arguments in the constructors for the various classes. But

Re: [FalconJx] progress update

Mike, Just kidding ;-) I'm really happy with FalconJx, once you get to know it it's a pleasure to work with. I hope my last commits didn't give you any additional work in your other projects? I did my best to leave all the APIs alone. There are plenty of TODOs in the code, and I would also like

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Hi Alex, Once we start accept pull-requests, we will need to view and easily find where it is, in case you need to touch or reverse, whether one or more commits. When we need to move, the resolution of a particular ticket between fork's, or between branches disconnected, it will be very useful

Re: [FalconJx] progress update

No thats not what I meant. I am saying with the Randori project compiler, I have not had to touch the core framework for weeks and it is compiling 1000's of lines of code. And application code now. What I meant to say was, the design keeps people in the correct spaces. :) Note; I AM SURE t

Re: [FalconJx] progress update

> All I can say is its easy to fix things in the emitters. :) Thanks, I feel SO special now... :-P EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl

Re: [FalconJx] progress update

Ah ok, this has to do with the emitter, I thought you were talking about language specific errors. All I can say is its easy to fix things in the emitters. :) Mike Quoting Alex Harui : Static initializers were not being output correctly. Some goog.requires were not being listed. On 3/27/1

Re: [FalconJx] progress update

On 3/27/13 10:56 AM, "Erik de Bruin" wrote: > Ok, but note that while the output is NEARLY correct, the application > doesn't work in the browser. Just thought I'd emphasise that ;-) Yeah, I saw that. > > > On Wed, Mar 27, 2013 at 6:50 PM, Alex Harui wrote: >> Excellent. I will try it out l

Re: [FalconJx] progress update

Static initializers were not being output correctly. Some goog.requires were not being listed. On 3/27/13 10:55 AM, "Michael Schmalle" wrote: > > Quoting Alex Harui : > >> Excellent. I will try it out later today. I have to quickly fix some >> FalconJS stuff for my potential "customer", but

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

without taking care if a branch is 1 commit or 10, since this make you gain control of revert something if you need at some point in time Are you saying it is easier to revert a set of one commit + the merge commit than only one commit ? Because to revert one commit is as easy as 'git revert '

Re: [FalconJx] progress update

Ok, but note that while the output is NEARLY correct, the application doesn't work in the browser. Just thought I'd emphasise that ;-) EdB On Wed, Mar 27, 2013 at 6:50 PM, Alex Harui wrote: > Excellent. I will try it out later today. I have to quickly fix some > FalconJS stuff for my potenti

Re: [FalconJx] progress update

Quoting Alex Harui : Excellent. I will try it out later today. I have to quickly fix some FalconJS stuff for my potential "customer", but once I get past that I will see if FalconJX can generate the same code. I am hopeful that if I run into more of the kinds of errors I am fixing in FalconJ

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Hi Carlos, If you could take the time to show an example where having a 1 commit branch helped you "gain control" that would help me and probably others understand the tradeoffs. On 3/27/13 10:47 AM, "Carlos Rovira" wrote: > Hi Alex, > > as I said this is a matter of taste, but we are using g

Re: [FalconJx] progress update

Excellent. I will try it out later today. I have to quickly fix some FalconJS stuff for my potential "customer", but once I get past that I will see if FalconJX can generate the same code. I am hopeful that if I run into more of the kinds of errors I am fixing in FalconJS, that they will be easi

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Hi Alex, as I said this is a matter of taste, but we are using git with huge projects for months and when we are merging and generating releases and we end wanting to easily see *all* branches to quickly see what we want to do, without taking care if a branch is 1 commit or 10, since this make you

Re: Git commit emails

I made this request to INFRA a while ago. I will ping them again now. (I dont think we can do this ourselves, but if someone knows how, please feel free to) Thanks, Om On Wed, Mar 27, 2013 at 10:43 AM, Erik de Bruin wrote: > Is this something we can implement ourselves, or must this go through

Re: Git commit emails

Is this something we can implement ourselves, or must this go through INFRA? EdB On Mon, Mar 18, 2013 at 6:45 PM, Om wrote: > On Mon, Mar 18, 2013 at 10:20 AM, Gordon Smith wrote: > >> The email subject is currently something like "git commit: The >> files/directories to exclude while checkin

Re: [FalconJx] progress update

Another update (have taken/will take some time to get this right this week): FalconJx can now parse both FlexJS MXML and AS reasonably correctly. If run from the command line, it will now create the correct output directories (bin/js-debug and bin/js-release) and emit all JS and HTML files, both p

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Jose, It is not a big deal to do in a way or another, I'm just saying it is more readable rebasing than forcing a merge commit, it makes 2 commits instead of 1 when there's only 1 commit of real work, and for what ? Thanks, -Fred -Message d'origine- From: Jose Barragan Sent: Wedne

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

I"m used to SVN's linear history. I like the fact that Git can show branch history, and like the idea that I can do multiple commits before pushing and each of those commits is clearly shown in the history. But if I don't want to show those multiple commits or I don't have multiple commits, my ins

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

That's the point Alex... Any solve can resolve as a single commit or in a change set, and this decision, under what criterial it does? -- Jose Barragan Chief Software Architect Codeoscopic Madrid C/. Infanta Mercedes, 92. Planta 5. 505. 28020 Madrid. Tel.: +34 912 94 80 80 On Mar 27, 2013, at

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Correction: "Why should I do" instead of "What should I do". Finally, you was one of the more talkative person about Git before the migration, I would have supposed you wrote something for Git on the wiki, good practices, etc... but it didn't happen and from what I read from you now, I'm reali

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

At minimum, if we can't decide on one particular practice, can we get a better understanding of what problem is solved by a single commit in a branch? Then those who are trying to decide what to do can make a better decision. On 3/27/13 9:36 AM, "Frédéric THOMAS" wrote: > Another point Carlos,

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Another point Carlos, this is really a matter of tastes. Each one should be happy with his way of proceed What should I do a git wiki with the good practices if at the end everyone does what he wants, I guess we can try as written in the wiki for one month and if it doesn't fit we can change

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Yeah, for sure, it's your point of view and happily everyone's got one and not everyone the same, but from what I see from the current graph on the develop branch or the one gave by Jose plus the explanations you gave, I have the impression to see and hear "Why should I do simple when I can do

Re: Error compiling SDK

Any chance you have a FLEX_HOME environment variable pointing to an Adobe Flex SDK? On 3/27/13 6:14 AM, "Tigran Najaryan" wrote: > Hi guys, > > > > I am trying to compile the SDK and get an error during the build. > > > > I started here http://flex.apache.org/download-source.html and fo

[jira] [Commented] (FLEX-33452) NEP with MXMLC

[ https://issues.apache.org/jira/browse/FLEX-33452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615399#comment-13615399 ] Alex Harui commented on FLEX-33452: --- I know that bugs.adobe.com/jira is near end of life

Re: Update about Utilities repo migration

+1 -- Jose Barragan Chief Software Architect Codeoscopic Madrid C/. Infanta Mercedes, 92. Planta 5. 505. 28020 Madrid. Tel.: +34 912 94 80 80 On Mar 27, 2013, at 10:39 AM, Carlos Rovira wrote: > +1 > > 2013/3/27 Frédéric THOMAS > >> +1 too >> >> -Fred >> >> -Message d'origine- Fr

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

IMHO this is hard to see, and even more for people outside or coming some time later in time, but that's only my opinion... I think we should not stand too much on these topics and going forward since this is really a matter of tastes. Each one should be happy with his way of proceed while making t

Error compiling SDK

Hi guys, I am trying to compile the SDK and get an error during the build. I started here http://flex.apache.org/download-source.html and followed the instructions in "Bleeding-Edge Release". After getting the source code using git I installed the prerequisites as per the README file. Then

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

It should have been like that even: * Merge branch ‘FLEX-33451’ into develop [Fred] * FLEX-33451: Fixed .gitignore [Fred] * FLEX-33451: Tempora... [Fred] * FLEX-33451: Fix TLF [Fred] * FLEX-33

Re: asdoc - Release build broken (was: Release build broken)

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

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Having the rule of one commit doesn't generated an extra merge commit and makes the log history more readable and because you know that corresponds to 1 single task/jira/file, it's still easy to find it back without the visual pollution of the extra useless merge commit. For the dictator-lieut

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Thanks Carlos, and sorry for the inconvenience -- Jose Barragan Chief Software Architect Codeoscopic Madrid C/. Infanta Mercedes, 92. Planta 5. 505. 28020 Madrid. Tel.: +34 912 94 80 80 On Mar 27, 2013, at 10:58 AM, Carlos Rovira wrote: > Hi Pepe, the link is tokenized for your use. Here's th

Re: asdoc - Release build broken (was: Release build broken)

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 doc' and got a successfu

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Hi Pepe, the link is tokenized for your use. Here's the public link: http://refcardz.dzone.com/refcardz/git-patterns-and-anti-patterns Thanks Carlos 2013/3/27 Jose Barragán > Sorry for missing link: Git Patterns and Anti-Patterns: Scaling from > Workgroup to Enterprise< > http://refcardz.dz

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Sorry for missing link: Git Patterns and Anti-Patterns: Scaling from Workgroup to Enterprise --> http://refcardz.dzone.com/assets/download/refcard/bf3d79c7ce6019dc5ff28cf

Re: asdoc - Release build broken (was: Release build broken)

I ran 'ant doc' and got a successful build. However, one of the 'sections' (?) did show a "Fatal Error": doc: [asdoc] Loading configuration file /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/flex-config.xml [asdoc] [Fatal Error] :54:6: The element type "p" must be terminated by

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

+1 with Carlos check it out this: Git Patterns and Anti-Patterns: Scaling from Workgroup to Enterprise -- Jose Barragan Chief Software Architect Codeoscopic Madrid C/. Infanta Mercedes, 92. Planta 5. 505. 28020 Madrid. Tel.: +34 912 94 80 80 On Mar 27, 2013, at 10:35 AM, Jose Barragan wrote

Re: asdoc - Release build broken (was: Release build broken)

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 'ant asdoc' gives me: Buildfi

Re: Update about Utilities repo migration

+1 2013/3/27 Frédéric THOMAS > +1 too > > -Fred > > -Message d'origine- From: Erik de Bruin > Sent: Wednesday, March 27, 2013 8:18 AM > To: dev@flex.apache.org > Subject: Re: Update about Utilities repo migration > > > +1 > > EdB > > > > On Wed, Mar 27, 2013 at 4:18 AM, Alex Harui wrote

Re: asdoc - Release build broken (was: Release build broken)

Running 'ant asdoc' gives me: Buildfile: build.xml asdoc: clean: doc: [asdoc] Loading configuration file /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/flex-config.xml [asdoc] /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/airspark/src/spark/components/Wind

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Hi Frederic, in our experience working with GIT we saw that was extremely helpful to have visual track of each set of commits that are a single fix, functionality, feature or whatever, since you can always operate and have much control as branches grow and ramifies. In the particular case you poin

Re: asdoc - Release build broken (was: Release build broken)

Did you tried the asdoc target for the experimental project ? I deactivated it in the release to be able to continue to build and see if there wasn't any other errors, to try it you should run the asdoc target directly from the experimental lib itself. Thanks, -Fred -Message d'origine---

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 'release'). EdB On Wed, Mar 27, 2013 at 8:42 AM, Frédéric THOMAS wrote: > Hi Justin, > > Couldn't you simply clone again the sdk, build on the develop branch, > checkout the 'FLEX-33451'

Re: Jenkins and Falcon

Hi So a falcon jenkins job is now up and running. In more detail this job goes through following steps: 1) Checkout tlf(master), sdk(develop), falcon(develop) from git 2) Copy tlf to sdk 3) Download dependencies like playerglobal, air, JFlex 4) Build SDK 5) Build compiler 6) Execute compiler Tes

Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop

Hi Carlos, This merge you did make me think I didn't talk about this case on the wiki [1], so I updated it, in short, while it is good to start a branch as you did for a new jira ticket and as you may don't know the final number of commits you will have at the end, once it is the time to merge

[jira] [Commented] (FLEX-33452) NEP with MXMLC

[ https://issues.apache.org/jira/browse/FLEX-33452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615028#comment-13615028 ] donjao commented on FLEX-33452: --- And as of bugbase.adobe.com I never got help from them unfo

[jira] [Commented] (FLEX-33452) NEP with MXMLC

[ https://issues.apache.org/jira/browse/FLEX-33452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615026#comment-13615026 ] donjao commented on FLEX-33452: --- @Alex Hauri, thank you for quick reply. Actually I was tryi

Re: Update about Utilities repo migration

+1 too -Fred -Message d'origine- From: Erik de Bruin Sent: Wednesday, March 27, 2013 8:18 AM To: dev@flex.apache.org Subject: Re: Update about Utilities repo migration +1 EdB On Wed, Mar 27, 2013 at 4:18 AM, Alex Harui wrote: Yup, let's get it done. On 3/26/13 7:55 PM, "Om" w

Re: asdoc - Release build broken (was: Release build broken)

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: Release build bro

Re: asdoc - Release build broken (was: Release build broken)

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

Re: asdoc - Release build broken (was: Release build broken)

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

Re: asdoc - Release build broken (was: Release build broken)

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: asdoc - Release build brok

Re: Update about Utilities repo migration

+1 EdB On Wed, Mar 27, 2013 at 4:18 AM, Alex Harui wrote: > Yup, let's get it done. > > > On 3/26/13 7:55 PM, "Om" wrote: > >> Here is David@Infra's note about the missing history in the flex-utilities >> git repo. >> >> I think we should accept the repo as it is and move ahead. Any objectio

Re: asdoc - Release build broken (was: Release build broken)

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