Re: AW: AW: [FlexJS] Status on Maven migration
Skipped over flex-compiler-oem and got the externs to compile. Then I synced up and got the same error that Chris reported. Looks like a bug where a class with no super class but has @override metadata on a method gets the method commented out. I'm out of time for tonight and will look at it tomorrow unless someone beats me to it. -Alex On 4/21/16, 2:00 PM, "Alex Harui" wrote: >OK, got through compiler.jx and its tests. > >I started looking at flex-oem-compiler and noticed it is pulling in the >Apache Flex SDK swfutils.jar instead of building a smaller subset that >frees FlexJS from dependencies on the Flex SDK. Since the files we need >are rarely changed, I am tempted to just check them into a project. Also, >they are shared by the debugger project which does not seem to have a >pom.xml. I think it would be ok to call this subset swfutils_min. The >trick is that the classes in this swfutils subset apparently shared with >FlashBuilder, so I think they have to retain their package names. > >Thoughts? >-Alex > >On 4/21/16, 8:28 AM, "Alex Harui" wrote: > >>Whee! The compiler tests are now working. >> >>I'm trying to figure out my next task. I'm afraid to sync up and push my >>changes since Chris is saying things are broken. And I'm not clear how >>desperate Harbs is for a fix for the Jquery thing. IMO, getting the >>Maven >>branches merged into develop is the top priority. >> >>My current thinking is for me to plow ahead on the rest of the Ant build >>without syncing up, then when I get through that I'll sync up and see if >>the Ant build has the same problems Chris is seeing. Chris can you work >>with an older revision of flex-falcon for now to make progress on >>flex-asjs? >> >>-Alex >> >>On 4/21/16, 7:50 AM, "Alex Harui" wrote: >> >>> >>> >>>On 4/21/16, 1:38 AM, "Christofer Dutz" >>>wrote: >>> Ok ... so today I'm feeling like I'm wasting my time again :-( I merged the changes from develop up to my feature/maven-migration-test ... unfortunately I had do manually merge quite some stuff, but that's ok. Now my build no longer worked. The Externs no longer compiled. So I switched to my Ant version, updated and did a "clean-all" and "all" build ... this too didn't work, even if I got different errors. So as a measure of last resort, I did that "wipe-all" and then an "all" build. Now at least the Ant build worked again. Unfortunately I couldn't see what has changed :-( >>> >>>What was the error you got? >>> Could you guys please post to this list if you change any downloads or change things in the build? It's one thing to port something, but it's a completely different thing to find problems that now occur in a previously ported part :-( I think it would eventually be a good idea to do the maven switch pretty soon cause I'm loosing more and more of my time in keeping things in sync ... time I would prefer to be investing on pushing the migration of ASJS forward. >>> >>>I'm still work on the Ant build in maven-migration-test. I got through >>>compiler-build-tools and compiler-jburg-types and most of compiler, but >>>am >>>currently on compiler/src/test. Then on to compiler.jx, and the externs >>>and other things. Hope to be done with it maybe Monday. >>> >>>-Alex >>> >> >
Re: AW: AW: [FlexJS] Status on Maven migration
OK, got through compiler.jx and its tests. I started looking at flex-oem-compiler and noticed it is pulling in the Apache Flex SDK swfutils.jar instead of building a smaller subset that frees FlexJS from dependencies on the Flex SDK. Since the files we need are rarely changed, I am tempted to just check them into a project. Also, they are shared by the debugger project which does not seem to have a pom.xml. I think it would be ok to call this subset swfutils_min. The trick is that the classes in this swfutils subset apparently shared with FlashBuilder, so I think they have to retain their package names. Thoughts? -Alex On 4/21/16, 8:28 AM, "Alex Harui" wrote: >Whee! The compiler tests are now working. > >I'm trying to figure out my next task. I'm afraid to sync up and push my >changes since Chris is saying things are broken. And I'm not clear how >desperate Harbs is for a fix for the Jquery thing. IMO, getting the Maven >branches merged into develop is the top priority. > >My current thinking is for me to plow ahead on the rest of the Ant build >without syncing up, then when I get through that I'll sync up and see if >the Ant build has the same problems Chris is seeing. Chris can you work >with an older revision of flex-falcon for now to make progress on >flex-asjs? > >-Alex > >On 4/21/16, 7:50 AM, "Alex Harui" wrote: > >> >> >>On 4/21/16, 1:38 AM, "Christofer Dutz" wrote: >> >>>Ok ... so today I'm feeling like I'm wasting my time again :-( >>> >>>I merged the changes from develop up to my feature/maven-migration-test >>>... unfortunately I had do manually merge quite some stuff, but that's >>>ok. Now my build no longer worked. The Externs no longer compiled. So I >>>switched to my Ant version, updated and did a "clean-all" and "all" >>>build >>>... this too didn't work, even if I got different errors. So as a >>>measure >>>of last resort, I did that "wipe-all" and then an "all" build. Now at >>>least the Ant build worked again. Unfortunately I couldn't see what has >>>changed :-( >> >>What was the error you got? >> >>> >>>Could you guys please post to this list if you change any downloads or >>>change things in the build? It's one thing to port something, but it's a >>>completely different thing to find problems that now occur in a >>>previously ported part :-( >>> >>>I think it would eventually be a good idea to do the maven switch pretty >>>soon cause I'm loosing more and more of my time in keeping things in >>>sync >>>... time I would prefer to be investing on pushing the migration of ASJS >>>forward. >> >>I'm still work on the Ant build in maven-migration-test. I got through >>compiler-build-tools and compiler-jburg-types and most of compiler, but >>am >>currently on compiler/src/test. Then on to compiler.jx, and the externs >>and other things. Hope to be done with it maybe Monday. >> >>-Alex >> >
Re: AW: AW: [FlexJS] Status on Maven migration
I might have misunderstood what you meant by synching up. I thought you meant that you didn't want to pull the latest changes because you worried about the Ant stuff not working. - Josh On Apr 21, 2016 9:06 AM, "Alex Harui" wrote: > I think maybe I'm confused, but I think he's not stuck on the node > externs, but in the externc output doing some commenting. So that's what > I'm going to avoid until I get to the externs section myself. > > -Alex > > On 4/21/16, 8:39 AM, "Josh Tynjala" wrote: > > >For the Ant build, you need to clear out the third-party downloads to > >ensure that some new files are downloaded (new externs for Node.js). If > >the > >Ant build sees that the Closure compiler is already there, it will skip > >the > >rest of the downloads. Chris said that wipe-all does the trick. Locally, I > >was running thirdparty-clean in the compiler.jx directory, so that works > >too. > > > >I was also able to get a successful build on Jenkins, so it should just be > >a matter of ensuring that the new files get downloaded. > > > >- Josh > > > >On Thu, Apr 21, 2016 at 8:28 AM, Alex Harui wrote: > > > >> Whee! The compiler tests are now working. > >> > >> I'm trying to figure out my next task. I'm afraid to sync up and push > >>my > >> changes since Chris is saying things are broken. And I'm not clear how > >> desperate Harbs is for a fix for the Jquery thing. IMO, getting the > >>Maven > >> branches merged into develop is the top priority. > >> > >> My current thinking is for me to plow ahead on the rest of the Ant build > >> without syncing up, then when I get through that I'll sync up and see if > >> the Ant build has the same problems Chris is seeing. Chris can you work > >> with an older revision of flex-falcon for now to make progress on > >> flex-asjs? > >> > >> -Alex > >> > >> On 4/21/16, 7:50 AM, "Alex Harui" wrote: > >> > >> > > >> > > >> >On 4/21/16, 1:38 AM, "Christofer Dutz" > >>wrote: > >> > > >> >>Ok ... so today I'm feeling like I'm wasting my time again :-( > >> >> > >> >>I merged the changes from develop up to my > >>feature/maven-migration-test > >> >>... unfortunately I had do manually merge quite some stuff, but that's > >> >>ok. Now my build no longer worked. The Externs no longer compiled. So > >>I > >> >>switched to my Ant version, updated and did a "clean-all" and "all" > >>build > >> >>... this too didn't work, even if I got different errors. So as a > >>measure > >> >>of last resort, I did that "wipe-all" and then an "all" build. Now at > >> >>least the Ant build worked again. Unfortunately I couldn't see what > >>has > >> >>changed :-( > >> > > >> >What was the error you got? > >> > > >> >> > >> >>Could you guys please post to this list if you change any downloads or > >> >>change things in the build? It's one thing to port something, but > >>it's a > >> >>completely different thing to find problems that now occur in a > >> >>previously ported part :-( > >> >> > >> >>I think it would eventually be a good idea to do the maven switch > >>pretty > >> >>soon cause I'm loosing more and more of my time in keeping things in > >>sync > >> >>... time I would prefer to be investing on pushing the migration of > >>ASJS > >> >>forward. > >> > > >> >I'm still work on the Ant build in maven-migration-test. I got through > >> >compiler-build-tools and compiler-jburg-types and most of compiler, > >>but am > >> >currently on compiler/src/test. Then on to compiler.jx, and the > >>externs > >> >and other things. Hope to be done with it maybe Monday. > >> > > >> >-Alex > >> > > >> > >> > >
Re: AW: AW: [FlexJS] Status on Maven migration
I think maybe I'm confused, but I think he's not stuck on the node externs, but in the externc output doing some commenting. So that's what I'm going to avoid until I get to the externs section myself. -Alex On 4/21/16, 8:39 AM, "Josh Tynjala" wrote: >For the Ant build, you need to clear out the third-party downloads to >ensure that some new files are downloaded (new externs for Node.js). If >the >Ant build sees that the Closure compiler is already there, it will skip >the >rest of the downloads. Chris said that wipe-all does the trick. Locally, I >was running thirdparty-clean in the compiler.jx directory, so that works >too. > >I was also able to get a successful build on Jenkins, so it should just be >a matter of ensuring that the new files get downloaded. > >- Josh > >On Thu, Apr 21, 2016 at 8:28 AM, Alex Harui wrote: > >> Whee! The compiler tests are now working. >> >> I'm trying to figure out my next task. I'm afraid to sync up and push >>my >> changes since Chris is saying things are broken. And I'm not clear how >> desperate Harbs is for a fix for the Jquery thing. IMO, getting the >>Maven >> branches merged into develop is the top priority. >> >> My current thinking is for me to plow ahead on the rest of the Ant build >> without syncing up, then when I get through that I'll sync up and see if >> the Ant build has the same problems Chris is seeing. Chris can you work >> with an older revision of flex-falcon for now to make progress on >> flex-asjs? >> >> -Alex >> >> On 4/21/16, 7:50 AM, "Alex Harui" wrote: >> >> > >> > >> >On 4/21/16, 1:38 AM, "Christofer Dutz" >>wrote: >> > >> >>Ok ... so today I'm feeling like I'm wasting my time again :-( >> >> >> >>I merged the changes from develop up to my >>feature/maven-migration-test >> >>... unfortunately I had do manually merge quite some stuff, but that's >> >>ok. Now my build no longer worked. The Externs no longer compiled. So >>I >> >>switched to my Ant version, updated and did a "clean-all" and "all" >>build >> >>... this too didn't work, even if I got different errors. So as a >>measure >> >>of last resort, I did that "wipe-all" and then an "all" build. Now at >> >>least the Ant build worked again. Unfortunately I couldn't see what >>has >> >>changed :-( >> > >> >What was the error you got? >> > >> >> >> >>Could you guys please post to this list if you change any downloads or >> >>change things in the build? It's one thing to port something, but >>it's a >> >>completely different thing to find problems that now occur in a >> >>previously ported part :-( >> >> >> >>I think it would eventually be a good idea to do the maven switch >>pretty >> >>soon cause I'm loosing more and more of my time in keeping things in >>sync >> >>... time I would prefer to be investing on pushing the migration of >>ASJS >> >>forward. >> > >> >I'm still work on the Ant build in maven-migration-test. I got through >> >compiler-build-tools and compiler-jburg-types and most of compiler, >>but am >> >currently on compiler/src/test. Then on to compiler.jx, and the >>externs >> >and other things. Hope to be done with it maybe Monday. >> > >> >-Alex >> > >> >>
Re: AW: AW: [FlexJS] Status on Maven migration
For the Ant build, you need to clear out the third-party downloads to ensure that some new files are downloaded (new externs for Node.js). If the Ant build sees that the Closure compiler is already there, it will skip the rest of the downloads. Chris said that wipe-all does the trick. Locally, I was running thirdparty-clean in the compiler.jx directory, so that works too. I was also able to get a successful build on Jenkins, so it should just be a matter of ensuring that the new files get downloaded. - Josh On Thu, Apr 21, 2016 at 8:28 AM, Alex Harui wrote: > Whee! The compiler tests are now working. > > I'm trying to figure out my next task. I'm afraid to sync up and push my > changes since Chris is saying things are broken. And I'm not clear how > desperate Harbs is for a fix for the Jquery thing. IMO, getting the Maven > branches merged into develop is the top priority. > > My current thinking is for me to plow ahead on the rest of the Ant build > without syncing up, then when I get through that I'll sync up and see if > the Ant build has the same problems Chris is seeing. Chris can you work > with an older revision of flex-falcon for now to make progress on > flex-asjs? > > -Alex > > On 4/21/16, 7:50 AM, "Alex Harui" wrote: > > > > > > >On 4/21/16, 1:38 AM, "Christofer Dutz" wrote: > > > >>Ok ... so today I'm feeling like I'm wasting my time again :-( > >> > >>I merged the changes from develop up to my feature/maven-migration-test > >>... unfortunately I had do manually merge quite some stuff, but that's > >>ok. Now my build no longer worked. The Externs no longer compiled. So I > >>switched to my Ant version, updated and did a "clean-all" and "all" build > >>... this too didn't work, even if I got different errors. So as a measure > >>of last resort, I did that "wipe-all" and then an "all" build. Now at > >>least the Ant build worked again. Unfortunately I couldn't see what has > >>changed :-( > > > >What was the error you got? > > > >> > >>Could you guys please post to this list if you change any downloads or > >>change things in the build? It's one thing to port something, but it's a > >>completely different thing to find problems that now occur in a > >>previously ported part :-( > >> > >>I think it would eventually be a good idea to do the maven switch pretty > >>soon cause I'm loosing more and more of my time in keeping things in sync > >>... time I would prefer to be investing on pushing the migration of ASJS > >>forward. > > > >I'm still work on the Ant build in maven-migration-test. I got through > >compiler-build-tools and compiler-jburg-types and most of compiler, but am > >currently on compiler/src/test. Then on to compiler.jx, and the externs > >and other things. Hope to be done with it maybe Monday. > > > >-Alex > > > >
Re: AW: AW: [FlexJS] Status on Maven migration
Whee! The compiler tests are now working. I'm trying to figure out my next task. I'm afraid to sync up and push my changes since Chris is saying things are broken. And I'm not clear how desperate Harbs is for a fix for the Jquery thing. IMO, getting the Maven branches merged into develop is the top priority. My current thinking is for me to plow ahead on the rest of the Ant build without syncing up, then when I get through that I'll sync up and see if the Ant build has the same problems Chris is seeing. Chris can you work with an older revision of flex-falcon for now to make progress on flex-asjs? -Alex On 4/21/16, 7:50 AM, "Alex Harui" wrote: > > >On 4/21/16, 1:38 AM, "Christofer Dutz" wrote: > >>Ok ... so today I'm feeling like I'm wasting my time again :-( >> >>I merged the changes from develop up to my feature/maven-migration-test >>... unfortunately I had do manually merge quite some stuff, but that's >>ok. Now my build no longer worked. The Externs no longer compiled. So I >>switched to my Ant version, updated and did a "clean-all" and "all" build >>... this too didn't work, even if I got different errors. So as a measure >>of last resort, I did that "wipe-all" and then an "all" build. Now at >>least the Ant build worked again. Unfortunately I couldn't see what has >>changed :-( > >What was the error you got? > >> >>Could you guys please post to this list if you change any downloads or >>change things in the build? It's one thing to port something, but it's a >>completely different thing to find problems that now occur in a >>previously ported part :-( >> >>I think it would eventually be a good idea to do the maven switch pretty >>soon cause I'm loosing more and more of my time in keeping things in sync >>... time I would prefer to be investing on pushing the migration of ASJS >>forward. > >I'm still work on the Ant build in maven-migration-test. I got through >compiler-build-tools and compiler-jburg-types and most of compiler, but am >currently on compiler/src/test. Then on to compiler.jx, and the externs >and other things. Hope to be done with it maybe Monday. > >-Alex >
Re: AW: AW: [FlexJS] Status on Maven migration
On 4/21/16, 1:38 AM, "Christofer Dutz" wrote: >Ok ... so today I'm feeling like I'm wasting my time again :-( > >I merged the changes from develop up to my feature/maven-migration-test >... unfortunately I had do manually merge quite some stuff, but that's >ok. Now my build no longer worked. The Externs no longer compiled. So I >switched to my Ant version, updated and did a "clean-all" and "all" build >... this too didn't work, even if I got different errors. So as a measure >of last resort, I did that "wipe-all" and then an "all" build. Now at >least the Ant build worked again. Unfortunately I couldn't see what has >changed :-( What was the error you got? > >Could you guys please post to this list if you change any downloads or >change things in the build? It's one thing to port something, but it's a >completely different thing to find problems that now occur in a >previously ported part :-( > >I think it would eventually be a good idea to do the maven switch pretty >soon cause I'm loosing more and more of my time in keeping things in sync >... time I would prefer to be investing on pushing the migration of ASJS >forward. I'm still work on the Ant build in maven-migration-test. I got through compiler-build-tools and compiler-jburg-types and most of compiler, but am currently on compiler/src/test. Then on to compiler.jx, and the externs and other things. Hope to be done with it maybe Monday. -Alex
Re: AW: AW: [FlexJS] Status on Maven migration
Things are commented out by externc when they are explicitly excluded.
Those look like some things I re-included in the config XML for js.swc
(which I assume you'd still use with Maven...) after fixing some bugs.
- Josh
On Apr 21, 2016 2:46 AM, "Christofer Dutz"
wrote:
> I'm currently having a problem with the JS extern.
> EXTERNC seems to be generating commented out methods and I have no idea
> why:
>
> Here the generated code for Generator.as where I get a compile error cause
> next is commented out :-(
>
>
> package {
>
> /**
> * @see
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Generator
> * @see [es6]
> * @constructor implements Iterator */
> public class Generator implements Iterator {
>
> /**
> * @see
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Generator
> * @see [es6]
> */
> public function Generator() {
> super();
> }
>
> /**
> * @param opt_value [?]
> * @see [es6]
> * @returns {{done: boolean, value: (VALUE|null)}}
> */
> //public function next(value:Object = null):Object { return null; }
>
> /**
> * @param exception [?]
> * @see [es6]
> * @returns {{done: boolean, value: (VALUE|null)}}
> */
> //public function throw(exception:Object /* ? */):Object { return
> null; }
>
> /**
> * @param value [(VALUE|null)]
> * @see [es6]
> * @returns {{done: boolean, value: (VALUE|null)}}
> */
> //public function return(value:Object):Object { return null; }
>
> }
> }
>
>
> Chris
>
> Von: Christofer Dutz
> Gesendet: Donnerstag, 21. April 2016 10:38
> An: dev@flex.apache.org
> Betreff: AW: AW: [FlexJS] Status on Maven migration
>
> Ok ... so today I'm feeling like I'm wasting my time again :-(
>
> I merged the changes from develop up to my feature/maven-migration-test
> ... unfortunately I had do manually merge quite some stuff, but that's ok.
> Now my build no longer worked. The Externs no longer compiled. So I
> switched to my Ant version, updated and did a "clean-all" and "all" build
> ... this too didn't work, even if I got different errors. So as a measure
> of last resort, I did that "wipe-all" and then an "all" build. Now at least
> the Ant build worked again. Unfortunately I couldn't see what has changed
> :-(
>
> Could you guys please post to this list if you change any downloads or
> change things in the build? It's one thing to port something, but it's a
> completely different thing to find problems that now occur in a previously
> ported part :-(
>
> I think it would eventually be a good idea to do the maven switch pretty
> soon cause I'm loosing more and more of my time in keeping things in sync
> ... time I would prefer to be investing on pushing the migration of ASJS
> forward.
>
> Chris
>
>
> Von: Christofer Dutz
> Gesendet: Freitag, 15. April 2016 07:44
> An: dev@flex.apache.org
> Betreff: AW: AW: [FlexJS] Status on Maven migration
>
> In the cleanup script I simply removed all non Maven related stuff. What I
> could do, was to have my IntelliJ to generate an ant build from the Maven
> build. Eventually that would get rid of some of the problems if the old ant
> build.
>
> Chris
>
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
> Ursprüngliche Nachricht
> Von: Alex Harui
> Datum: 15.04.16 01:02 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: AW: [FlexJS] Status on Maven migration
>
>
>
> On 4/14/16, 9:30 AM, "Christofer Dutz" wrote:
>
> >The structure is final, I'm just working on the details now. I also
> >noticed that hit seems to be able to sync updates even if the structure
> >is changed :-)
> >
> >But how about giving Maven a try? Eclipse does support that with the
> >m2eclipse plugin.
>
> I might try that once you get snapshots working in one build.
>
> I got the maven-migration-test branch. There is no build.xml at the
> top-level. Any reason I can't put one there?
>
> Thanks,
> -Alex
>
Re: AW: AW: [FlexJS] Status on Maven migration
We should probably use language_in with whatever the ES5 value is, instead
of the default ES3. We're targeting ES5 in our compiler output, so it would
make sense.
- Josh
On Apr 21, 2016 3:23 AM, "Christofer Dutz"
wrote:
> Would it be possible to eliminate some of the warnings while generating
> the externs?
> I am getting tons of:
> WARNUNG: [es6]:1083: WARNING - Keywords and reserved words are not allowed
> as unquoted property names in older versions of JavaScript. If you are
> targeting newer versions of JavaScript, set the appropriate language_in
> option.
>
> So I started ignoring the red text printed out in my console ... now I
> noticed that some CRITICAL have mixed themselves between all of these
> warnings. If we could set that "language_in" option, it would make things
> easier and I could make the generator fail if there is output on the error
> stream.
>
> Chris
>
>
> Von: Christofer Dutz
> Gesendet: Donnerstag, 21. April 2016 11:46
> An: dev@flex.apache.org
> Betreff: AW: AW: [FlexJS] Status on Maven migration
>
> I'm currently having a problem with the JS extern.
> EXTERNC seems to be generating commented out methods and I have no idea
> why:
>
> Here the generated code for Generator.as where I get a compile error cause
> next is commented out :-(
>
>
> package {
>
> /**
> * @see
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Generator
> * @see [es6]
> * @constructor implements Iterator */
> public class Generator implements Iterator {
>
> /**
> * @see
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Generator
> * @see [es6]
> */
> public function Generator() {
> super();
> }
>
> /**
> * @param opt_value [?]
> * @see [es6]
> * @returns {{done: boolean, value: (VALUE|null)}}
> */
> //public function next(value:Object = null):Object { return null; }
>
> /**
> * @param exception [?]
> * @see [es6]
> * @returns {{done: boolean, value: (VALUE|null)}}
> */
> //public function throw(exception:Object /* ? */):Object { return
> null; }
>
> /**
> * @param value [(VALUE|null)]
> * @see [es6]
> * @returns {{done: boolean, value: (VALUE|null)}}
> */
> //public function return(value:Object):Object { return null; }
>
> }
> }
>
>
> Chris
>
> Von: Christofer Dutz
> Gesendet: Donnerstag, 21. April 2016 10:38
> An: dev@flex.apache.org
> Betreff: AW: AW: [FlexJS] Status on Maven migration
>
> Ok ... so today I'm feeling like I'm wasting my time again :-(
>
> I merged the changes from develop up to my feature/maven-migration-test
> ... unfortunately I had do manually merge quite some stuff, but that's ok.
> Now my build no longer worked. The Externs no longer compiled. So I
> switched to my Ant version, updated and did a "clean-all" and "all" build
> ... this too didn't work, even if I got different errors. So as a measure
> of last resort, I did that "wipe-all" and then an "all" build. Now at least
> the Ant build worked again. Unfortunately I couldn't see what has changed
> :-(
>
> Could you guys please post to this list if you change any downloads or
> change things in the build? It's one thing to port something, but it's a
> completely different thing to find problems that now occur in a previously
> ported part :-(
>
> I think it would eventually be a good idea to do the maven switch pretty
> soon cause I'm loosing more and more of my time in keeping things in sync
> ... time I would prefer to be investing on pushing the migration of ASJS
> forward.
>
> Chris
>
>
> Von: Christofer Dutz
> Gesendet: Freitag, 15. April 2016 07:44
> An: dev@flex.apache.org
> Betreff: AW: AW: [FlexJS] Status on Maven migration
>
> In the cleanup script I simply removed all non Maven related stuff. What I
> could do, was to have my IntelliJ to generate an ant build from the Maven
> build. Eventually that would get rid of some of the problems if the old ant
> build.
>
> Chris
>
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
> Ursprüngliche Nachricht
> Von: Alex Harui
> Datum: 15.04.16 01:02 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: AW: [FlexJS] Status on Maven migration
>
>
>
> On 4/14/16, 9:30 AM, "Christofer Dutz" wrote:
>
> >The structure is final, I'm just working on the details now. I also
> >noticed that hit seems to be able to sync updates even if the structure
> >is changed :-)
> >
> >But how about giving Maven a try? Eclipse does support that with the
> >m2eclipse plugin.
>
> I might try that once you get snapshots working in one build.
>
> I got the maven-migration-test branch. There is no build.xml at the
> top-level. Any reason I can't put one there?
>
> Thanks,
> -Alex
>
Re: AW: AW: [FlexJS] Status on Maven migration
On 4/14/16, 10:44 PM, "Christofer Dutz" wrote: >In the cleanup script I simply removed all non Maven related stuff. What >I could do, was to have my IntelliJ to generate an ant build from the >Maven build. Eventually that would get rid of some of the problems if the >old ant build. That might help for the contents of compiler and compiler.jx, although I might learn something by trying to get the old scripts to work. At the top-level, I think I would want to retain the release packaging scripts. If you are busy trying to get the Maven build finalized, I might try to do the Ant build in parallel by copying in old build.xml files and fixing them. I think you are down to four weeks before ApacheCon. -Alex
