maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Hammar <>
Subject Re: How to add a dependency programmatically for the compile phase?
Date Fri, 20 Dec 2013 14:22:17 GMT
Well, it doesn't talk about the solution you're talking about, which I
pointed out in my initial mail.
The solution I had in mind, but don't really know if it is doable, would be
to have a custom packaging type (which is packaged as a plugin as explained
in the article) which would map to the .aar file type. It would then have
an ArtifactHandler which would then do the magic you're asking about.

BUT, I don't know if this works.

How would this work if Maven was not used? How would the compiler be able
to read/use the jar in the aar file? Is it a special classloader?

I was about to point you at Manfred, but I found a thread where I see that
you're already working with him. :-)


On Fri, Dec 20, 2013 at 2:43 PM, Benoit Billington <> wrote:

> Thanks Anders but unfortunately the content of that article didn't talk
> about
> the thing we need. which is adding content of a dependency to the
> classpath.
> This article is talking about supporting new extensions which we already do
> by supporting aar.
>  But an ".aar" contains a ".jar" that needs to be added to the classpath
> too.
> --
> View this message in context:
> Sent from the Maven - Users mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message