You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Julius Davies <ju...@gmail.com> on 2011/03/31 21:28:44 UTC
Re: [Nexus] Commons-codec release not showing up in Maven Central
after 24 hours
Somewhat off topic question:
Why do some commons artifacts go here?
http://repo2.maven.org/maven2/org/apache/commons/
And others go to the root (look for commons-*)?
http://repo2.maven.org/maven2/
On Wed, Mar 30, 2011 at 1:58 PM, sebb <se...@gmail.com> wrote:
> Commons Codec 1.5 was promoted from Nexus on 29 March 2011 06:21
>
> and is showing up here:
>
> https://repository.apache.org/content/groups/staging/commons-codec/commons-codec/1.5/
>
> However it has yet to show up in Maven Central over 24 hours later.
>
> http://repo1.maven.org/maven2/commons-codec/commons-codec/
>
> Has something gone wrong with the process?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
yours,
Julius Davies
250-592-2284 (Home)
$ sudo apt-get install cowsay
$ echo "Moo." | cowsay | cowsay -n | cowsay -n
http://juliusdavies.ca/cowsay/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Nexus] Commons-codec release not showing up in Maven Central after 24 hours
Posted by Jörg Schaible <jo...@gmx.de>.
Hi Julius,
Julius Davies wrote:
> Somewhat off topic question:
>
> Why do some commons artifacts go here?
>
> http://repo2.maven.org/maven2/org/apache/commons/
New ones and the ones with major API changes
>
> And others go to the root (look for commons-*)?
>
> http://repo2.maven.org/maven2/
The ones who were already available for Maven 1 and where new releases are
still binary upward compatible.
Changing the groupId will create disruptions for Maven's dpeendency
resolution (and yes, we know about relocation functionality).
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Nexus] Commons-codec release not showing up in Maven Central
after 24 hours
Posted by Julius Davies <ju...@gmail.com>.
On Thu, Mar 31, 2011 at 7:15 PM, sebb <se...@gmail.com> wrote:
> On 1 April 2011 02:49, Phil Steitz <ph...@gmail.com> wrote:
>> On 3/31/11 1:58 PM, Gary Gregory wrote:
>>> Because the Maven groupId in the POM. They dictate where files go. Changing
>>> an ID is a big deal.
>>
>> To provide a little more context, Commons began drinking the maven
>> cool-aid very early, back in the pre-release maven 1 days. At that
>> time, artifact naming had not evolved to the point that is has
>> now. The current recommended maven approach is to use
>> org.apache.project... as the groupId. When we starting pushing
>> Commons components to m1 repos, that had not been established, so
>> many of our older components were published with groupIds of the
>> form "commons-foo". Changing is a disruptive PITA for us and users,
>> so we have decided to do it coincident with major version changes.
>> Over time, all will move to org.apache.commons.
>
> With the possible exception of commons-logging ...
>
Thanks, all, for the explanation and background! I'm an ant man
myself (a mant?), but I recently worked on an academic paper on jars
in Maven2 (google for 'bertillonage'), and I was curious how these
different directories come to be! Thank you!!!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Nexus] Commons-codec release not showing up in Maven Central
after 24 hours
Posted by sebb <se...@gmail.com>.
On 1 April 2011 02:49, Phil Steitz <ph...@gmail.com> wrote:
> On 3/31/11 1:58 PM, Gary Gregory wrote:
>> Because the Maven groupId in the POM. They dictate where files go. Changing
>> an ID is a big deal.
>
> To provide a little more context, Commons began drinking the maven
> cool-aid very early, back in the pre-release maven 1 days. At that
> time, artifact naming had not evolved to the point that is has
> now. The current recommended maven approach is to use
> org.apache.project... as the groupId. When we starting pushing
> Commons components to m1 repos, that had not been established, so
> many of our older components were published with groupIds of the
> form "commons-foo". Changing is a disruptive PITA for us and users,
> so we have decided to do it coincident with major version changes.
> Over time, all will move to org.apache.commons.
With the possible exception of commons-logging ...
> Phil
>
>
>> Gary
>>
>> On Thu, Mar 31, 2011 at 3:28 PM, Julius Davies <ju...@gmail.com>wrote:
>>
>>> Somewhat off topic question:
>>>
>>> Why do some commons artifacts go here?
>>>
>>> http://repo2.maven.org/maven2/org/apache/commons/
>>>
>>> And others go to the root (look for commons-*)?
>>>
>>> http://repo2.maven.org/maven2/
>>>
>>>
>>>
>>> On Wed, Mar 30, 2011 at 1:58 PM, sebb <se...@gmail.com> wrote:
>>>> Commons Codec 1.5 was promoted from Nexus on 29 March 2011 06:21
>>>>
>>>> and is showing up here:
>>>>
>>>>
>>> https://repository.apache.org/content/groups/staging/commons-codec/commons-codec/1.5/
>>>> However it has yet to show up in Maven Central over 24 hours later.
>>>>
>>>> http://repo1.maven.org/maven2/commons-codec/commons-codec/
>>>>
>>>> Has something gone wrong with the process?
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> yours,
>>>
>>> Julius Davies
>>> 250-592-2284 (Home)
>>>
>>> $ sudo apt-get install cowsay
>>> $ echo "Moo." | cowsay | cowsay -n | cowsay -n
>>> http://juliusdavies.ca/cowsay/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Nexus] Commons-codec release not showing up in Maven Central
after 24 hours
Posted by Phil Steitz <ph...@gmail.com>.
On 3/31/11 1:58 PM, Gary Gregory wrote:
> Because the Maven groupId in the POM. They dictate where files go. Changing
> an ID is a big deal.
To provide a little more context, Commons began drinking the maven
cool-aid very early, back in the pre-release maven 1 days. At that
time, artifact naming had not evolved to the point that is has
now. The current recommended maven approach is to use
org.apache.project... as the groupId. When we starting pushing
Commons components to m1 repos, that had not been established, so
many of our older components were published with groupIds of the
form "commons-foo". Changing is a disruptive PITA for us and users,
so we have decided to do it coincident with major version changes.
Over time, all will move to org.apache.commons.
Phil
> Gary
>
> On Thu, Mar 31, 2011 at 3:28 PM, Julius Davies <ju...@gmail.com>wrote:
>
>> Somewhat off topic question:
>>
>> Why do some commons artifacts go here?
>>
>> http://repo2.maven.org/maven2/org/apache/commons/
>>
>> And others go to the root (look for commons-*)?
>>
>> http://repo2.maven.org/maven2/
>>
>>
>>
>> On Wed, Mar 30, 2011 at 1:58 PM, sebb <se...@gmail.com> wrote:
>>> Commons Codec 1.5 was promoted from Nexus on 29 March 2011 06:21
>>>
>>> and is showing up here:
>>>
>>>
>> https://repository.apache.org/content/groups/staging/commons-codec/commons-codec/1.5/
>>> However it has yet to show up in Maven Central over 24 hours later.
>>>
>>> http://repo1.maven.org/maven2/commons-codec/commons-codec/
>>>
>>> Has something gone wrong with the process?
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>>
>> --
>> yours,
>>
>> Julius Davies
>> 250-592-2284 (Home)
>>
>> $ sudo apt-get install cowsay
>> $ echo "Moo." | cowsay | cowsay -n | cowsay -n
>> http://juliusdavies.ca/cowsay/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Nexus] Commons-codec release not showing up in Maven Central
after 24 hours
Posted by sebb <se...@gmail.com>.
https://issues.apache.org/jira/browse/INFRA-3556
On 1 April 2011 02:38, sebb <se...@gmail.com> wrote:
> Normally the RAO list is very responsive; I'll raise a JIRA.
>
> On 1 April 2011 02:01, Gary Gregory <ga...@gmail.com> wrote:
>> And... still nothing on Maven Central :( What IS (not) going on?
>>
>> Did I miss a step? Forget to bark at the moon?
>>
>> Gary
>>
>> On Thu, Mar 31, 2011 at 4:58 PM, Gary Gregory <ga...@gmail.com>wrote:
>>
>>> Because the Maven groupId in the POM. They dictate where files go. Changing
>>> an ID is a big deal.
>>>
>>> Gary
>>>
>>> On Thu, Mar 31, 2011 at 3:28 PM, Julius Davies <ju...@gmail.com>wrote:
>>>
>>>> Somewhat off topic question:
>>>>
>>>> Why do some commons artifacts go here?
>>>>
>>>> http://repo2.maven.org/maven2/org/apache/commons/
>>>>
>>>> And others go to the root (look for commons-*)?
>>>>
>>>> http://repo2.maven.org/maven2/
>>>>
>>>>
>>>>
>>>> On Wed, Mar 30, 2011 at 1:58 PM, sebb <se...@gmail.com> wrote:
>>>> > Commons Codec 1.5 was promoted from Nexus on 29 March 2011 06:21
>>>> >
>>>> > and is showing up here:
>>>> >
>>>> >
>>>> https://repository.apache.org/content/groups/staging/commons-codec/commons-codec/1.5/
>>>> >
>>>> > However it has yet to show up in Maven Central over 24 hours later.
>>>> >
>>>> > http://repo1.maven.org/maven2/commons-codec/commons-codec/
>>>> >
>>>> > Has something gone wrong with the process?
>>>> >
>>>> > ---------------------------------------------------------------------
>>>> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> > For additional commands, e-mail: dev-help@commons.apache.org
>>>> >
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> yours,
>>>>
>>>> Julius Davies
>>>> 250-592-2284 (Home)
>>>>
>>>> $ sudo apt-get install cowsay
>>>> $ echo "Moo." | cowsay | cowsay -n | cowsay -n
>>>> http://juliusdavies.ca/cowsay/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Thank you,
>>> Gary
>>>
>>> http://garygregory.wordpress.com/
>>> http://garygregory.com/
>>> http://people.apache.org/~ggregory/
>>> http://twitter.com/GaryGregory
>>>
>>
>>
>>
>> --
>> Thank you,
>> Gary
>>
>> http://garygregory.wordpress.com/
>> http://garygregory.com/
>> http://people.apache.org/~ggregory/
>> http://twitter.com/GaryGregory
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Nexus] Commons-codec release not showing up in Maven Central
after 24 hours
Posted by sebb <se...@gmail.com>.
Normally the RAO list is very responsive; I'll raise a JIRA.
On 1 April 2011 02:01, Gary Gregory <ga...@gmail.com> wrote:
> And... still nothing on Maven Central :( What IS (not) going on?
>
> Did I miss a step? Forget to bark at the moon?
>
> Gary
>
> On Thu, Mar 31, 2011 at 4:58 PM, Gary Gregory <ga...@gmail.com>wrote:
>
>> Because the Maven groupId in the POM. They dictate where files go. Changing
>> an ID is a big deal.
>>
>> Gary
>>
>> On Thu, Mar 31, 2011 at 3:28 PM, Julius Davies <ju...@gmail.com>wrote:
>>
>>> Somewhat off topic question:
>>>
>>> Why do some commons artifacts go here?
>>>
>>> http://repo2.maven.org/maven2/org/apache/commons/
>>>
>>> And others go to the root (look for commons-*)?
>>>
>>> http://repo2.maven.org/maven2/
>>>
>>>
>>>
>>> On Wed, Mar 30, 2011 at 1:58 PM, sebb <se...@gmail.com> wrote:
>>> > Commons Codec 1.5 was promoted from Nexus on 29 March 2011 06:21
>>> >
>>> > and is showing up here:
>>> >
>>> >
>>> https://repository.apache.org/content/groups/staging/commons-codec/commons-codec/1.5/
>>> >
>>> > However it has yet to show up in Maven Central over 24 hours later.
>>> >
>>> > http://repo1.maven.org/maven2/commons-codec/commons-codec/
>>> >
>>> > Has something gone wrong with the process?
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> > For additional commands, e-mail: dev-help@commons.apache.org
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> yours,
>>>
>>> Julius Davies
>>> 250-592-2284 (Home)
>>>
>>> $ sudo apt-get install cowsay
>>> $ echo "Moo." | cowsay | cowsay -n | cowsay -n
>>> http://juliusdavies.ca/cowsay/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>>
>> --
>> Thank you,
>> Gary
>>
>> http://garygregory.wordpress.com/
>> http://garygregory.com/
>> http://people.apache.org/~ggregory/
>> http://twitter.com/GaryGregory
>>
>
>
>
> --
> Thank you,
> Gary
>
> http://garygregory.wordpress.com/
> http://garygregory.com/
> http://people.apache.org/~ggregory/
> http://twitter.com/GaryGregory
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Nexus] Commons-codec release not showing up in Maven Central
after 24 hours
Posted by Gary Gregory <ga...@gmail.com>.
And... still nothing on Maven Central :( What IS (not) going on?
Did I miss a step? Forget to bark at the moon?
Gary
On Thu, Mar 31, 2011 at 4:58 PM, Gary Gregory <ga...@gmail.com>wrote:
> Because the Maven groupId in the POM. They dictate where files go. Changing
> an ID is a big deal.
>
> Gary
>
> On Thu, Mar 31, 2011 at 3:28 PM, Julius Davies <ju...@gmail.com>wrote:
>
>> Somewhat off topic question:
>>
>> Why do some commons artifacts go here?
>>
>> http://repo2.maven.org/maven2/org/apache/commons/
>>
>> And others go to the root (look for commons-*)?
>>
>> http://repo2.maven.org/maven2/
>>
>>
>>
>> On Wed, Mar 30, 2011 at 1:58 PM, sebb <se...@gmail.com> wrote:
>> > Commons Codec 1.5 was promoted from Nexus on 29 March 2011 06:21
>> >
>> > and is showing up here:
>> >
>> >
>> https://repository.apache.org/content/groups/staging/commons-codec/commons-codec/1.5/
>> >
>> > However it has yet to show up in Maven Central over 24 hours later.
>> >
>> > http://repo1.maven.org/maven2/commons-codec/commons-codec/
>> >
>> > Has something gone wrong with the process?
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> > For additional commands, e-mail: dev-help@commons.apache.org
>> >
>> >
>>
>>
>>
>> --
>> yours,
>>
>> Julius Davies
>> 250-592-2284 (Home)
>>
>> $ sudo apt-get install cowsay
>> $ echo "Moo." | cowsay | cowsay -n | cowsay -n
>> http://juliusdavies.ca/cowsay/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> --
> Thank you,
> Gary
>
> http://garygregory.wordpress.com/
> http://garygregory.com/
> http://people.apache.org/~ggregory/
> http://twitter.com/GaryGregory
>
--
Thank you,
Gary
http://garygregory.wordpress.com/
http://garygregory.com/
http://people.apache.org/~ggregory/
http://twitter.com/GaryGregory
Re: [Nexus] Commons-codec release not showing up in Maven Central
after 24 hours
Posted by Gary Gregory <ga...@gmail.com>.
Because the Maven groupId in the POM. They dictate where files go. Changing
an ID is a big deal.
Gary
On Thu, Mar 31, 2011 at 3:28 PM, Julius Davies <ju...@gmail.com>wrote:
> Somewhat off topic question:
>
> Why do some commons artifacts go here?
>
> http://repo2.maven.org/maven2/org/apache/commons/
>
> And others go to the root (look for commons-*)?
>
> http://repo2.maven.org/maven2/
>
>
>
> On Wed, Mar 30, 2011 at 1:58 PM, sebb <se...@gmail.com> wrote:
> > Commons Codec 1.5 was promoted from Nexus on 29 March 2011 06:21
> >
> > and is showing up here:
> >
> >
> https://repository.apache.org/content/groups/staging/commons-codec/commons-codec/1.5/
> >
> > However it has yet to show up in Maven Central over 24 hours later.
> >
> > http://repo1.maven.org/maven2/commons-codec/commons-codec/
> >
> > Has something gone wrong with the process?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
>
>
> --
> yours,
>
> Julius Davies
> 250-592-2284 (Home)
>
> $ sudo apt-get install cowsay
> $ echo "Moo." | cowsay | cowsay -n | cowsay -n
> http://juliusdavies.ca/cowsay/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Thank you,
Gary
http://garygregory.wordpress.com/
http://garygregory.com/
http://people.apache.org/~ggregory/
http://twitter.com/GaryGregory