mvn site runs up to the test phase, it doesn't run the package phase, so
that's why you get just target/classes
On Mon, Apr 11, 2011 at 1:39 AM, Lucas Persson lucas.pers...@oracle.comwrote:
But when I do mvn install on the multiprojet then I will get a JAR but
when doing mvn site on the
But when I do mvn install on the multiprojet then I will get a
JAR but when doing mvn site on the multiproject I get
target/classes.
That seems to be the opposite to what you have described?
/Lucas
On 04/08/2011 07:52 PM, Brian Fox
Hi
I have some issues with the maven-dependency-plugin
vers 2.2 under Maven3.
In one project I uses the plugin to unpack a sources artifact
like this:
plugin
I believe I've run into a similar issue at some time.
However, there are a few things you should understand:
1. An reactor build is executed and for that to work, Maven *should* get
artifacts from the reactor and not the repo
2. executing mvn pmd:pmd will not install any artifacts to the local
Thanks Anders
I note I get the same issue for mvn site when the reports shall be
generated.
I can understand that during a reactor build artifacts shall be
fetched from the build but it does not make scenes that the plugin
tries to use
It's not a hack, the plugin asks maven core to resolve the artifacts and the
objects it gets back have file handles. In reactor builds with sibling
dependencies, those handles point to the sibling target folder. If you do a
compile reactor build, those handles will point to the /target/classes
