So what we need to do is put together a list of all the components that went into a build (so all the supporting maven plugins) this allows a couple of things:
* reproducability of the build environment [this is required to help us re-construct a build] * knowing what went into a build so if a later plugin breaks we know a good roll back point : this happened to us with a site plugin and it took a lot of work to find a previous version that worked. hth and thanks! -- aman Wendy Smoak-3 wrote: > > On Sat, Oct 11, 2008 at 1:41 PM, aman kohli <[EMAIL PROTECTED]> wrote: >> Thanks for the responses. Unfortunately 'mvn help:effective-pom' does >> not >> quite do what we need it to. Here's an example, trying to get a list of >> all the site plugins and their versions used is a challenge as this is >> not >> covered by effective-pom. > > Do you mean all the available versions of the maven-site-plugin? If > so, the metadata file should list them: > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/ > > If you explain the problem you're trying to solve, (why do you want > this list?) you may get some other suggestions. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Generate-list-of-plugins-and-their-versions-used-in-a-build-tp19895592p19936858.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]
