Turns out that the problem was due to the certificate change in
svn.dev.java.net. The issue is fixed now, and your files are visible at
http://download.java.net/maven/1/
Kohsuke Kawaguchi wrote:
> Paul Sandoz wrote:
>> On Sep 18, 2007, at 5:56 PM, Aaron Anderson wrote:
>>
>>>
>>> Paul Sandoz <Paul.Sandoz_at_Sun.COM> wrote:
>>> > I am in two minds whether to back patch this to the JAX-RS 0.2
>>> zip as to
>>> > be completely consistent i would have to modify the stable Jersey
>>> 0.2.1
>>> > release. So perhaps we should only support this for 0.3 and
>>> onwards... ?
>>> >
>>> > In any case i will do things for 0.3 first.
>>> >
>>>
>>> Done.
>>>
>>> Great!
>>>
>>> I have not heard anything back from Kohsuke on the maven-repository
>>> project supporting SVN or the reason why the 2.1.1 release has not
>>> been published to the repository yet.
>>
>> I checked the issues list membership and the maven_repository user is
>> a member.
>>
>> I suspect that "/trunk/repo" is the wrong directory and the maven
>> repository listener will try to fetch artifacts from the "/repo"
>> directory.
>
> Sorry for my delay in response. The whole stuff relies on java.net HTTP
> UI, so perhaps in one of those java.net updates it broke the automation.
>
> I'll see if I can fix it quickly. Apologies about the problem.
>
>
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com