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 <aha...@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
