There can be no sane integration between Maven and Eclipse with mapping many Maven projects to one Eclipse project. If you have Maven plugins configured for your projects we cannot just jam the lifecycles of all those projects together and make something that works. We need to map individual projects 1:1. To just use Maven as a project aggregator for Eclipse is not a primary use case for us.
The code exists so if someone in the community wants to support an m2e extra for this behavior that's entirely possible. For Maven users we know this is not useful. It is simply impossible to map the behavior of many Maven projects to one Eclipse project.
I'm concerned how this is going to scale
because I usually have a couple of maintenance branches checked out along
with the trunk so that will give me a total of 54 projects... *ouch*. On
the brighter side because the maven dependencies are at the module level
now making the mistake of accidentally using a dependency in a module that
is declared in another modules pom won't happen... but that was a minor
inconvenience.
So I don't know if I like this change
or not. I'm going to give it a try and see how it goes. Hopefully soon
someone will re-implement multi-module support as an m2e extension.
Our team encountered too many problems which forced to
enter evaluation period of Netbeans:
- Very slow IDE, which may be caused by the m2eclipse plugin
- Tons of errors when working WTP, which results in Clean
Project, Redeploy, Remove module and add it back to Tomcat, etc.
Our
developers were too frustrated to continue working with Eclipse and M2Eclipse,
thus we are now working Netbeans 6.9.1, on evaluation period. So far, it
works flawlessly and ultra fast.
2011/2/24 Kuntze, Oliver (UIT) <Oliver.Kuntze@xxxxxxxxxxxxxxxxxxx>
Hey Jordan,
unfortunately the m2e team decided to drop
multi module project support. Even worse, they don’t plan to bring this
feature back.
We have an eai platform based on jbi/servicemix
running, so for us multi module project support is crucial, too.
The folks at eclipse have to address this
topic.
Currently we are evaluating shifting our
organization’s standard ide to netbeans, since it supports multi module
projects – Not as good as m2e did, but at least it does.
Cheers
Oliver
_________________________________
Union
IT-Services
GmbH
Oliver Kuntze
Anwendungsentwicklung EAI
Baseler Straße 10
60329 Frankfurt am Main
Tel.: 069 / 2567
1237
Fax: 069 / 2567 61237
E-Mail: oliver.kuntze@xxxxxxxxxxxxxxxxxxx
Sitz der Gesellschaft: Wiesenhüttenstraße 10, 60329 Frankfurt am Main
Registergericht: Amtsgericht Frankfurt am Main HRB 33314
Geschäftsführer: Ralph Höllig (Sprecher), Christian Leitner, Dr. Olaf Zeitnitz
Der Inhalt dieser E-Mail ist ausschließlich für den in der E-Mail bezeichneten
Empfänger bestimmt und kann vertrauliche und rechtlich geschützte Informationen
enthalten. Das Kopieren, die Weitergabe oder Offenlegung dieser Mail gegenüber
Dritten ist nicht gestattet. Sollten Sie nicht der richtige Adressat sein
oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort
den Absender telefonisch und löschen Sie diese Mail von Ihrem System. Vielen
Dank.
Die Sicherheit und Fehlerfreiheit der E-Mail-Übertragung kann nicht garantiert
werden, denn die gesendeten Informationen können abgefangen, manipuliert
oder zerstört werden, verloren gehen, verspätet oder unvollständig sein
oder Viren enthalten. Der Absender übernimmt deshalb keine Verantwortung
für jegliche Fehler oder Schäden, die sich aus der E-Mail-Übertragung ergeben.
Sofern Sie eine Bestätigung des Inhalts dieser E-Mail benötigen, kann dies
auf Anfrage durch einen Brief erfolgen.
Von: m2e-users-bounces@xxxxxxxxxxx
[mailto:m2e-users-bounces@xxxxxxxxxxx]
Im Auftrag von Jordan.Hein@xxxxxxxxxxx
Gesendet: Mittwoch, 23. Februar 2011 19:38
An: m2e-users@xxxxxxxxxxx
Betreff: [m2e-users] multi-module projects broken in 0.12.1?
We decided to do a tool chain update and get the latest eclipse and plugins.
Unfortunately when we use the 0.12.1 maven integration for eclipse our
multi-module projects are now broken. The maven integration is only seeing
the top level module and only putting dependencies from it in the "Maven
Dependencies". The modules in the projects are now all showing red
X's.
If we switch back to 0.10.x maven integration it works fine.
Is there some sort of setting we are missing that needs to enabled for
multi-module projects?
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
