On Wed, Aug 26, 2009 at 5:38 PM, Jean-Baptiste Onofré<[email protected]> wrote:
> Hi Barrie,
>
> we're working to use only repo1.maven.org and repository.apache.org, at
> least for major releases. Nevertheless, for some development purposes, we
> use our svn m2 repo. When the code is promoted into a release or major
> source code part (like it was the case with servicemix-smpp and jSMPP jar),
> we move and deploy into a major repo.
>
> For woden, I think it's a mistake and we need to move to another woden
> version.

That's good news you plan to use the main repos for releases.
I have no problems with development using internal repos.

I'm not sure if there is an easy way to enforce this policy for releases.
I wonder if the enforcer plugin can be used
http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html

Barrie

Reply via email to