| Re: [m2e-users] share a m2Eclipse like "Team Project Set" |
Hi Asaf, sound very interesting ;-) I understand your "foo-build" solution as a “big” multi module maven pom-artefact, which have all the department maven artefacts as module. This will simplify the checkout in eclipse, but it is a litle kind of workaround. Maybe I will do that! Your maven plugin will help to check out the “referenced” projects, but they are no projects with eclipse nature. You use a pom for handling the “meta-data” which for example in the eclipse project set. I’m not sure if this is The solution, but I’m sure it is the right way. Fredy Von: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] Im Auftrag von Asaf Mesika 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 Hi all, _______________________________________________ |