2. He means, download a given plugin's code from the public repo, build it yourself, and deploy it into your own corporate repo with a real version. Don't use snapshots.
3. Again (I believe) he is just talking about locking down versions. Wayne On 5/25/06, Adam Hardy <[EMAIL PROTECTED]> wrote:
Dan, Can you elaborate a little on your point (2)? What do you specify as a dependency or plugin version for a particular revision that you deployed on your internal repo? For (3), do you mean specifying a version number, or something more? Regards Adam -----Original Message----- From: dan tran [mailto:[EMAIL PROTECTED] Sent: 25 May 2006 17:51 To: Maven Users List Subject: Re: Rant (very long) 2. Dont use snapshot, cut a release yourself. I fetch the source and post fix the version with svn revision number. For example, if I need a feature/bug fix in maven-assembly-plugin version 2.2-snapshot, then I build 2.2-${svn.revision} and deploy to your internal repository that can serve by maven-proxy. 3. Use pluginManagement to specify all plugins that used by your project'poms. This get your team's build much faster since it does not have to go to maven-proxy to look for daily update. --------------------------------------------------------------------- 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]
