Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 312351

Summary:	build.eclipse.org needs a Maven2 location
Product:	Community	Reporter:	Antoine Toulmé <antoine>
Component:	Servers	Assignee:	Eclipse Webmaster <webmaster>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	d_a_carver, joakim.erdfelt, nboldt, wayne.beaton
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Antoine Toulmé

2010-05-10 18:25:06 EDT

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.

Comment 1 Joakim Erdfelt

2010-05-10 18:46:27 EDT

Additional information.

The "Eclipse Maven 2 Build Repository" does not need to be served off http://
  
It can be served off file:// as well.

Comment 2 Denis Roy

2010-05-10 18:52:11 EDT

Does this relate somehow to bug 297533?

Comment 3 Antoine Toulmé

2010-05-10 18:57:32 EDT

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.

Comment 4 Denis Roy

2010-05-10 19:17:15 EDT

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?

Comment 5 Antoine Toulmé

2010-05-10 19:31:50 EDT

/shared/m2repo would make my day.

Comment 6 Nick Boldt

2010-05-10 21:55:05 EDT

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

Comment 7 Denis Roy

2010-05-11 09:43:11 EDT

> /shared/m2repo would make my day.

You have write access to /shared/common .. /shared/common/m2repo is only marginally longer  :)

Comment 8 Antoine Toulmé

2010-05-27 19:06:32 EDT

mkdir m2repo... marking this as fixed.