Hello,
Your first two points proves that Chas is right. Maven 2 is not stable
(and lacks documentation), I agree with this. But it is still a great
tool and I hope it will be improved in the near future.
> Chas, i feel your pains, so here a list of my own recommendations:
>
> 1. Get a maven-proxy in place, so when a central repo is down, you can
> switch to
> a another mirror without user notice. Set up maven-proxy is not that
> hard ;-)
> check out archive list for all maven-proxy discussion. Feel free to
> ping us for help
>
> 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.
>
> This settup will prevent most of maven's uncertainties that others and I
> have gone thru
--
Best regards,
Wojciech Gdela.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
