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

Jörg Schaible wrote:

>> Alternately we simply fix the m2 POMs - redeploy from 
>> branches and simply retag with -m2 postfix
>> eg 
>> https://svn.codehaus.org/picocontainer/java/picocontainer/tags
>> /picocontainer-1_2-m2
>> (and obviously merge into trunk).
>>
>> Going down the route of MEV tools is IMO more complicated, 
>> more prone to unsuccess,
>> less reproducible from SVN, etc
> 
> It's just for our already released stuff. Just check out e.g. svn://svn.codehaus.org/maven/scm/repository/picocontainer, fix the POM with the wrong info and create an issue for MEV with the patch. They often applied on a daily basis.
> 

Yes - but the process of going through the POMs and fixing all the version variables not replaced
is considerably more work than simply redeploying using m2.   And does not garantee success.
Bearing in mind that we are going to be using a different groupId, eg org.picocontainer instead of 
picocontainer, makes the two releases distinguisable and allows them to co-exist.

Also, once the POMs have dependencies and non-trivial information - consensus has to be reached 
before applying the patch:

http://maven.apache.org/guides/mini/guide-maven-evangelism.html

I don't really understand the objection to fixing the m2 poms in branches, redeploying to 
http://repository.codehaus.org - which will then be synched to ibiblio.
We then merge to trunks - and then keep on supporting both m1 and m2 deployment (to different deploy 
sites and groupId) until we are ready to drop m1 support.

Cheers