I haven't run into this use case, but I would think it should work. Have you
tried other Maven versions like 2.0.x? Also, I would strongly suggest you
try out 3.0-alpha-5. My experience is that errors that I've run into with
the 2.x code is fixed in 3.0.
/Anders
On Mon, Dec 7, 2009 at 23:29, Mike Olson wrote:
>
> Hello,
>
> This is with Maven 2.2.1.
>
> I have an aggregate POM file that contains 2 child projects, say project A
> and project B.
>
> Each of these child projects uses a custom build plugin. Project A calls
> it like
>
>
>
>
> myGrupId
> myArtifactId
> 1.0
>
>
> my-dep-1-group
> my-dep-1-artifactId
> my-dep-1-version
> data
> compile
>
>
>
> param
>
>
>
> EXEC1
> generate-sources
>
> generate-code
>
>
> param2
>
>
>
>
>
>
>
> Basically it invokes a custom MOJO in the generate-sources phase. The
> plugin uses information on the classpath (among other things) to determine
> what code to generate.
>
> Child project 2 has the exact same setup "however" it changes the
> dependency defined in the plugin to be dependent on a different project.
>
> When I build each project individually, they build perfectly fine.
> However, when I build the aggregate project, child project 2 fails because
> it is using the dependencies of the first project. I have verified this
> with various dumps of the class path, etc. I have tried inheriting the
> plugin information, separate plugin definitions in the child project, many
> configurations. It always seems that the first time a plugin is loaded that
> is the classpath used for that plugin whenever it is executed.
>
> Is this a bug? I would have expected the inline dependencies to work just
> like the configuration section of a plugin, basically it is for that
> invocation only.
>
> If this is not a bug, how should I be invoking the same plugin twice, with
> different class paths, within the same build.
>
> Thank
> Mike
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
