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

Bug 367126

Summary:	[maven.eclipse.org] Define process how to deploy official Eclipse releases
Product:	[Technology] Dash	Reporter:	Aaron Digulla <digulla>
Component:	Maven	Assignee:	Project Dash Incoming bugs <dash-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	btickets, stephan.herrmann, t-oberlies, thanh.ha
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:	361515
Bug Blocks:	361396, 366298, 489900

Description Aaron Digulla

2011-12-19 15:13:50 EST

We need a process and scripts to help building staging and release repos of Eclipse releases.

If possible, the repos should contain at least the milestones, the final release and the two service releases.

Open points:

- Write a script that collects the official release via rsync plus tools that help to write this script
- A git repo to manage the mt4e patches for each release
- Do we need a staging repo?
- How do we handle broken artifacts? Will we deploy a 3.7.1-1 or rather redeploy a fixed 3.7.1 plus publish this somewhere to consumers can fix their local caches? Or both?
- An official announcement of each release is necessary to gather people using our hard work :-)
- Anything I missed

Comment 1 Aaron Digulla

2011-12-19 16:40:15 EST

The current status of Maven Tools 4 Eclipse (mt4e) is that the Python tools has all the features but it has some unusual dependencies which makes it harder than necessary to deploy.

I've converted 90% of the features to a Groovy version (which would eventually become a single executable JAR). Most prominently, the patching tools are still lacking all of the features of the Python version.

Also some people have reported problems running the unit tests. If you want a go at the current version, follow the instructions on this page: http://wiki.eclipse.org/Maven_Tools_4_Eclipse

I hope to resume work in this in the next few days.

Comment 2 Tobias Oberlies

2011-12-20 04:03:02 EST

What is the process for regular Maven builds which just want to deploy their releases? Some Eclipse projects don't produce p2 artifacts and/or don't participate in the release train - so how will they release via maven.eclipse.org?

Comment 3 Tobias Oberlies

2011-12-20 04:04:58 EST

IMHO, bug 361515 is a prerequisite for this story.

Comment 4 Aaron Digulla

2011-12-20 04:34:32 EST

(In reply to comment #2)
> What is the process for regular Maven builds which just want to deploy their
> releases? Some Eclipse projects don't produce p2 artifacts and/or don't
> participate in the release train - so how will they release via
> maven.eclipse.org?

That's still to be defined. See bug 367138.

Comment 5 Thanh Ha

2014-04-29 09:47:00 EDT

maven.eclipse.org was decommissioned via bug 405750 and replaced with
repo.eclipse.org.

See: https://wiki.eclipse.org/Services/Nexus