Hi Ken,
I didn't set this up so I'm also trying to understand the setup.
This is what's happening, when you do a maven deployment to
http://maven2-repository.dev.java.net/svn/maven2-repository/trunk/repository
or "java-net:/maven2-repository/trunk/repository/", you're actually
checking-in the artifacts to a svn repository. This is not the actual
repository that is hosting the maven artifacts for java.net projects.
The repository that is hosting the artifacts is here:
http://download.java.net/maven/.
An internal Hudson job checks-out the svn workspace and scp to the
system that is hosting the maven repository on java.net.
Earlier you were able to successful deploy to the svn repository but the
Hudson job that scp to one of the maven repository
(
http://maven.dyndns.org/) is out of space therefore causing the job to
fail and not able to complete the rest of the transaction which is to
copy to the maven repository on
http://download.java.net/maven. All I
did was disable scp to
http://maven.dyndns.org. I think disabling this
repo should be okay since it is a back-up of the maven repo on
http://download.java.net/maven.
HTH,
Jane
Ken Cavanaugh wrote:
> Jane Young wrote:
>> Please check it now. Corba artifacts are now uploaded to java.net
>> The job that rsync the artifacts to java.net was down.
>>
>
> Could you explain how this is set up? I thought I was uploading
> directly to
> java.net. What is the intermediate step?
>
> Thanks,
>
> Ken.
>