Re: Guide for relocating artifacts from one groupId to another
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 foo is made, you only need to publish a Maven 2 pom with a groupId of org.bar, since users of previous versions have already been informed of the changed groupId. If users have cached the poms in the old groupid maven won't know about the relocation, so you still need to publish poms for next versions in old locations in order for the user to see the warning. Is this due to the bug mentioned in the thread about Cocoon? If it is due to a bug should I write on this page that it is due to a bug, and that the need to publish new poms in the old location will go away over time? On 7/8/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Committed for review: http://svn.apache.org/viewvc?view=revrevision=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 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-component 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. Is this something that would be appropriate for maven-site? If so where should I put it? I was thinking maybe http://maven.apache.org/guides/mini/guide-relocation.html -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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
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 foo is made, you only need to publish a Maven 2 pom with a groupId of org.bar, since users of previous versions have already been informed of the changed groupId. If users have cached the poms in the old groupid maven won't know about the relocation, so you still need to publish poms for next versions in old locations in order for the user to see the warning. Is this due to the bug mentioned in the thread about Cocoon? If it is due to a bug should I write on this page that it is due to a bug, and that the need to publish new poms in the old location will go away over time? It is not a bug, data in the repo is not supposed to change so maven doesn't download it again. If it's already cached you won't notice that it has been relocated, that's why you should provide relocation poms for next releases. On 7/8/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Committed for review: http://svn.apache.org/viewvc?view=revrevision=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 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-component 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. Is this something that would be appropriate for maven-site? If so where should I put it? I was thinking maybe http://maven.apache.org/guides/mini/guide-relocation.html -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Guide for relocating artifacts from one groupId to another
Committed the proposed changes in http://svn.apache.org/viewvc?view=revrevision=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
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 foo is made, you only need to publish a Maven 2 pom with a groupId of org.bar, since users of previous versions have already been informed of the changed groupId. If users have cached the poms in the old groupid maven won't know about the relocation, so you still need to publish poms for next versions in old locations in order for the user to see the warning. On 7/8/06, Dennis Lundberg [EMAIL PROTECTED] wrote: Committed for review: http://svn.apache.org/viewvc?view=revrevision=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 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-component 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. Is this something that would be appropriate for maven-site? If so where should I put it? I was thinking maybe http://maven.apache.org/guides/mini/guide-relocation.html -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Guide for relocating artifacts from one groupId to another
Committed for review: http://svn.apache.org/viewvc?view=revrevision=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 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-component 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. Is this something that would be appropriate for maven-site? If so where should I put it? I was thinking maybe http://maven.apache.org/guides/mini/guide-relocation.html -- 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
+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-component 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. Is this something that would be appropriate for maven-site? If so where should I put it? I was thinking maybe http:// maven.apache.org/guides/mini/guide-relocation.html -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Jason van Zyl [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Guide for relocating artifacts from one groupId to another
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-component 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. Is this something that would be appropriate for maven-site? If so where should I put it? I was thinking maybe http://maven.apache.org/guides/mini/guide-relocation.html -- 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
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-component 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. Is this something that would be appropriate for maven-site? If so where should I put it? I was thinking maybe http://maven.apache.org/guides/mini/guide-relocation.html -- Brett Porter [EMAIL PROTECTED] Apache Maven - http://maven.apache.org/ Better Builds with Maven - http://library.mergere.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Guide for relocating artifacts from one groupId to another
Hi I'm in the process of relocating Jakarta commons components from groupID commons-component 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. Is this something that would be appropriate for maven-site? If so where should I put it? I was thinking maybe http://maven.apache.org/guides/mini/guide-relocation.html -- 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
+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-component 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. Is this something that would be appropriate for maven-site? If so where should I put it? I was thinking maybe http://maven.apache.org/guides/mini/guide-relocation.html -- Brett Porter [EMAIL PROTECTED] Apache Maven - http://maven.apache.org/ Better Builds with Maven - http://library.mergere.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Guide for relocating artifacts from one groupId to another
+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-component 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. Is this something that would be appropriate for maven-site? If so where should I put it? I was thinking maybe http://maven.apache.org/guides/mini/guide-relocation.html -- Brett Porter [EMAIL PROTECTED] Apache Maven - http://maven.apache.org/ Better Builds with Maven - http://library.mergere.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
