Community
Participate
Working Groups
I need to point my build to a Maven2 repository. As of now, I can use an Intalio machine to hold my dependencies, but this is a rather bad set up. My build consumes exclusively Eclipse built artifacts. I can put together a hack to build against a site, by doing a file search every time, but it is expensive as well. I need: 1. a folder that is labelled "Maven 2 build repository" on build.eclipse.org That folder doesn't need to be public or open for consumption to the outside world. I would push whatever dependencies I have there. 2. a folder that is the offical Maven2 repo for Eclipse. I want to promote jars there. It's not as critical as I can promote my update site for now. Let me know on the feasibility of those points. I can do 1. easily by putting junk on /shared, but I have the feeling it's best to ask nicely first.
Additional information. The "Eclipse Maven 2 Build Repository" does not need to be served off http:// It can be served off file:// as well.
Does this relate somehow to bug 297533?
Err, frankly no. In one bug we have people discussing a name, in the other we're asking the webmaster to give us a spot on the build machine to place Maven artifacts. On the other bug, I think they want to consume artifacts using p2 to make them available like a a Maven repository.
Ok, I say just toss junk on /shared (as you say) and then post to cross-project to say that the junk is official. Works?
/shared/m2repo would make my day.
In my experience a local m2 repo can get corrupt... is that what we're asking for here, or a published repo? Or should we look at per-top-level-project repos? See also [1]. http://www.sonatype.com/people/2009/01/maven-continuous-integration-best-practices/ Note too that if you depend on Eclipse p2 repos, you can use Tycho [2] to resolve those deps w/o them being in a Maven repo. Ping me if you need sample code; it's pretty straightforward if you know Maven already. https://docs.sonatype.org/display/TYCHO/Tycho+reference+card
> /shared/m2repo would make my day. You have write access to /shared/common .. /shared/common/m2repo is only marginally longer :)
mkdir m2repo... marking this as fixed.
