Yeah, a *company* pom even that all Parent POMs load as a parent. I like to nail down everything, to me, it's a build specification and I want it all defined and (self) documented.
________________________________ Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time -----Original Message----- From: Phillip Hellewell [mailto:ssh...@gmail.com] Sent: Wednesday, October 20, 2010 6:51 PM To: Maven Users List Subject: Re: Plugin versions On Wed, Oct 20, 2010 at 4:11 PM, Yanko, Curtis <curt_ya...@uhc.com> wrote: > Try the dependency plugin > > dependency:resolve-plugins Thanks. I also found versions:display-plugin-updates, which was the main one I was trying to remember. I should specify versions for all plugins I'm using in my parent pom, and not just rely on the super pom, right? Phillip --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
