You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repo-maintainers@maven.apache.org by Lukas Theussl <lt...@apache.org> on 2009/10/09 14:42:15 UTC
old m1 artifacts missing from m1 repo
Hi guys,
Ref: http://www.nabble.com/Maven-1.0-and-j2sdk-1.5-Compilation-issues-td25819977.html
It seems like some jars are missing from http://repo1.maven.org/maven/ that
certainly have been there at one point (m1.1 already shipped with repo1 as default
repo). This causes old m1 builds to break if you start with a fresh local repo.
-Lukas
Re: old m1 artifacts missing from m1 repo
Posted by Arnaud HERITIER <ah...@gmail.com>.
Isn't it a problem of redirection which wasn't supported in 1.0 and we
fixed in 1.1?
Sent from my iPhone
On 11 oct. 2009, at 19:47, Carlos Sanchez <ca...@apache.org> wrote:
> the whole m1 repo is redirected to the m2 repo
>
> this url works
> http://repo1.maven.org/maven/velocity/jars/velocity-1.4-dev.jar
>
>
> On Fri, Oct 9, 2009 at 5:42 AM, Lukas Theussl <lt...@apache.org>
> wrote:
>>
>> Hi guys,
>>
>> Ref:
>> http://www.nabble.com/Maven-1.0-and-j2sdk-1.5-Compilation-issues-td25819977.html
>>
>> It seems like some jars are missing from http://repo1.maven.org/maven/
>> that
>> certainly have been there at one point (m1.1 already shipped with
>> repo1 as
>> default repo). This causes old m1 builds to break if you start with
>> a fresh
>> local repo.
>>
>>
>> -Lukas
>>
Re: old m1 artifacts missing from m1 repo
Posted by Lukas Theussl <lt...@apache.org>.
Right, sorry for the false alarm. I guess the quoted problem is due to the ibiblio
redirect issue [1] but for now there's no user feedback, so let's assume that it
works.
Cheerio,
-Lukas
[1] http://maven.apache.org/maven-1.x/news.html#ibiblio_redirect
Brian Fox wrote:
> Right, there's a note in there saying that it's redirected. You can't
> browse it in m1 form, but requests should work fine.
>
> On Sun, Oct 11, 2009 at 1:46 PM, Carlos Sanchez <ca...@apache.org> wrote:
>> the whole m1 repo is redirected to the m2 repo
>>
>> this url works
>> http://repo1.maven.org/maven/velocity/jars/velocity-1.4-dev.jar
>>
>>
>> On Fri, Oct 9, 2009 at 5:42 AM, Lukas Theussl <lt...@apache.org> wrote:
>>> Hi guys,
>>>
>>> Ref:
>>> http://www.nabble.com/Maven-1.0-and-j2sdk-1.5-Compilation-issues-td25819977.html
>>>
>>> It seems like some jars are missing from http://repo1.maven.org/maven/ that
>>> certainly have been there at one point (m1.1 already shipped with repo1 as
>>> default repo). This causes old m1 builds to break if you start with a fresh
>>> local repo.
>>>
>>>
>>> -Lukas
>>>
>
Re: old m1 artifacts missing from m1 repo
Posted by Brian Fox <br...@sonatype.com>.
Right, there's a note in there saying that it's redirected. You can't
browse it in m1 form, but requests should work fine.
On Sun, Oct 11, 2009 at 1:46 PM, Carlos Sanchez <ca...@apache.org> wrote:
> the whole m1 repo is redirected to the m2 repo
>
> this url works
> http://repo1.maven.org/maven/velocity/jars/velocity-1.4-dev.jar
>
>
> On Fri, Oct 9, 2009 at 5:42 AM, Lukas Theussl <lt...@apache.org> wrote:
>>
>> Hi guys,
>>
>> Ref:
>> http://www.nabble.com/Maven-1.0-and-j2sdk-1.5-Compilation-issues-td25819977.html
>>
>> It seems like some jars are missing from http://repo1.maven.org/maven/ that
>> certainly have been there at one point (m1.1 already shipped with repo1 as
>> default repo). This causes old m1 builds to break if you start with a fresh
>> local repo.
>>
>>
>> -Lukas
>>
>
Re: old m1 artifacts missing from m1 repo
Posted by Carlos Sanchez <ca...@apache.org>.
the whole m1 repo is redirected to the m2 repo
this url works
http://repo1.maven.org/maven/velocity/jars/velocity-1.4-dev.jar
On Fri, Oct 9, 2009 at 5:42 AM, Lukas Theussl <lt...@apache.org> wrote:
>
> Hi guys,
>
> Ref:
> http://www.nabble.com/Maven-1.0-and-j2sdk-1.5-Compilation-issues-td25819977.html
>
> It seems like some jars are missing from http://repo1.maven.org/maven/ that
> certainly have been there at one point (m1.1 already shipped with repo1 as
> default repo). This causes old m1 builds to break if you start with a fresh
> local repo.
>
>
> -Lukas
>