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

Paul Hammant <[email protected]>
Newsgroups gmane.comp.java.picocontainer.devel
Message-ID <[email protected]>
Lets just do a redeployment without changing version numbers of  
anything rather than go down the MEV route...

Regards,

- Paul

On Mar 1, 2006, at 8:05 AM, Jörg Schaible wrote:

> Hi Mauro,
>
>> -----Original Message-----
>> From: Mauro Talevi [mailto:[email protected]]
>> Sent: Wednesday, March 01, 2006 12:26 PM
>> To: dev-qxt/[email protected]
>> Subject: Re: [picocontainer-dev] Branches created for
>> released components and m2 support
>>
>> Jörg Schaible wrote:
>>
>>> 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.
>>
>> Yes - m2 POMs use groupId org.(pico/nano)container.
>>
>> Don't see any redirections presently in ibiblio.
>
> There are quite some e.g. spring is redirected (http:// 
> www.ibiblio.org/maven2/org/springframework/), see the old releases  
> there. Just ask Brett.
>
>>>> 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.
>>
>> 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.
>
> - Jörg
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.