flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: AW: AW: AW: AW: AW: [FlexJS] Maven-friendly folders
Date Mon, 11 Jan 2016 21:00:39 GMT
I have started on this rename.  I have reworked the
frameworks/project/Core folder and pushed it to a new branch called
"mavenfolders".  Please take a look and provide feedback.  I'll do HTML
next.  Then I'll proceed on the other folders.

Thanks,
-Alex

On 12/21/15, 7:48 AM, "Alex Harui" <aharui@adobe.com> wrote:

>OK.  I think we have a plan.
>
>My goal for the holiday break is to fix as many bugs as I can.  If I get
>through the ones I know about, then I'll start on this.  I'll probably
>just do the Core and HTML folders and get your ok before doing the rest.
>
>I'll also look at the BlazeDS ant script.
>
>Thanks,
>-Alex 
>
>On 12/21/15, 1:18 AM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:
>
>>>>src/main/resources/compile-asjs-config.xml and
>>>>src/main/resources/compile-config.xml are build scripts too and should
>>>>reside in the root of the module alongside the build.xml.
>>>
>>>These -config files aren't Ant scripts, but rather more like
>>>flex-config.xml.  Should they still go in src/main/resources?
>>
>>They definitely bekong in "src/main/resources" in that case.
>>
>>
>>________________________________________
>>Von: Alex Harui <aharui@adobe.com>
>>Gesendet: Montag, 21. Dezember 2015 09:17
>>An: dev@flex.apache.org
>>Betreff: Re: AW: AW: AW: AW: [FlexJS] Maven-friendly folders
>>
>>On 12/19/15, 3:37 AM, "Christofer Dutz" <christofer.dutz@c-ware.de>
>>wrote:
>>
>>>Ok .. so the build.xml shouldn't be in src/test/flex as ist's not
>>>test-code, but the ant script running the tests ... it should be in the
>>>root of the module.
>>
>>That build.xml is the Ant script for the tests.  It gets called by the
>>root build.xml which I guess I forgot to list.  Is it ok to have
>>build.xml
>>files elsewhere in the folder tree besides root?
>>
>>>
>>>src/main/resources/compile-asjs-config.xml and
>>>src/main/resources/compile-config.xml are build scripts too and should
>>>reside in the root of the module alongside the build.xml.
>>
>>These -config files aren't Ant scripts, but rather more like
>>flex-config.xml.  Should they still go in src/main/resources?
>>
>>>
>>>By the way .. I got the ok to re-relase the jburg lib in a version that
>>>works with java 1.6 and 1.7. I will probably do that during the
>>>holidays.
>>
>>Yay!
>>
>>>
>>>Would this be a valid option if you started moving things and adjusting
>>>the ant build to those changes and then I would try to setup a maven
>>>build in parallel and we could streamline any adjustments needed? As the
>>>pom.xml would simply reside next to the ant script I don't think there's
>>>a need to create a branch for this ...
>>
>>Yes, sound like a good plan, once I truly understand where everything
>>should go.
>>
>>-Alex
>>
>>>
>>>________________________________________
>>>Von: Alex Harui <aharui@adobe.com>
>>>Gesendet: Samstag, 19. Dezember 2015 01:27
>>>An: dev@flex.apache.org
>>>Betreff: Re: AW: AW: AW: [FlexJS] Maven-friendly folders
>>>
>>>OK, not sure how easy this will be to read, but below is a snippet of a
>>>current SWC folder listing and what I think should be the new folders.
>>>I'm not sure what to do with the output of the flexunit tests.
>>>
>>>---- current listing -----
>>>
>>>.actionScriptProperties
>>>.flexLibProperties
>>>... and other hidden FB Project files
>>>
>>>as/defaults.css
>>>as/src
>>>as/src/HTMLClasses.as
>>>as/src/org
>>>as/src/org/apache
>>>as/src/org/apache/flex
>>>as/src/org/apache/flex/core
>>>as/src/org/apache/flex/core/IScrollingLayoutParent.as
>>>as/src/org/apache/flex/html
>>>as/src/org/apache/flex/html/accessories
>>>as/src/org/apache/flex/html/accessories/NumericOnlyTextInputBead.as
>>>as/src/org/apache/flex/html/Alert.as
>>>... and other AS source
>>>
>>>as/tests
>>>as/tests/build.xml
>>>as/tests/FlexUnitFlexJSApplication.mxml
>>>as/tests/FlexUnitFlexJSApplication.swf
>>>as/tests/flexUnitTests
>>>as/tests/flexUnitTests/DataGridColumnTester.as
>>>as/tests/flexUnitTests/DataGridColumnTesterTest.as
>>>as/tests/out
>>>as/tests/out/html
>>>as/tests/out/html/all-tests.html
>>>as/tests/out/html/allclasses-frame.html
>>>as/tests/out/html/alltests-errors.html
>>>as/tests/out/html/alltests-fails.html
>>>as/tests/out/html/alltests-skipped.html
>>>as/tests/out/html/flexUnitTests
>>>as/tests/out/html/flexUnitTests/0_DataGridColumnTesterTest.html
>>>as/tests/out/html/flexUnitTests/package-frame.html
>>>as/tests/out/html/flexUnitTests/package-summary.html
>>>as/tests/out/html/index.html
>>>as/tests/out/html/overview-frame.html
>>>as/tests/out/html/overview-summary.html
>>>as/tests/out/html/stylesheet.css
>>>as/tests/out/TEST-flexUnitTests.DataGridColumnTesterTest.xml
>>>as/tests/out/TESTS-TestSuites.xml
>>>
>>>basic-as-manifest.xml
>>>basic-manifest.xml
>>>... and other manifests
>>>
>>>build.xml
>>>compile-asjs-config.xml
>>>compile-config.xml
>>>
>>>js/out/HTMLClasses.js
>>>js/out/org
>>>js/out/org/apache
>>>js/out/org/apache/flex
>>>js/out/org/apache/flex/html
>>>js/out/org/apache/flex/html/accessories
>>>js/out/org/apache/flex/html/accessories/NumericOnlyTextInputBead.js
>>>js/out/org/apache/flex/html/Alert.js
>>>
>>>---- end current listing -----
>>>---- proposed listing ------
>>>.actionScriptProperties
>>>.flexLibProperties
>>>... and other hidden FB Project files
>>>
>>>src/main/resources/defaults.css
>>>src/main/flex
>>>src/main/flex/HTMLClasses.as
>>>src/main/flex/org
>>>src/main/flex/org/apache
>>>src/main/flex/org/apache/flex
>>>src/main/flex/org/apache/flex/core
>>>src/main/flex/org/apache/flex/core/IScrollingLayoutParent.as
>>>src/main/flex/org/apache/flex/html
>>>src/main/flex/org/apache/flex/html/accessories
>>>src/main/flex/org/apache/flex/html/accessories/NumericOnlyTextInputBead.
>>>a
>>>s
>>>src/main/flex/org/apache/flex/html/Alert.as
>>>... and other AS source
>>>
>>>
>>>src/test/flex/build.xml
>>>src/test/flex/FlexUnitFlexJSApplication.mxml
>>>src/test/flex/FlexUnitFlexJSApplication.swf
>>>src/test/flex/flexUnitTests
>>>src/test/flex/flexUnitTests/DataGridColumnTester.as
>>>src/test/flex/flexUnitTests/DataGridColumnTesterTest.as
>>>src/test/flex/out
>>>src/test/flex/out/html
>>>src/test/flex/out/html/all-tests.html
>>>src/test/flex/out/html/allclasses-frame.html
>>>src/test/flex/out/html/alltests-errors.html
>>>src/test/flex/out/html/alltests-fails.html
>>>src/test/flex/out/html/alltests-skipped.html
>>>src/test/flex/out/html/flexUnitTests
>>>src/test/flex/out/html/flexUnitTests/0_DataGridColumnTesterTest.html
>>>src/test/flex/out/html/flexUnitTests/package-frame.html
>>>src/test/flex/out/html/flexUnitTests/package-summary.html
>>>src/test/flex/out/html/index.html
>>>src/test/flex/out/html/overview-frame.html
>>>src/test/flex/out/html/overview-summary.html
>>>src/test/flex/out/html/stylesheet.css
>>>src/test/flex/out/TEST-flexUnitTests.DataGridColumnTesterTest.xml
>>>src/test/flex/out/TESTS-TestSuites.xml
>>>
>>>src/main/resources/basic-as-manifest.xml
>>>src/main/resources/basic-manifest.xml
>>>... and other manifests
>>>
>>>build.xml
>>>src/main/resources/compile-asjs-config.xml
>>>src/main/resources/compile-config.xml
>>>
>>>target/generated-sources/flexjs/HTMLClasses.js
>>>target/generated-sources/flexjs/org
>>>target/generated-sources/flexjs/org/apache
>>>target/generated-sources/flexjs/org/apache/flex
>>>target/generated-sources/flexjs/org/apache/flex/html
>>>target/generated-sources/flexjs/org/apache/flex/html/accessories
>>>target/generated-sources/flexjs/org/apache/flex/html/accessories/Numeric
>>>O
>>>n
>>>l
>>>yTextInputBead.js
>>>target/generated-sources/flexjs/org/apache/flex/html/Alert.js
>>>
>>>---- end proposed listing -----
>>>
>>>
>>>Feel free to make changes.
>>>
>>>Thanks,
>>>-Alex
>>>
>>>
>>>
>>>
>>>On 12/18/15, 4:03 PM, "Christofer Dutz" <christofer.dutz@c-ware.de>
>>>wrote:
>>>
>>>>Well for example Flexmojos has a built in generator based upon
>>>>graniteds
>>>>... the jaxb plugin generates code, antlr and there is a vast number of
>>>>other code generators ... each one would generate its code into:
>>>>
>>>>target/generated-sources/flexmojos
>>>>target/generated-sources/jaxb
>>>>target/generated-sources/antlr
>>>>...
>>>>
>>>>Chris
>>>>
>>>>-----Ursprüngliche Nachricht-----
>>>>Von: Alex Harui [mailto:aharui@adobe.com]
>>>>Gesendet: Freitag, 18. Dezember 2015 16:59
>>>>An: dev@flex.apache.org
>>>>Betreff: Re: AW: AW: [FlexJS] Maven-friendly folders
>>>>
>>>>What is a "generator-name"?  Like FalconJX or swc and js?
>>>>
>>>>Do you know what artifact-id's you want to use for FlexJS?
>>>>
>>>>It could be a big change to add versions to the name of the SWC.  Is
>>>>that
>>>>a requirement in Maven?
>>>>
>>>>Thanks,
>>>>-Alex
>>>>
>>>>On 12/18/15, 1:12 AM, "Christofer Dutz" <christofer.dutz@c-ware.de>
>>>>wrote:
>>>>
>>>>>Well for generated sources, they usually go to
>>>>>"target/generated-sources/{generator-name}" or
>>>>>"target/generated-test-sources/{generator-name}" ... at least this is
>>>>>what the most ides seem to directly support.
>>>>>
>>>>>Chris
>>>>>
>>>>>________________________________________
>>>>>Von: carlos.rovira@gmail.com <carlos.rovira@gmail.com> im Auftrag
von
>>>>>Carlos Rovira <carlos.rovira@codeoscopic.com>
>>>>>Gesendet: Donnerstag, 17. Dezember 2015 18:23
>>>>>An: dev@flex.apache.org
>>>>>Betreff: Re: AW: [FlexJS] Maven-friendly folders
>>>>>
>>>>>Hi Chris,
>>>>>
>>>>>maybe Alex is referring to generated "output", isn't it?
>>>>>
>>>>>in maven is normal to see the standard "target" where all the
>>>>>generation output is done (and could be separated in folders as "lib",
>>>>>"js", "swc"
>>>>>and
>>>>>so on...
>>>>>
>>>>>make this sense?
>>>>>
>>>>>thanks
>>>>>
>>>>>Carlos
>>>>>
>>>>>
>>>>>2015-12-17 17:31 GMT+01:00 Christofer Dutz
>>>>><christofer.dutz@c-ware.de>:
>>>>>
>>>>>> Well In maven you have
>>>>>>
>>>>>> src/main/... For the actual code
>>>>>> src/test/... For stuff needed to run unit tests src/it/... (Not
>>>>>>quite
>>>>>> standard yet, but probably the standard for
>>>>>> integration-tests)
>>>>>>
>>>>>> Also site stuff for the automatically generated maven project
>>>>>> documentation, ....
>>>>>>
>>>>>> So yes ... there is more stuff to go in there ....:-)
>>>>>>
>>>>>> Regarding the output ... I would like the maven default:
>>>>>> Classes and filtered resources go to "target/classes"
>>>>>> The jars are bundled at "target/{artifact-id}-{version}.jar"
>>>>>> or in case of flex "target/{artifact-id}-{version}.swc" (or swf ...
>>>>>> or
>>>>>> both)
>>>>>>
>>>>>> Chris
>>>>>>
>>>>>> ________________________________________
>>>>>> Von: Alex Harui <aharui@adobe.com>
>>>>>> Gesendet: Donnerstag, 17. Dezember 2015 16:45
>>>>>> An: dev@flex.apache.org
>>>>>> Betreff: Re: AW: [FlexJS] Maven-friendly folders
>>>>>>
>>>>>> One folder is better for Flash Builder debugging as well.  So, the
>>>>>> decision is:
>>>>>>
>>>>>>         src/main/flex
>>>>>>
>>>>>> Just curious, does anything else ever go in src or is there always
>>>>>> just one "main" folder?
>>>>>>
>>>>>> Now, what about the output folder?  Currently crossed compiled stuff
>>>>>>goes  in js/out.  Should it go somewhere else?  And while we're at
>>>>>>it,
>>>>>>the SWC  actually goes in ../../libs so all swcs get gathered in one
>>>>>>place.  Is  that ok for Maven builds?
>>>>>>
>>>>>> Thanks,
>>>>>> -Alex
>>>>>>
>>>>>> On 12/17/15, 3:38 AM, "Christofer Dutz" <christofer.dutz@c-ware.de>
>>>>>>wrote:
>>>>>>
>>>>>> >Me too as this requires less adjusting of Flexmojos ;-)
>>>>>> >
>>>>>> >Chris
>>>>>> >
>>>>>> >________________________________________
>>>>>> >Von: carlos.rovira@gmail.com <carlos.rovira@gmail.com>
im Auftrag
>>>>>> >von Carlos Rovira <carlos.rovira@codeoscopic.com>
>>>>>> >Gesendet: Donnerstag, 17. Dezember 2015 11:55
>>>>>> >An: dev@flex.apache.org
>>>>>> >Betreff: Re: [FlexJS] Maven-friendly folders
>>>>>> >
>>>>>> >maybe b) should be better, since I think 2 folders could be a
bit
>>>>>>of
>>>>>> >a nightmare. So I vote for a unique "flex" folder
>>>>>> >
>>>>>> >2015-12-17 11:33 GMT+01:00 Christofer Dutz
>>>>>><christofer.dutz@c-ware.de>:
>>>>>> >
>>>>>> >> Well if there is .as and .mxml I could vote for one of these
two
>>>>>> >>options:
>>>>>> >>
>>>>>> >> a) src/main/as and src/main/mxml
>>>>>> >> b) src/main/flex
>>>>>> >>
>>>>>> >> The "src/main/resources" is the default in Maven ... if
there are
>>>>>> >>no  resources, the directory isn't either. Just if there
are
>>>>>>static
>>>>>> >>resources,  they should go in there.
>>>>>> >>
>>>>>> >> Chris
>>>>>> >>
>>>>>> >> ________________________________________
>>>>>> >> Von: carlos.rovira@gmail.com <carlos.rovira@gmail.com>
im Auftrag
>>>>>> >> von Carlos Rovira <carlos.rovira@codeoscopic.com>
>>>>>> >> Gesendet: Donnerstag, 17. Dezember 2015 11:19
>>>>>> >> An: dev@flex.apache.org
>>>>>> >> Betreff: Re: [FlexJS] Maven-friendly folders
>>>>>> >>
>>>>>> >> Just was thinking on that. Thanks Chris to rise the
>>>>>>mvn-like-folders! :)
>>>>>> >>
>>>>>> >> the four paths are needed in maven.
>>>>>> >>
>>>>>> >> Regarding "as" vs "flex", is hard to decide. both seems
ok to me.
>>>>>>Maybe
>>>>>> >> "flex" has more meaning...but "as" refers to the extension
of the
>>>>>> >>language  (and this should make us think in what happens
to
>>>>>> >>".mxml", should we have
>>>>>> >> /mxml?)
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> 2015-12-17 11:07 GMT+01:00 Christofer Dutz
>>>>>><christofer.dutz@c-ware.de>:
>>>>>> >>
>>>>>> >> > Well if we wanted to go more in the direction of a
>>>>>> >> > Maven-firendly structure, it would probably be:
>>>>>> >> >
>>>>>> >> > - src/main/as (or src/main/flex or src/main/flexjs
... don't
>>>>>> >> > know
>>>>>> >>what we
>>>>>> >> > want to call the highest level ... I don't really care
as long
>>>>>> >> > as
>>>>>>we
>>>>>> >> stick
>>>>>> >> > to the decision)
>>>>>> >> > - src/main/resources (for config file, static resources
etc.)
>>>>>> >> > - src/test/as (for test code)
>>>>>> >> > - src/test/resources (for resources needed during tests)
>>>>>> >> >
>>>>>> >> > I personally would prefer "src/main/flex" and src/test/flex"
as
>>>>>> >> > I
>>>>>> >>think
>>>>>> >> > that we also have mxml and that is not as but both
sort of "are
>>>>>>flex"
>>>>>> >>...
>>>>>> >> > what do you think?
>>>>>> >> >
>>>>>> >> > Chris
>>>>>> >> >
>>>>>> >> > ________________________________________
>>>>>> >> > Von: Alex Harui <aharui@adobe.com>
>>>>>> >> > Gesendet: Donnerstag, 17. Dezember 2015 09:18
>>>>>> >> > An: dev@flex.apache.org
>>>>>> >> > Betreff: [FlexJS] Maven-friendly folders
>>>>>> >> >
>>>>>> >> > Hi,
>>>>>> >> >
>>>>>> >> > Now that all JS files are generated via cross-compiling,
the
>>>>>> >> > folder structure in each SWC project currently looks
like:
>>>>>> >> >
>>>>>> >> > SWCFolder/as/src  -- The source code
>>>>>> >> >          /as/tests -- Any FlexUnit tests
>>>>>> >> >          /js/out  -- The cross-compiled output
>>>>>> >> >          *-manifest.xml -- The MXML manifests
>>>>>> >> >          compile-config.xml -- config file for SWF
>>>>>> >> >          compile-asjs-config.xml -- config file for
JS
>>>>>> >> >          build.xml  -- The Ant build script
>>>>>> >> >
>>>>>> >> > I don't think we need the "as" folder level.  We had
it since
>>>>>>we
>>>>>>used
>>>>>> >>to
>>>>>> >> > have a js/src and wanted to distinguish between languages
in
>>>>>>the
>>>>>> >>sources,
>>>>>> >> > so I was thinking we'd bring the as/src and as/tests
folder to
>>>>>> >> > the
>>>>>>top
>>>>>> >> > level as in:
>>>>>> >> >
>>>>>> >> > SWCFolder/src  -- The source code
>>>>>> >> >          /tests -- Any FlexUnit tests
>>>>>> >> >
>>>>>> >> > and I'm wondering if there is some other organization
of
>>>>>>folders
>>>>>>that
>>>>>> >> > might be more Maven-friendly.
>>>>>> >> >
>>>>>> >> > Thoughts?  I'm shutting down for tonight.  Will check
back in
>>>>>>my
>>>>>> >>morning.
>>>>>> >> >
>>>>>> >> > -Alex
>>>>>> >> >
>>>>>> >> >
>>>>>> >>
>>>>>> >>
>>>>>> >> --
>>>>>> >>
>>>>>> >> Carlos Rovira
>>>>>> >> Director General
>>>>>> >> M: +34 607 22 60 05
>>>>>> >> http://www.codeoscopic.com
>>>>>> >> http://www.avant2.es
>>>>>> >>
>>>>>> >>
>>>>>> >> Este mensaje se dirige exclusivamente a su destinatario
y puede
>>>>>>contener
>>>>>> >> información privilegiada o confidencial. Si ha recibido
este
>>>>>> >> mensaje
>>>>>>por
>>>>>> >> error, le rogamos que nos lo comunique inmediatamente por
esta
>>>>>> >>misma vía y  proceda a su destrucción.
>>>>>> >>
>>>>>> >> De la vigente Ley Orgánica de Protección de Datos (15/1999),
le
>>>>>> >>comunicamos  que sus datos forman parte de un fichero cuyo
>>>>>> >>responsable es
>>>>>>CODEOSCOPIC
>>>>>> >> S.A. La finalidad de dicho tratamiento es facilitar la prestación
>>>>>> >>del  servicio o información solicitados, teniendo usted
derecho de
>>>>>> >>acceso,  rectificación, cancelación y oposición de sus
datos
>>>>>> >>dirigiéndose a nuestras  oficinas c/ Paseo de la Habana
9-11,
>>>>>> >>28036, Madrid con la
>>>>>>documentación
>>>>>> >> necesaria.
>>>>>> >>
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >--
>>>>>> >
>>>>>> >Carlos Rovira
>>>>>> >Director General
>>>>>> >M: +34 607 22 60 05
>>>>>> >http://www.codeoscopic.com
>>>>>> >http://www.avant2.es
>>>>>> >
>>>>>> >
>>>>>> >Este mensaje se dirige exclusivamente a su destinatario y puede
>>>>>>contener
>>>>>> >información privilegiada o confidencial. Si ha recibido este
>>>>>>mensaje
>>>>>>por
>>>>>> >error, le rogamos que nos lo comunique inmediatamente por esta
>>>>>>misma
>>>>>>vía y
>>>>>> >proceda a su destrucción.
>>>>>> >
>>>>>> >De la vigente Ley Orgánica de Protección de Datos (15/1999),
le
>>>>>> >comunicamos que sus datos forman parte de un fichero cuyo
>>>>>> >responsable es
>>>>>>CODEOSCOPIC
>>>>>> >S.A. La finalidad de dicho tratamiento es facilitar la prestación
>>>>>> >del servicio o información solicitados, teniendo usted derecho
de
>>>>>> >acceso, rectificación, cancelación y oposición de sus datos
>>>>>> >dirigiéndose a nuestras oficinas c/ Paseo de la Habana 9-11,
28036,
>>>>>> >Madrid con la documentación necesaria.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>--
>>>>>
>>>>>Carlos Rovira
>>>>>Director General
>>>>>M: +34 607 22 60 05
>>>>>http://www.codeoscopic.com
>>>>>http://www.avant2.es
>>>>>
>>>>>
>>>>>Este mensaje se dirige exclusivamente a su destinatario y puede
>>>>>contener información privilegiada o confidencial. Si ha recibido este
>>>>>mensaje por error, le rogamos que nos lo comunique inmediatamente por
>>>>>esta misma vía y proceda a su destrucción.
>>>>>
>>>>>De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>>>>>comunicamos que sus datos forman parte de un fichero cuyo responsable
>>>>>es CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la
>>>>>prestación del servicio o información solicitados, teniendo usted
>>>>>derecho de acceso, rectificación, cancelación y oposición de sus datos
>>>>>dirigiéndose a nuestras oficinas c/ Paseo de la Habana 9-11, 28036,
>>>>>Madrid con la documentación necesaria.
>>>>
>>
>

Mime
View raw message