Thank you Brett!
Switching to the package phase did the trick.
Thanks,
Ørjan
Brett Porter wrote:
The active project changes during the reactor build. At the compile
stage, it refers to the target/classes directory. At the package
stage, it points to the jar file. If you are implementing
I have created a plugin which creates a custom distribution of artifacts
built within a multi-project.
Since maven-2.0-beta-3 I've seen that the file property of an
ActiveProjectArtifact has changed from a reference to a jar-file to a
reference of the artifacts target/classes directory.
How
Since I got now responses yet I'll try to clarify:
A plugin that I wrote loops through the dependencies of an artifact
trying to copy jars, wars and special archives into a distribution
directory.
The problem now is that since m2-b3 all artifacts beeing a part of the
current multi-artifact
The active project changes during the reactor build. At the compile
stage, it refers to the target/classes directory. At the package
stage, it points to the jar file. If you are implementing your own
packaging goal, you need to call project.getArtifact().setFile( ... )
to ensure this is used.
-
