We find that a Site report produces a better BOM. The POM, even the *effective* one, often does not list all of the dependencies. We also like Sonar for two-way traceability of dependencies.
________________________________ Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time, 700 times a day > -----Original Message----- > From: Greg Akins [mailto:[email protected]] > Sent: Thursday, June 02, 2011 12:15 PM > To: Maven Users List > Subject: Including Effective pom in .jar metadata > > Is there a way to include the effective pom in the deployed > jar's metadata? > > We're discussing being able to research the "bill of > materials" for a build. And while that information can be > found by examining all the included poms, at a top-level we'd > like to see the effective pom so the information that is > derived from there isn't "hidden" > > Any thoughts? Am I missing something simple? > > -- > Greg Akins > http://twitter.com/akinsgre > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
