Re: Guide for relocating artifacts from one groupId to another

2006-07-09 Thread Dennis Lundberg
Committed the proposed changes in http://svn.apache.org/viewvc?view=rev&revision=420352 -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Guide for relocating artifacts from one groupId to another

2006-07-09 Thread Carlos Sanchez
On 7/9/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Carlos Sanchez wrote: > Some comments Thanks! > - add SHA1 checksums where you mention MD5. Maven2 uses first SHA1 if > present Will do that. > - Maven2 to Maven 2 / Releasing the next version > > When the next release of <<>> is made, you

Re: Guide for relocating artifacts from one groupId to another

2006-07-09 Thread Dennis Lundberg
Carlos Sanchez wrote: Some comments Thanks! - add SHA1 checksums where you mention MD5. Maven2 uses first SHA1 if present Will do that. - Maven2 to Maven 2 / Releasing the next version When the next release of <<>> is made, you only need to publish a Maven 2 pom with a groupId of <<>>,

Re: Guide for relocating artifacts from one groupId to another

2006-07-08 Thread Carlos Sanchez
Some comments - add SHA1 checksums where you mention MD5. Maven2 uses first SHA1 if present - Maven2 to Maven 2 / Releasing the next version When the next release of <<>> is made, you only need to publish a Maven 2 pom with a groupId of <<>>, since users of previous versions have already been i

Re: Guide for relocating artifacts from one groupId to another

2006-07-07 Thread Dennis Lundberg
Committed for review: http://svn.apache.org/viewvc?view=rev&revision=420011 I have not created a link to this page in the index page yet. Will do that if review goes well. Brett Porter wrote: CTR On 6/07/2006 7:10 AM, Dennis Lundberg wrote: Do you prefer - commit then review or - review t

Re: Guide for relocating artifacts from one groupId to another

2006-07-05 Thread Brett Porter
CTR On 6/07/2006 7:10 AM, Dennis Lundberg wrote: Do you prefer - commit then review or - review then commit on stuff like this? Brett Porter wrote: +1 On 5/07/2006 10:37 AM, Dennis Lundberg wrote: Hi I'm in the process of relocating Jakarta commons components from groupID commons- to org.a

Re: Guide for relocating artifacts from one groupId to another

2006-07-05 Thread Dennis Lundberg
Do you prefer - commit then review or - review then commit on stuff like this? Brett Porter wrote: +1 On 5/07/2006 10:37 AM, Dennis Lundberg wrote: Hi I'm in the process of relocating Jakarta commons components from groupID commons- to org.apache.commons. To be able to do this correctly I'v

Re: Guide for relocating artifacts from one groupId to another

2006-07-05 Thread Jason van Zyl
+1 That would be awesome! On 5 Jul 06, at 1:37 AM 5 Jul 06, Dennis Lundberg wrote: Hi I'm in the process of relocating Jakarta commons components from groupID commons- to org.apache.commons. To be able to do this correctly I've had much help from Carlos. As this might be something that

Re: Guide for relocating artifacts from one groupId to another

2006-07-04 Thread jerome lacoste
+1 On 7/5/06, Brett Porter <[EMAIL PROTECTED]> wrote: +1 On 5/07/2006 10:37 AM, Dennis Lundberg wrote: > Hi > > I'm in the process of relocating Jakarta commons components from groupID > commons- to org.apache.commons. To be able to do this > correctly I've had much help from Carlos. As this mi

Re: Guide for relocating artifacts from one groupId to another

2006-07-04 Thread Brett Porter
+1 On 5/07/2006 10:37 AM, Dennis Lundberg wrote: Hi I'm in the process of relocating Jakarta commons components from groupID commons- to org.apache.commons. To be able to do this correctly I've had much help from Carlos. As this might be something that others will face, I thought it would be

Guide for relocating artifacts from one groupId to another

2006-07-04 Thread Dennis Lundberg
Hi I'm in the process of relocating Jakarta commons components from groupID commons- to org.apache.commons. To be able to do this correctly I've had much help from Carlos. As this might be something that others will face, I thought it would be a good idea to create some documentation for it.