Community
Participate
Working Groups
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
Assigning to Dmitry for now as agreed since he is interested in working on this bug.
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.
(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.
OK, thanks for the update. Closing as previous comment.