You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Thomas Neidhart <th...@gmail.com> on 2013/03/14 22:24:40 UTC

[collections] was Re: [jira] [Closed] (COLLECTIONS-449) Latest Version is set to 20040616

On 03/14/2013 08:30 AM, Joerg Schaible (JIRA) wrote:
> 
>      [ https://issues.apache.org/jira/browse/COLLECTIONS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> 
> Joerg Schaible closed COLLECTIONS-449.
> --------------------------------------
> 
>     Resolution: Won't Fix
>       Assignee: Joerg Schaible
> 
> Sorry, but we have no control over the central Maven repository.

but central is sync'ed from our repo afaik.

Looking at

https://repository.apache.org/content/groups/public/commons-collections/commons-collections/

You can see the same meta-data change on 13-Mar-2013 17:45
Can we do something about this?

Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [collections] was Re: [jira] [Closed] (COLLECTIONS-449) Latest Version is set to 20040616

Posted by Thomas Neidhart <th...@gmail.com>.
On 03/15/2013 11:06 AM, Jörg Schaible wrote:
> Hi Thomas,
> 
> Thomas Neidhart wrote:
> 
>> On Fri, Mar 15, 2013 at 9:32 AM, Jörg Schaible
>> <Jo...@scalaris.com>wrote:
> 
> [snip]
> 
>>>> This looks more like a mistake rather than an official release, and is
>>>> also not contained in the doap file. Does anybody know something about
>>>> them, can we remove them?
>>>>
>>>>  20030418.083655/
>>>>  20031027.000000/
>>>>  20040102.233541/
>>>>  20040616/
>>>
>>> It will not help at all for central.
>>>
>>
>> The question is, can we safely delete them in our repo, and ask them to do
>> the same?
> 
> They cannot be removed, they are used 
> (http://mvnrepository.com/artifact/commons-collections/commons-
> collections/20040616). And they will not, it is completely against the 
> policy.

ok, I understand, hopefully collections4 will be ready soon where we
have a different groupId.

Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [collections] was Re: [jira] [Closed] (COLLECTIONS-449) Latest Version is set to 20040616

Posted by Jörg Schaible <Jo...@scalaris.com>.
Hi Thomas,

Thomas Neidhart wrote:

> On Fri, Mar 15, 2013 at 9:32 AM, Jörg Schaible
> <Jo...@scalaris.com>wrote:

[snip]

>> > This looks more like a mistake rather than an official release, and is
>> > also not contained in the doap file. Does anybody know something about
>> > them, can we remove them?
>> >
>> >  20030418.083655/
>> >  20031027.000000/
>> >  20040102.233541/
>> >  20040616/
>>
>> It will not help at all for central.
>>
> 
> The question is, can we safely delete them in our repo, and ask them to do
> the same?

They cannot be removed, they are used 
(http://mvnrepository.com/artifact/commons-collections/commons-
collections/20040616). And they will not, it is completely against the 
policy.

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [collections] was Re: [jira] [Closed] (COLLECTIONS-449) Latest Version is set to 20040616

Posted by Thomas Neidhart <th...@gmail.com>.
On Fri, Mar 15, 2013 at 9:32 AM, Jörg Schaible
<Jo...@scalaris.com>wrote:

> Hi Thomas,
>
> Thomas Neidhart wrote:
>
> > On 03/14/2013 10:24 PM, Thomas Neidhart wrote:
> >> On 03/14/2013 08:30 AM, Joerg Schaible (JIRA) wrote:
> >>>
> >>>      [
>
> https://issues.apache.org/jira/browse/COLLECTIONS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-
> tabpanel
> >>>      [ ]
> >>>
> >>> Joerg Schaible closed COLLECTIONS-449.
> >>> --------------------------------------
> >>>
> >>>     Resolution: Won't Fix
> >>>       Assignee: Joerg Schaible
> >>>
> >>> Sorry, but we have no control over the central Maven repository.
> >>
> >> but central is sync'ed from our repo afaik.
>
> Yes, but the sync is one way, nothing on central will be removed.
>
> >>
> >> Looking at
> >>
> >> https://repository.apache.org/content/groups/public/commons-
> collections/commons-collections/
> >>
> >> You can see the same meta-data change on 13-Mar-2013 17:45
> >> Can we do something about this?
>
> Meta-data is *not* synced. The repo manager at central will create its own.
> Look at the one at central, it is different.
>
> > well, I guess the problem is there since a long time, as the mechanism
> > to detect the latest version will not be able to cope with the weird
> > version that is available in the repo:
> >
> >  20040616 > 3.2.1
> >
> > This looks more like a mistake rather than an official release, and is
> > also not contained in the doap file. Does anybody know something about
> > them, can we remove them?
> >
> >  20030418.083655/
> >  20031027.000000/
> >  20040102.233541/
> >  20040616/
>
> It will not help at all for central.
>

The question is, can we safely delete them in our repo, and ask them to do
the same?

Thomas

Re: [collections] was Re: [jira] [Closed] (COLLECTIONS-449) Latest Version is set to 20040616

Posted by Jörg Schaible <Jo...@scalaris.com>.
Hi Thomas,

Thomas Neidhart wrote:

> On 03/14/2013 10:24 PM, Thomas Neidhart wrote:
>> On 03/14/2013 08:30 AM, Joerg Schaible (JIRA) wrote:
>>>
>>>      [ 
https://issues.apache.org/jira/browse/COLLECTIONS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-
tabpanel
>>>      [ ]
>>>
>>> Joerg Schaible closed COLLECTIONS-449.
>>> --------------------------------------
>>>
>>>     Resolution: Won't Fix
>>>       Assignee: Joerg Schaible
>>>
>>> Sorry, but we have no control over the central Maven repository.
>> 
>> but central is sync'ed from our repo afaik.

Yes, but the sync is one way, nothing on central will be removed.

>> 
>> Looking at
>> 
>> https://repository.apache.org/content/groups/public/commons-
collections/commons-collections/
>> 
>> You can see the same meta-data change on 13-Mar-2013 17:45
>> Can we do something about this?

Meta-data is *not* synced. The repo manager at central will create its own. 
Look at the one at central, it is different.

> well, I guess the problem is there since a long time, as the mechanism
> to detect the latest version will not be able to cope with the weird
> version that is available in the repo:
> 
>  20040616 > 3.2.1
> 
> This looks more like a mistake rather than an official release, and is
> also not contained in the doap file. Does anybody know something about
> them, can we remove them?
> 
>  20030418.083655/
>  20031027.000000/
>  20040102.233541/
>  20040616/

It will not help at all for central.

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [collections] was Re: [jira] [Closed] (COLLECTIONS-449) Latest Version is set to 20040616

Posted by Thomas Neidhart <th...@gmail.com>.
On 03/14/2013 10:24 PM, Thomas Neidhart wrote:
> On 03/14/2013 08:30 AM, Joerg Schaible (JIRA) wrote:
>>
>>      [ https://issues.apache.org/jira/browse/COLLECTIONS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Joerg Schaible closed COLLECTIONS-449.
>> --------------------------------------
>>
>>     Resolution: Won't Fix
>>       Assignee: Joerg Schaible
>>
>> Sorry, but we have no control over the central Maven repository.
> 
> but central is sync'ed from our repo afaik.
> 
> Looking at
> 
> https://repository.apache.org/content/groups/public/commons-collections/commons-collections/
> 
> You can see the same meta-data change on 13-Mar-2013 17:45
> Can we do something about this?

well, I guess the problem is there since a long time, as the mechanism
to detect the latest version will not be able to cope with the weird
version that is available in the repo:

 20040616 > 3.2.1

This looks more like a mistake rather than an official release, and is
also not contained in the doap file. Does anybody know something about
them, can we remove them?

 20030418.083655/
 20031027.000000/
 20040102.233541/
 20040616/

Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org