Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration

[Alex Harui]

On 4/23/16, 7:05 AM, "Alex Harui"  wrote:

>
>>
>>Regarding the merge ... I'm ready when you are.
>
>I want to verify the install of a nightly will work.  Might take all
>weekend to get that far.

OK, I think the nightly will work now.  I will take care of merging recent
changes in the develop branch.

-Alex

Re: AW: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration

[Alex Harui]

Every swc in asjs should create a swc for swf and a swc for js with different 
compile flags.  Downstream swcs need the platform specific api.


Sent from my LG G3, an AT 4G LTE smartphone


-- Original message--

From: Christofer Dutz

Date: Sun, Apr 24, 2016 7:42 AM

To: Alex Harui;dev@flex.apache.org;

Subject:AW: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration


Up till now I only have the falcon externs compiling ... they use falcon for 
this.


Are there more externs in the ASJS package?


Chris



Von: Alex Harui <aha...@adobe.com>
Gesendet: Sonntag, 24. April 2016 16:11
An: Christofer Dutz; dev@flex.apache.org
Betreff: Re: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration


Asjs extern swc is written in ActionScript so it uses falcon to compile.  
Doesn't the final phase of flex falcon extern swc also use falcon?


Sent from my LG G3, an AT 4G LTE smartphone


-- Original message--

From: Christofer Dutz

Date: Sun, Apr 24, 2016 3:17 AM

To: dev@flex.apache.org;

Subject:AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration


No I'm still quite far from finished with that. I am coming closer and closer, 
but still I need to do some work. Currently the Core module is not building. 
Haven't had the time to dig into that though cause I was stuck with merging 
falcon stuff.

One thing I did notice two days ago, was that I have to compile ASJS with the 
Flex Tool Group "FlexJS" (that's in falcon-jx) and the externs are compiled 
using the group "Falcon" (that's in falcon). I would have expected the externs 
to be compiled using the falcon-jx compiler as the externs belong to the cross 
compilation tool-chain ... any reason why they don't compile using falcon-jx?

Chris


Von: Alex Harui <aha...@adobe.com>
Gesendet: Samstag, 23. April 2016 18:10
An: dev@flex.apache.org
Betreff: Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration

Forgot to ask...

On 4/23/16, 2:06 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:

>Regarding the double run externc ... I noticed this too ... but I think I
>managed to get everything working with just one pass in the Maven build.
>In order to get things running I compared the output with the final
>output of the Ant JavaScript and re-engineered ALL of the replacement
>operations. So eventually looking at the replacements of the maven build
>could eliminate the need to run externc twice.

OK, I guess I will someday switch to using your replace tools.  I've been
wondering if there is some other way we should be doing this.  Should we
just use patch files instead?

>
>Regarding the merge ... I'm ready when you are.

Are you also done with flex-asjs?  I haven't looked there at all yet.

-Alex

AW: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration

[Christofer Dutz]

Up till now I only have the falcon externs compiling ... they use falcon for 
this.


Are there more externs in the ASJS package?


Chris



Von: Alex Harui <aha...@adobe.com>
Gesendet: Sonntag, 24. April 2016 16:11
An: Christofer Dutz; dev@flex.apache.org
Betreff: Re: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration


Asjs extern swc is written in ActionScript so it uses falcon to compile.  
Doesn't the final phase of flex falcon extern swc also use falcon?


Sent from my LG G3, an AT 4G LTE smartphone


-- Original message--

From: Christofer Dutz

Date: Sun, Apr 24, 2016 3:17 AM

To: dev@flex.apache.org;

Subject:AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration


No I'm still quite far from finished with that. I am coming closer and closer, 
but still I need to do some work. Currently the Core module is not building. 
Haven't had the time to dig into that though cause I was stuck with merging 
falcon stuff.

One thing I did notice two days ago, was that I have to compile ASJS with the 
Flex Tool Group "FlexJS" (that's in falcon-jx) and the externs are compiled 
using the group "Falcon" (that's in falcon). I would have expected the externs 
to be compiled using the falcon-jx compiler as the externs belong to the cross 
compilation tool-chain ... any reason why they don't compile using falcon-jx?

Chris


Von: Alex Harui <aha...@adobe.com>
Gesendet: Samstag, 23. April 2016 18:10
An: dev@flex.apache.org
Betreff: Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration

Forgot to ask...

On 4/23/16, 2:06 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:

>Regarding the double run externc ... I noticed this too ... but I think I
>managed to get everything working with just one pass in the Maven build.
>In order to get things running I compared the output with the final
>output of the Ant JavaScript and re-engineered ALL of the replacement
>operations. So eventually looking at the replacements of the maven build
>could eliminate the need to run externc twice.

OK, I guess I will someday switch to using your replace tools.  I've been
wondering if there is some other way we should be doing this.  Should we
just use patch files instead?

>
>Regarding the merge ... I'm ready when you are.

Are you also done with flex-asjs?  I haven't looked there at all yet.

-Alex

Re: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration

[Alex Harui]

Asjs extern swc is written in ActionScript so it uses falcon to compile.  
Doesn't the final phase of flex falcon extern swc also use falcon?


Sent from my LG G3, an AT 4G LTE smartphone


-- Original message--

From: Christofer Dutz

Date: Sun, Apr 24, 2016 3:17 AM

To: dev@flex.apache.org;

Subject:AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration


No I'm still quite far from finished with that. I am coming closer and closer, 
but still I need to do some work. Currently the Core module is not building. 
Haven't had the time to dig into that though cause I was stuck with merging 
falcon stuff.

One thing I did notice two days ago, was that I have to compile ASJS with the 
Flex Tool Group "FlexJS" (that's in falcon-jx) and the externs are compiled 
using the group "Falcon" (that's in falcon). I would have expected the externs 
to be compiled using the falcon-jx compiler as the externs belong to the cross 
compilation tool-chain ... any reason why they don't compile using falcon-jx?

Chris


Von: Alex Harui <aha...@adobe.com>
Gesendet: Samstag, 23. April 2016 18:10
An: dev@flex.apache.org
Betreff: Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration

Forgot to ask...

On 4/23/16, 2:06 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:

>Regarding the double run externc ... I noticed this too ... but I think I
>managed to get everything working with just one pass in the Maven build.
>In order to get things running I compared the output with the final
>output of the Ant JavaScript and re-engineered ALL of the replacement
>operations. So eventually looking at the replacements of the maven build
>could eliminate the need to run externc twice.

OK, I guess I will someday switch to using your replace tools.  I've been
wondering if there is some other way we should be doing this.  Should we
just use patch files instead?

>
>Regarding the merge ... I'm ready when you are.

Are you also done with flex-asjs?  I haven't looked there at all yet.

-Alex

AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration

[Christofer Dutz]

No I'm still quite far from finished with that. I am coming closer and closer, 
but still I need to do some work. Currently the Core module is not building. 
Haven't had the time to dig into that though cause I was stuck with merging 
falcon stuff.

One thing I did notice two days ago, was that I have to compile ASJS with the 
Flex Tool Group "FlexJS" (that's in falcon-jx) and the externs are compiled 
using the group "Falcon" (that's in falcon). I would have expected the externs 
to be compiled using the falcon-jx compiler as the externs belong to the cross 
compilation tool-chain ... any reason why they don't compile using falcon-jx?

Chris


Von: Alex Harui <aha...@adobe.com>
Gesendet: Samstag, 23. April 2016 18:10
An: dev@flex.apache.org
Betreff: Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration

Forgot to ask...

On 4/23/16, 2:06 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:

>Regarding the double run externc ... I noticed this too ... but I think I
>managed to get everything working with just one pass in the Maven build.
>In order to get things running I compared the output with the final
>output of the Ant JavaScript and re-engineered ALL of the replacement
>operations. So eventually looking at the replacements of the maven build
>could eliminate the need to run externc twice.

OK, I guess I will someday switch to using your replace tools.  I've been
wondering if there is some other way we should be doing this.  Should we
just use patch files instead?

>
>Regarding the merge ... I'm ready when you are.

Are you also done with flex-asjs?  I haven't looked there at all yet.

-Alex

Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration

[Alex Harui]

Forgot to ask...

On 4/23/16, 2:06 AM, "Christofer Dutz"  wrote:

>Regarding the double run externc ... I noticed this too ... but I think I
>managed to get everything working with just one pass in the Maven build.
>In order to get things running I compared the output with the final
>output of the Ant JavaScript and re-engineered ALL of the replacement
>operations. So eventually looking at the replacements of the maven build
>could eliminate the need to run externc twice.

OK, I guess I will someday switch to using your replace tools.  I've been
wondering if there is some other way we should be doing this.  Should we
just use patch files instead?

>
>Regarding the merge ... I'm ready when you are.

Are you also done with flex-asjs?  I haven't looked there at all yet.

-Alex

Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration

[Alex Harui]

On 4/23/16, 2:06 AM, "Christofer Dutz"  wrote:

>
>So you want/did add the source files of swfutils to the falcon projects?
>in what branch did you do that? Can I now remove the dependency to the
>Flex 4.15 SDK?

The Ant script in maven-migration-test downloads certain source files.
They are not checked in.  Not sure how you want to adjust the Maven build.

>
>Regarding the merge ... I'm ready when you are.

I want to verify the install of a nightly will work.  Might take all
weekend to get that far.

-Alex

AW: AW: AW: AW: [FlexJS] Status on Maven migration

[Christofer Dutz]

Aggregating responses to multiple mails:

You couldn't find anything in Maven-central, cause we never released it as 
maven artifact. What I'm doing currently is simply mavenizing the 4.15 FDK and 
referencing the swfutils from there, but that dependency doesn't have any 
further dependencies, but that's just because I didn't model them in the 
mavenizer.

Regarding the double run externc ... I noticed this too ... but I think I 
managed to get everything working with just one pass in the Maven build. In 
order to get things running I compared the output with the final output of the 
Ant JavaScript and re-engineered ALL of the replacement operations. So 
eventually looking at the replacements of the maven build could eliminate the 
need to run externc twice.

So you want/did add the source files of swfutils to the falcon projects? in 
what branch did you do that? Can I now remove the dependency to the Flex 4.15 
SDK?

Regarding the merge ... I'm ready when you are.

Chris


Von: Alex Harui <aha...@adobe.com>
Gesendet: Freitag, 22. April 2016 18:35
An: dev@flex.apache.org
Betreff: Re: AW: AW: AW: [FlexJS] Status on Maven migration

On 4/22/16, 1:11 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:

>I'm currently just pulling the jar from the latest SDK release ...
>anything wrong with that?

IIRC, swfutils may have other dependencies on Flex SDK jars and end up
pulling lots of stuff in, including classes I'm trying to replace with
versions of mxmlc and compc that proxy in to Falcon.  I was able to find
this subset of swfutils that works for both flex-compiler-oem and debugger
and doesn't bring in un-needed stuff.  I couldn't find swfutils in maven
central or a pom.xml for it to see what its dependencies are.

I also found another issue: the externs/createjs project was running
externc twice, once with the js-root option.  I remembered as I was
working on that part of the Ant build that the reason it is called twice
is to "sanitize" the .js files before they are put into the SWC so that
the Google Closure Compiler will correctly use them as externs files.  The
CreateJS source files are brought down, munged with various replace/sed
tasks into a state where ExternC can use them to create .as files, but
later in the workflow, the Google Closure Compiler wants more cleanly
formatted .js files to use as externs during minification/optimization.

So I was thinking of directing the output of the js-root pass to
target/generated-sources/externs, and modifying the compile-as-config.xml
to pick up the  from there.  Is that ok?

Thanks,
-Alex

Re: AW: AW: AW: [FlexJS] Status on Maven migration

[Alex Harui]

By downloading the subset of swfutils, I was able to complete
flex-compiler-oem and debugger.  Next up is to test the "all" target and
then release packaging.

-Alex

On 4/22/16, 10:32 AM, "Alex Harui"  wrote:

>OK, I have finished re-creating the Ant builds for compiler, and
>compiler-jx and externs and pushed those changes.  Hopefully I didn't
>break the Maven build.  AFAIK, I did not change any file locations or
>names.
>
>Since we are downloading externs files, I think I am going to download the
>swfutils files and use those to complete flex-compiler-oem and debugger.
>I'll bake them right into those jars, so no separate swfutils.jar.
>
>FWIW, we could merge now, but the nightly builds would be broken.
>
>-Alex
>
>On 4/22/16, 9:35 AM, "Alex Harui"  wrote:
>
>>
>>
>>On 4/22/16, 1:11 AM, "Christofer Dutz"  wrote:
>>
>>>I'm currently just pulling the jar from the latest SDK release ...
>>>anything wrong with that?
>>
>>IIRC, swfutils may have other dependencies on Flex SDK jars and end up
>>pulling lots of stuff in, including classes I'm trying to replace with
>>versions of mxmlc and compc that proxy in to Falcon.  I was able to find
>>this subset of swfutils that works for both flex-compiler-oem and
>>debugger
>>and doesn't bring in un-needed stuff.  I couldn't find swfutils in maven
>>central or a pom.xml for it to see what its dependencies are.
>>
>>I also found another issue: the externs/createjs project was running
>>externc twice, once with the js-root option.  I remembered as I was
>>working on that part of the Ant build that the reason it is called twice
>>is to "sanitize" the .js files before they are put into the SWC so that
>>the Google Closure Compiler will correctly use them as externs files.
>>The
>>CreateJS source files are brought down, munged with various replace/sed
>>tasks into a state where ExternC can use them to create .as files, but
>>later in the workflow, the Google Closure Compiler wants more cleanly
>>formatted .js files to use as externs during minification/optimization.
>>
>>So I was thinking of directing the output of the js-root pass to
>>target/generated-sources/externs, and modifying the compile-as-config.xml
>>to pick up the  from there.  Is that ok?
>>
>>Thanks,
>>-Alex
>>
>>
>

Re: AW: AW: AW: [FlexJS] Status on Maven migration

[Alex Harui]

OK, I have finished re-creating the Ant builds for compiler, and
compiler-jx and externs and pushed those changes.  Hopefully I didn't
break the Maven build.  AFAIK, I did not change any file locations or
names.

Since we are downloading externs files, I think I am going to download the
swfutils files and use those to complete flex-compiler-oem and debugger.
I'll bake them right into those jars, so no separate swfutils.jar.

FWIW, we could merge now, but the nightly builds would be broken.

-Alex

On 4/22/16, 9:35 AM, "Alex Harui"  wrote:

>
>
>On 4/22/16, 1:11 AM, "Christofer Dutz"  wrote:
>
>>I'm currently just pulling the jar from the latest SDK release ...
>>anything wrong with that?
>
>IIRC, swfutils may have other dependencies on Flex SDK jars and end up
>pulling lots of stuff in, including classes I'm trying to replace with
>versions of mxmlc and compc that proxy in to Falcon.  I was able to find
>this subset of swfutils that works for both flex-compiler-oem and debugger
>and doesn't bring in un-needed stuff.  I couldn't find swfutils in maven
>central or a pom.xml for it to see what its dependencies are.
>
>I also found another issue: the externs/createjs project was running
>externc twice, once with the js-root option.  I remembered as I was
>working on that part of the Ant build that the reason it is called twice
>is to "sanitize" the .js files before they are put into the SWC so that
>the Google Closure Compiler will correctly use them as externs files.  The
>CreateJS source files are brought down, munged with various replace/sed
>tasks into a state where ExternC can use them to create .as files, but
>later in the workflow, the Google Closure Compiler wants more cleanly
>formatted .js files to use as externs during minification/optimization.
>
>So I was thinking of directing the output of the js-root pass to
>target/generated-sources/externs, and modifying the compile-as-config.xml
>to pick up the  from there.  Is that ok?
>
>Thanks,
>-Alex
>
>

Re: AW: AW: AW: [FlexJS] Status on Maven migration

[Alex Harui]

On 4/22/16, 1:11 AM, "Christofer Dutz"  wrote:

>I'm currently just pulling the jar from the latest SDK release ...
>anything wrong with that?

IIRC, swfutils may have other dependencies on Flex SDK jars and end up
pulling lots of stuff in, including classes I'm trying to replace with
versions of mxmlc and compc that proxy in to Falcon.  I was able to find
this subset of swfutils that works for both flex-compiler-oem and debugger
and doesn't bring in un-needed stuff.  I couldn't find swfutils in maven
central or a pom.xml for it to see what its dependencies are.

I also found another issue: the externs/createjs project was running
externc twice, once with the js-root option.  I remembered as I was
working on that part of the Ant build that the reason it is called twice
is to "sanitize" the .js files before they are put into the SWC so that
the Google Closure Compiler will correctly use them as externs files.  The
CreateJS source files are brought down, munged with various replace/sed
tasks into a state where ExternC can use them to create .as files, but
later in the workflow, the Google Closure Compiler wants more cleanly
formatted .js files to use as externs during minification/optimization.

So I was thinking of directing the output of the js-root pass to
target/generated-sources/externs, and modifying the compile-as-config.xml
to pick up the  from there.  Is that ok?

Thanks,
-Alex

Re: AW: AW: AW: [FlexJS] Status on Maven migration

[Alex Harui]

On 4/22/16, 6:26 AM, "Christofer Dutz"  wrote:

>Ok ... so the hint with the no longer excluded stuff was good ... wonder
>why I didn't see those changes ... oh well ... builds are back to "blue",
>so Alex feel free to do stuff.
>
>But it keeps on getting more and more difficult to keep the branches in
>sync ... would be happy to do the move soon.

Me too.  Once I get the Ant build working (or close to working), it will
be time to merge the branch.


>But I would like to do one rearrangement.
>
>Any objections to move the falcon and falcon-jx modules under a
>"compiler" directory? I would like to have 3 directories in the end
>"utils", "compiler" and "externs". Each reflecting on major part of the
>build. 

How does this help us?  Keep in mind that compiler may some day ship as a
release without compiler-jx (but packaged with debugger and
flex-compiler-oem) if it becomes useful for regular Flex SDK customers.
In my mind, compiler-jx is downstream.


>If it was possible I would like to link in the asjs repo inside a
>"framework" directory.

What are the benefits of doing that?  Again, there is the possibility that
there are release packages without the flex-asjs/frameworks SWCs.  Also,
there seems to be enough anti-git-submodule articles to make it onto the
first page of search results.

>
>The old build sort of had the structure of the final SDK, I would
>replicate this using Mavens assembly mechanism. Then finished sdks would
>end up in the  target directory of the assembly module. The final
>structure would be like this:

Do Maven customers actually care about the structure being like an SDK?  I
think we can teach the Installer ant script to do the assembly.

-Alex

AW: AW: AW: [FlexJS] Status on Maven migration

[Christofer Dutz]

Ok ... so the hint with the no longer excluded stuff was good ... wonder why I 
didn't see those changes ... oh well ... builds are back to "blue", so Alex 
feel free to do stuff.

But it keeps on getting more and more difficult to keep the branches in sync 
... would be happy to do the move soon. But I would like to do one 
rearrangement.

Any objections to move the falcon and falcon-jx modules under a "compiler" 
directory? I would like to have 3 directories in the end "utils", "compiler" 
and "externs". Each reflecting on major part of the build. If it was possible I 
would like to link in the asjs repo inside a "framework" directory.

The old build sort of had the structure of the final SDK, I would replicate 
this using Mavens assembly mechanism. Then finished sdks would end up in the  
target directory of the assembly module. The final structure would be like this:

/utils
/utils/compiler-build-tools
/utils/compiler-jburg-types
/utils/flexjs-maven-plugin (Will move code from here to a dedicated 
flex-maven-plugin repo as soon as it's there)
/compiler
/compiler/compiler
/compiler/compiler-jx
/compiler/flex-compiler-oem
/compiler/debugger
/externs
/externs/cordova
/externs/createjs
/externs/GCL
/externs/google_maps
/externs/jasmine
/externs/jquery
/externs/js
/externs/node
(framework is linked in using Git 
https://git-scm.com/book/en/v2/Git-Tools-Submodules)
/framework
/framework/Binding
/framework/Charts
/framework/Collections
/framework/Core
/framework/CreateJS
/framework/...

What do you think?

Chris


Von: Christofer Dutz <christofer.d...@c-ware.de>
Gesendet: Freitag, 22. April 2016 10:11
An: dev@flex.apache.org
Betreff: AW: AW: AW: [FlexJS] Status on Maven migration

I'm currently just pulling the jar from the latest SDK release ... anything 
wrong with that?

Haven't worked on the debugger yet as I was going to migrate the non-essential 
parts after finishing the essential parts.

Chris


Von: Alex Harui <aha...@adobe.com>
Gesendet: Donnerstag, 21. April 2016 23:00
An: dev@flex.apache.org
Betreff: 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" <aha...@adobe.com> 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" <aha...@adobe.com> wrote:
>
>>
>>
>>On 4/21/16, 1:38 AM, "Christofer Dutz" <christofer.d...@c-ware.de> 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 thi

AW: AW: AW: [FlexJS] Status on Maven migration

[Christofer Dutz]

I'm currently just pulling the jar from the latest SDK release ... anything 
wrong with that?

Haven't worked on the debugger yet as I was going to migrate the non-essential 
parts after finishing the essential parts.

Chris


Von: Alex Harui <aha...@adobe.com>
Gesendet: Donnerstag, 21. April 2016 23:00
An: dev@flex.apache.org
Betreff: 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" <aha...@adobe.com> 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" <aha...@adobe.com> wrote:
>
>>
>>
>>On 4/21/16, 1:38 AM, "Christofer Dutz" <christofer.d...@c-ware.de> 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
>>
>

AW: AW: AW: [FlexJS] Status on Maven migration

[Christofer Dutz]

If you are doing anything ... use the feature/maven-migration-test branch as 
this is the one with the checked in movement changes. I found out that I could 
merge in changes form develop even if the structure has changed, so this is 
what I'm currently working on.

Chris


Von: Alex Harui <aha...@adobe.com>
Gesendet: Freitag, 15. April 2016 08:09
An: dev@flex.apache.org
Betreff: Re: AW: AW: [FlexJS] Status on Maven migration

On 4/14/16, 10:44 PM, "Christofer Dutz" <christofer.d...@c-ware.de> 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