Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] multi-module projects broken in 0.12.1?

Hi Oliver,

Your naming conflict can be resolved when using 'import/existing maven project': open the advanced section of the dialog and choose an appropriate name template.

Regards, Marcel

On Mon, Feb 28, 2011 at 3:47 PM, Kuntze, Oliver (UIT) <Oliver.Kuntze@xxxxxxxxxxxxxxxxxxx> wrote:
Hey Igor,
sure.

As far as I understand, any multi module project with nested modules having different group-ids but the same artifact-id will not be imported in eclipse because of the naming conflict (modules having same artifact-id -> same folder name -> same project name).

One can argue about JBI being a relevant Java standard or not, especially since the advent of OSGi (Well, in my opinion stripping down JBI to the NMR spec and adding OSGi would be sufficient/better...), but the recent m2e releases render JBI development nearly impossible.
Not because it is inconvenient, eclipse is not able to handle that amount of projects in its workspace. At least on my dev machine eclipse's performance drops to zero.

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
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.


-----Ursprüngliche Nachricht-----
Von: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] Im Auftrag von Igor Fedorenko
Gesendet: Montag, 28. Februar 2011 13:19
Betreff: Re: [m2e-users] multi-module projects broken in 0.12.1?

Can you explain this statement in more details "We have lost a lot of
flexibility regarding the types of projects and even java standards
support when the nested multi module option was dropped from m2e"? Apart
from inconvenience of dealing with large number of workspace projects,
what types of projects and java standards cannot be supported by m2e?

--
Regards,
Igor

On 11-02-28 06:17 AM, Kuntze, Oliver (UIT) wrote:
> Hey,
>
> for whom working with working sets instead of nested multi module
> projects is feasible this is definitely an option.
>
> We develop JBI based applications, so one application can easily consist
> of 50+ modules. So regarding our EAI platform we are speaking of
> hundreds of modules. Plus loosing the structural information that
> service assemblies are comprised of service units. For us using working
> sets would not do it.
>
> Is there a solution in the current m2e release for the following nested
> modules scenario?
>
> -group-id=my-app-group, artifact-id=my-app-1
>
> ogroup-id=my-app-1, artifact-id=my-app-module-1
>
> §group-id= my-app-module-1, artifact-id=rule-engine
>
> ogroup-id=my-app-1, artifact-id=my-app-module-2
>
> §group-id= my-app-module-2, artifact-id=rule-engine
>
> With nested multi module support and one eclipse project "my-app-1" this
> scenario posed no problem.
>
> Without multi module support and eclipse trying to create projects
> "my-app-1", "my-app-module-1", "rule-engine", "my-app-module-2" and
> another "rule-engine" ... Not working.
>
> Netbeans for example uses group-id and artifact-id to determine project
> names.
>
> We have lost a lot of flexibility regarding the types of projects and
> even java standards support when the nested multi module option was
> dropped from m2e. I am absolutely with you that with regards to
> classpath topics etc. this has to be addressed within eclipse as a
> general. It cannot be addressed isolated in m2e. But since m2e is
> becoming part of the standard eclipse rollout it would be great if you
> guys could  put this topic on the eclipse agenda.
>
> Thanks for the great work you all are committing! I really appreciate it
> (even if my mail doesn't sound like ;-)!
>
> Cheers
>
> Oliver
>
> _________________________________
>
> *Union****IT-Services****GmbH*
> *Oliver Kuntze**
> *Anwendungsentwicklung EAI
> Baseler Straße 10
> 60329 Frankfurt am Main
>
> Tel.: 069 / 25671237
> Fax: 069 / 256761237
> E-Mail:oliver.kuntze@xxxxxxxxxxxxxxxxxxx
> <mailto: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 *Marshall Schor
> *Gesendet:* Freitag, 25. Februar 2011 19:22
> *An:* Maven Integration for Eclipse users mailing list
> *Betreff:* Re: [m2e-users] multi-module projects broken in 0.12.1?
>
> We also use working sets. They are integrated with may aspects of Eclipse.
>
> For instance, you can select one (or more) working sets to do "search"es
> in , to do SVN update - to - head, or commits, etc.
>
> You can collapse (in the package explorer) the "projects" in the working
> sets so you just see the the working set.
>
> And, if it makes sense, you can put a project into more than one working
> set, even...
>
> -Marshall Schor
>
> On 2/24/2011 4:16 PM, Jordan.Hein@xxxxxxxxxxx
> <mailto:Jordan.Hein@xxxxxxxxxxx> wrote:
>
>
> That is a fantastic idea! I have never considered working sets to be
> very useful and had forgotten that functionality even existed in eclipse.
>
> I am going to have to bone up on using working sets, but I think that
> will make this sellable to the rest of the dev team I work with.
>
> -Cheers, -Jordan
>
>
> From:
>
>
>
> Guus der Kinderen <guus.der.kinderen@xxxxxxxxx>
> <mailto:guus.der.kinderen@xxxxxxxxx>
>
> To:
>
>
>
> Maven Integration for Eclipse users mailing list <m2e-users@xxxxxxxxxxx>
> <mailto:m2e-users@xxxxxxxxxxx>
>
> Date:
>
>
>
> 02/24/2011 01:54 PM
>
> Subject:
>
>
>
> Re: [m2e-users] multi-module projects broken in 0.12.1?
>
> Sent by:
>
>
>
> m2e-users-bounces@xxxxxxxxxxx <mailto:m2e-users-bounces@xxxxxxxxxxx>
>
> ------------------------------------------------------------------------
>
>
>
>
> Jordan, try organizing projects using Working Sets (and configure your
> Package Explorer window to use Working Sets for its Top Level Elements
> setting). That has helped me retain most of my sanity when working in
> workspaces that house many projects.
>
> Regards,
>
> Guus
>
> On 24 February 2011 21:29, <Jordan.Hein@xxxxxxxxxxx
> <mailto:Jordan.Hein@xxxxxxxxxxx>> wrote:
>
> Thanks for the info everyone.
>
> I was afraid that this was the case (dropping support for multi-module
> projects). I did as recommended and imported the project again in
> eclipse (not my usual way of checking out a project so it took me a
> while to figure out I needed the subversive integration for m2e) and the
> import created .project and .classpath files for each module and the
> modules appear as separate projects now. So using the import to migrate
> a project forward works. On the down side I now have 18 projects instead
> of just one so that will take some getting used to.
>
> 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.
>
>
>
>
>
> From:
>
>
>
> Asaf Mesika <asaf.mesika@xxxxxxxxx <mailto:asaf.mesika@xxxxxxxxx>>
>
> To:
>
>
>
> Maven Integration for Eclipse users mailing list <m2e-users@xxxxxxxxxxx
> <mailto:m2e-users@xxxxxxxxxxx>>
>
> Date:
>
>
>
> 02/24/2011 12:16 PM
>
> Subject:
>
>
>
> Re: [m2e-users] multi-module projects broken in 0.12.1?
>
> Sent by:
>
>
>
> m2e-users-bounces@xxxxxxxxxxx <mailto:m2e-users-bounces@xxxxxxxxxxx>
>
> ------------------------------------------------------------------------
>
>
>
>
>
> 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
> <mailto: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 / 25671237
> Fax: 069 / 256761237
> E-Mail:oliver.kuntze@xxxxxxxxxxxxxxxxxxx
> <mailto: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>[mailto:m2e-users-bounces@xxxxxxxxxxx
> <mailto:m2e-users-bounces@xxxxxxxxxxx>] *Im Auftrag von
> *Jordan.Hein@xxxxxxxxxxx <mailto:Jordan.Hein@xxxxxxxxxxx>*
> Gesendet:*Mittwoch, 23. Februar 2011 19:38*
> An:* m2e-users@xxxxxxxxxxx <mailto: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 <mailto:m2e-users@xxxxxxxxxxx>_
> _https://dev.eclipse.org/mailman/listinfo/m2e-users
>
> _______________________________________________
> m2e-users mailing list_
> _m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>_
> _https://dev.eclipse.org/mailman/listinfo/m2e-users
>
>
> _______________________________________________
> m2e-users mailing list_
> _m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>_
> _https://dev.eclipse.org/mailman/listinfo/m2e-users
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
>
>
>
>
> _______________________________________________
>
> m2e-users mailing list
>
> m2e-users@xxxxxxxxxxx  <mailto: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
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users



--
Fotografie
http://schutte.name/


Back to the top