maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mirko Friedenhagen <mfriedenha...@gmail.com>
Subject Re: Accessing *reactor* build path in an Ant-Maven-plugin
Date Wed, 10 Jul 2013 21:26:12 GMT
Hello Russel,

thanks, but how do I specify this in Ant-Mojos?

Regards Mirko
-- 
Sent from my mobile
On Jul 10, 2013 2:37 PM, "Russell Gold" <russ@gold-family.us> wrote:

> Hi Mirko. If you want the compile class path for the pom executing a
> plugin, you can do this:
>
> 1. Configure the plugin to require compile and runtime dependency
> resolution:
>
> @Mojo( ... requiresDependencyResolution =
> ResolutionScope.COMPILE_PLUS_RUNTIME)
>
> 2. Specify a parameter configured to receive project.compileClassElements
>
>    /**
>     * Compile classpath of the maven project.
>     */
>    @Parameter(defaultValue = "${project.compileClasspathElements}")
>    private List<String> projectCompileClasspathElements;
>
> On Jul 10, 2013, at 1:12 AM, Mirko Friedenhagen <mfriedenhagen@gmail.com>
> wrote:
>
> > Hello,
> >
> > I inherited a Maven plugin written by an Ant-master which currently execs
> > mvn dependency:build-classpath to inspect files. (Rewrite almost
> impossible
> > as there are no tests).
> >
> > This leads to problems during the first run of verify (e.g. while
> > release:prepare).
> >
> > Any hint how to get the *reactor* class path would be appreciated :-).
> >
> > Regards Mirko
> > --
> > Sent from my mobile
>
> -----------------
> Come read my webnovel, Take a Lemon <http://www.takealemon.com>,
> and listen to the Misfile radio play <
> http://www.gold-family.us/audio/misfile.html>!
>
>
>
>
>

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