The key thing we need to decide here is whether folks who want to develop
using IDEs will need to run a Maven or Ant before importing the projects
into the IDEs and that the IDEs will properly handle regeneration of the
config files. The IDEs currently use config files checked into the repo,
instead of generated by the build.
And we need to decide whether we are going to make such changes before or
after the 0.7.0 release.
-Alex
On 7/7/16, 7:44 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Hi,
>
>
>I just added a new module to the flex-asjs module called "distribution".
>This is a maven module that uses the maven-assembly-plugin to produce
>bundles of software. I am currently trying to make it automatically build
>installable versions of the SDK [1]. It would be cool if you could have a
>look at what I'm producing.
>
>
>Currently the Ant build sort of builds the artifacts in-place. It's sort
>of like living the house while you are building it. Everyone knows - or
>can at least imaging - that's not nice ;-)
>
>
>I think moving the static parts (like run scripts, config files,
>manifests etc.) to the distribution module would clean up the project a
>lot.
>
>
>I think the cleanest option would be to have a completely separate module
>("flex-flexjs" for example) which does the distribution packaging and to
>have it depend on flex-falcon and flex-asjs. This would separate
>compiler, framework and distribution, but that's just my oppinion. I just
>think there's far too much static stuff hanging around in the directories
>and I have no idea what is used for what or if its obsolete.
>
>
>Chris
>
>
>[1]
>https://builds.apache.org/view/E-G/view/Flex/job/flex-asjs%20(maven)/ws/di
>stribution/target/
>
