Hi,
I think people of TI enviroments would want a tech like this that rely on
maven, but thinking on what people expect to have on his own CI process, we
need to be pure maven (without ANT hacks that would make this not valid).
So my vote is to rely only on maven, since if not it will defeats the maven
main purpose (IMHO).
In local dev machines, if they are building software using FlexJS, they
will config their poms to download FlexJS transparently and then configure
their IDEs, If they work as well on FlexJS, they will build running the
poms.
Regarding original Chris question. If I understand what he is describing, I
think will be normal to have some parent project that bundles some part of
the software and then builds child project. Those kind of problems (egg or
chicken first) use to be very typical in maven builds, so maybe making some
hierarchy of projects that builds first dependant parts could be a good
solution...is that way what you are describing?
2016-07-07 16:54 GMT+02:00 Alex Harui <aha...@adobe.com>:
> 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/
> >
>
>
--
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.
