RE: [picocontainer-dev] Branches created for released components and m2 support

Hi Mauro, 

> -----Original Message-----
> From: Mauro Talevi [mailto:[email protected]] 
> Sent: Wednesday, March 01, 2006 11:59 AM
> To: dev-qxt/[email protected]
> Subject: [picocontainer-dev] Branches created for released 
> components and m2 support
> 
> Hi folks,
> 
> I've created branches for the released Pico/Nano components.
> 
> https://svn.codehaus.org/picocontainer/java/picocontainer/bran
> ches/picocontainer-1_2
> https://svn.codehaus.org/picocontainer/java/nanocontainer/bran
> ches/nanocontainer-1_0
> https://svn.codehaus.org/picocontainer/java/nanocontainer-nano
> war/branches/nanocontainer-nanowar-1_0
> https://svn.codehaus.org/picocontainer/java/nanocontainer-pers
> istence/branches/nanocontainer-persistence-1_0
> 
> These can be used for bugfix and maintainance releases.

+1

> The first of these should be to support m2 properly.
> 
> We now have an m2-compatible Codehaus repository 
> http://repository.codehaus.org
> 
> I would like to release Pico/Nano to m2 repo and bump up the 
> version to 1.2.1 and 1.0.1
> to avoid possible conflicts - even though they are only POM 
> changes and no "code" changes.
> I'm aware that we'd be using different groupIds but using 
> different versions would make it
> easier to tag in svn and trace changes.

So are you now switching to groupId org.(pico/nano)container? They establish redirections on ibiblio to retrieve even the old versions at the new location.

> Thoughts?

With those redirections I am not sure, if we should release only because we changed our build tool. If the M2 poms of the releases have missing deps or are incorrect, we might use MEV to fix 'em. A new release with nothing's changed seems somewhat strange from a user's PoV. If we supply with such a release also the -javadoc and -src artifacts such a release might be justified though, these artifacts are used in the tool support.

- Jörg