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.
- Brett On 10/17/05, Orjan Austvold <[EMAIL PROTECTED]> wrote: > 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 build is found to be of the concrete type > ActiveProjectArtifact. > > ActiveProjectArtifacts have no reference to the resulting file of that > artifact (the resulting jar/war/etc...). > > The question is: How can a plugin in a multiproject build resolve an > ActiveProjectArtifact resulting artifact file? > > > Thanks, > Ørjan > > > Orjan Austvold wrote: > > 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 can I retreive a reference to the jar-file of an artifact built in > > the current project? > > > > > > Ørjan > > > > > > -- > Ørjan Austvold - Senior Software Architect > www.colibria.com - putting the presence into messaging > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
