Why not have a "foo-build" project which has a pom.xml file of pom packaging,which serves as an aggregator for you project.
This project will contain all the projects you need for a specific product. You can use git sub-module to hold the references to each project.
I'm in the process of writing a maven plugin which analyzes a pom.xml file, and for a specific groupId artifacts, it retrieves its pom file from Nexus, extracts the repository location and checks it out to the "foo-build" project directory. I think Atlassian Confluence wrote something similar.
On Tue, Feb 8, 2011 at 3:52 PM, Igor Fedorenko
<igor@xxxxxxxxxxxxxx> wrote:
You'll have to write some java code to do that, I can provide pointers
at m2e-dev mailing list if you are interested.
Sonatype also has a commercial product that does this as part of larger
development workspace materialization workflow.
--
Regards,
Igor
On 11-02-08 02:42 AM, Hauschel Fred Robert wrote:
Hi all,
is there a possibility to share a m2Eclipse like "Team Project Set" ?
The standard project set cannot handle Multi Modules and the maven
nature (I think so!).
The Goal:
Semi automated Eclipse setup with all the department Projects for new
developers in a easy way.
Or does anybody have a scripting idea ?
Thanks Fredy
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
