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

Bug 314307

Summary:	Add Maven build support to Virgo
Product:	[RT] Virgo	Reporter:	Dmitry Sklyut <dmitry>
Component:	unknown	Assignee:	Dmitry Sklyut <dmitry>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	dmitry, eclipse, glyn.normington
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=311877
Whiteboard:
Bug Depends on:	357763
Bug Blocks:

Description Dmitry Sklyut

2010-05-25 12:57:05 EDT

Current Virgo build process is based on Ant and Ivy.  There isn't anything bad or wrong with it, but there is some interest in adding Maven support as well.


This has been discussed on Virgo community conference call on 2010-05-25.
http://wiki.eclipse.org/Virgo/Community/Minutes-2010-05-25

Comment 1 Glyn Normington

2010-05-25 22:59:22 EDT

Assigning to Dmitry for now as agreed since he is interested in working on this bug.

Comment 2 Chris Frost

2011-09-15 06:20:50 EDT

Dmitry, could you expand on this issue a little please. Is it just to produce Maven artifacts from the Virgo build or for something more.

Comment 3 Dmitry Sklyut

2011-09-15 10:12:10 EDT

(In reply to comment #2)
This issue was raised to have a parallel build system done in maven.
After some prototyping - I ran into maven plugin issues and was not able to create a build configuration that would be guaranteed to produce identical (bytecode compatible) artifacts.  Basically I could not get maven to use the same version of the eclipse compiler that Ant build used.

I think this issue can be closed now as there is very little worth in keeping two build systems side by side.  We should publish virgo artifacts to a maven repo as requested in another issue.

Comment 4 Chris Frost

2011-09-15 10:25:39 EDT

OK, thanks for the update.

Closing as previous comment.