So are you using the jar plugin to make another jar artifact and attaching it with the buildhelper? I'm not completely clear what you're trying to do. Maybe post the pom that is creating the artifact?
-----Original Message----- From: Robert Reiner [mailto:[EMAIL PROTECTED] Sent: Saturday, April 05, 2008 8:22 AM To: [email protected] Subject: RE: jar does not attach to reactor? Hello Brian, thank you for your reply! I think I did not make my problem clear... I already follow your hint by using 'unpack-dependencies', so my question is basically how to get artifacts in the reactor, not out of it. But your answer confirms me that I am correctly accessing artifacts from the reactor. I am wondering why I have to use the jar-plugin _and_ the buildhelper-plugin to make the artifact available to the reactor, where the jar-plugin is alone sufficent to (e.g.) deploy the artifact. So my question is: Is there a reason why the jar-plugin does not add the generated artifact to the reactor? I always thought that the reactor is a way to store all created artifacts of the current build to make them available to other modules. Is this true or is there more to know about it? Any documentation availiable? Brian E Fox wrote: > > Using the copy/unpack-dependencies goals should find what you need from > the reactor. The copy/unpack goals currently do not. > -- View this message in context: http://www.nabble.com/jar-does-not-attach-to-reactor--tp16491295s177p165 12393.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
