So all I need to do is deploy these as maven artifacts and all's good?
Do you have some sort of dependency tree I could use, or should I simply say:
org.apache.flex:flexjs:0.0.3:pom
- org.apache.flex:binding:0.0.3:swc
- org.apache.flex:charts:0.0.3:swc
- org.apache.flex:collections:0.0.3:swc
- org.apache.flex:core:0.0.3:swc
- org.apache.flex:createjs:0.0.3:swc
- org.apache.flex:dragdrop:0.0.3:swc
- org.apache.flex:effects:0.0.3:swc
...
Or is there something like this:
org.apache.flex:flexjs:0.0.3:pom
- org.apache.flex:charts:0.0.3:swc
- org.apache.flex:binding:0.0.3:swc
- org.apache.flex:core:0.0.3:swc
- org.apache.flex:dragdrop:0.0.3:swc
- org.apache.flex:core:0.0.3:swc
...
I don't want to make it monolithik if it doesn't have to.
Currently I don't mavenize the normal FDK as one monolithic block, I have the
mobile stuff stipped out, the themes, the experimental stuff ... so if there
are any constaints which I can use to partition the artifacts, it would be
great if you could tell me about that. Otherwise I'll stick to the monolithik
approach for now ... after all we can change this with every new release.
Chris
________________________________________
Von: Alex Harui <aha...@adobe.com>
Gesendet: Donnerstag, 7. Mai 2015 18:43
An: dev@flex.apache.org
Betreff: Re: A little help getting up to speed with the latest changes in FlexJS
On 5/7/15, 9:24 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Am I still correct with the assumption, the important stuff is all in
>"frameworks" especially the "libs" directory? I am assuming this as
>FlashBuilder has proven to be quite inflexible with regards to directory
>structures ;-)
>
>
>Do I simply have to mavenize the 15 swcs in that directory? If yes ... is
>there any hierarchy in which they depend on each other? Do I need to
>deploy the stuff in frameworks/as/libs and frameworks/FlexJS/libs? I hope
>not as I could see the swcs in frameworks/libs already contained a lot of
>js.
The 15 swcs should now be in frameworks/libs, not frameworks/as/libs.
Frameworks/js/FlexJS/libs is no longer needed as all of its contents
should be packaged in the various swcs. Frameworks/js/FlexJS/libs still
has a copy of the js just to make it easier to try quick edits of the JS.
Some of the swcs do need to be built before the others. I think Core goes
first, then Binding and Graphics, then HTML, then the rest shouldn’t
matter. You can get a quick view of dependencies via:
grep -r --include=compile-config.xml 'swc' frameworks/
-Alex
