the classpath
> too.
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/How-to-add-a-dependency-programmatically-for-the-compile-phase-tp5778954p5779153.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---
;.jar" that needs to be added to the classpath
too.
--
View this message in context:
http://maven.40175.n5.nabble.com/How-to-add-a-dependency-programmatically-for-the-compile-phase-tp5778954p5779153.html
Sent from the Maven - Users mailing l
This is the page is quickly glanced through before replying:
http://blog.sonatype.com/2009/08/create-a-customized-build-process-in-maven/
As I've never written an ArtifactHandler I don't really know what the
limitations are. Maybe there is someone else here who knows more on this?
/Anders
On Th
There are only a few consumers of aar (which is a newish packaging type)
artifacts from a Maven repository.
1. People that build using Maven and our plugin.
2. People that build using Gradle.
3. Building from an IDE like IntelliJ/Eclipse
This solution would appears to solve 1 and probabl
I don't have the code at hands on how to do what you're asking, but I
wanted to stress that changing the dependency list in a plugin will only
affect that list during the build where your plugin is executed. Any
consumers of your artifact (from the repo) will not get this dependency, as
the plugin
Hi,
I would like to know how to add a dependency (such as a jar) into the
project's list of compile time dependencies programmatically within a Mojo.
Benoit should probably have posted this in Maven Users rather than
Maven Dev, so I'm reposting here.
We are developing a Mojo that needs to add som
