I wonder why topics in which I am forced to respond in a lengthy fashion always
pop up when I’m travelling and responding lengthily on my phone is no fun. But
it seems that I must.
You wrote “AFAICT” (after checking the meaning of this) … well the thing is you
are telling wrong. Maven is far more than a simple xml with nodes. Behind every
dependency declared in the pom there are transitive dependencies. Different
ones depending on the type. You can inherit dependencies from parents and have
dependencies in profiles which are activated on checking multiple types of
conditions. Also, you can use dependency management in the pom or in any parent
poms which handles which versions are loaded and how transitive dependencies
are eventually excluded. You can even use properties to configure versions or
other parts. I could keep on going mentioning mechanisms in place here, but I
think this is enough. If you would implement pom handling the way you were
mentioning, this will break the entire Maven integration unless you use Maven
to achieve this. Bundling maven with the compiler is the wrong way and I don’t
see any sense in this.
However, getting rid of the config files would be super-easy if the
configuration system was cleaned up. Then the Maven plugin would configure
everything using Maven (this is ok cause it’s a Maven plugin) and pass in the
configuration into the compiler. Right now, I wouldn’t trust the concurrent
compilation of modules Maven supports as I only managed to clean up parts of
the configs. Much more cleaning up needed here. Solving this problem by adding
another module that needs maintenance is the wrong way.
The Eclipse Aether library has recently been donated to the Maven project,
which is handling the dependency resolutions and soon this will become an
extendable mechanism. As soon as that’s done I can extend the maven plugin to
support Flex’s dependency scopes. Then things would start becoming even more
complex if the mechanism was manually implemented in the compiler.
So, regarding Maven questions … please trust my opinion. The internals of the
compiler are your domain, Maven however is something I do have expertise in and
you should trust me, if I make such suggestions.
Chris
Am 12.05.17, 22:52 schrieb "Christofer Dutz" <christofer.d...@c-ware.de>:
Good luck with that ... LOL
Von meinem Samsung Galaxy Smartphone gesendet.
-------- Ursprüngliche Nachricht --------
Von: Alex Harui <aha...@adobe.com.INVALID>
Datum: 12.05.17 19:03 (GMT-05:00)
An: dev@flex.apache.org
Betreff: Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0
On 5/12/17, 3:27 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Hi Alex,
>
>I think I miss-read the ant thing ... Sorry for that. But I got the
>implementing Maven from the ability to process poms as this would require
>that unless you add a direct dependency to Maven libraries, which I think
>is also a bad idea ... That's what Maven plugins are used for.
AFAICT, a pom.xml is simple XML. I was going to parse the XML looking for
specific nodes. No need for Maven library dependencies, IMO.
-Alex
