Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jgit-dev] Maven Repositories

The builds at Eclipse do not need to happen on Eclipse servers (I talked with Mike about this). Sonatype has a Contegix managed infrastructure where we do all our builds. If the requirement is everyone who requires access gets it, the infrastructure has someone who will respond when there are problems, could we deploy the JGit releases to one of our Nexus instances and deliver back the necessary P2 repositories?

The discussion of whether we can install Nexus at Eclipse will likely go on ad nauseum. And while that is happening I would like to get something working because not having the artifacts in Maven Central is a major pita. Copying files around from servers doesn't really appeal to me. I'll do it but I would prefer to deploy to the type of infrastructure we have setup for Apache, Codehaus and the other OSS forges we help support.

On Jul 7, 2010, at 6:40 AM, Matthias Sohn wrote:

2010/7/7 Alin Dreghiciu <adreghiciu@xxxxxxxxx>
Tis ws looks outdated. Latest version of jgit is 0.6.0-SNAPSHOT. I
suppose that some other workspace is used.

Oops, I thought we use a job private maven repository here, but it seems this
has been changed for some reason I don't know. The maven repository shared 
between the jobs running on the same box isn't accessible from outside.

jgit-dev mailing list



Jason van Zyl
Founder,  Apache Maven

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 

Back to the top