Re: [m2e-dev] Nested modules option for multi module projects

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

Proper support for nested project structure requires direct support from
Eclipse platform. We will certainly consider adding support for nested
modules back when/if platform provides such support.

Providing even partially working generic support for nested modules in
m2e without platform support proved to be very expensive both from code
and support point of view for m2e developers. We believe our very
limited resources are better spent on other features.

Given recent changes to m2e core I believe it is feasible to implement
basic/limited nested project support as an external eclipse bundle. I
can't promise this will be trivial, but we will certainly help if
somebody is interested to work on such m2e extension.

--
Regards,
Igor

On 11-01-13 11:19 AM, Kuntze, Oliver (UIT) wrote:
> Hi all,
>
> since Igor(Fedorenko)asked to address this issue in the dev mailing
> list, I’d like to take the chance and join the choir of petitioners for
> re-introducing the“nested modules option”for multimoduleprojects
> (availableuntilversion0.10).
>
> For our organizationsupport for nested modules isessentialsince
> ourglobal EAI platform is based on JBI/Servicemixand one deployable unit
> in JBI consists of a let’s say 5-12 maven modules (depending on complexity).
>
> Let me give you a brief ideaof what our module structure islike:
>
> +…
>
> + depot-process
>
> ++ order-process
>
> +++ data
>
> ++++ xslt
>
> +++++ order-mapping.xsl
>
> +++++…
>
> +++++ pom.xml
>
> ++++ ... (drools, sql, etc.)
>
> +++sa
>
> ++++ order-process-sa
>
> +++++ pom.xml
>
> ++++ order-process-jms-su
>
> +++++ pom.xml
>
> ++++ order-process-xslt-su
>
> +++++ pom.xml
>
> ++++ order-process-drbms-su
>
> +++++ pom.xml
>
> ++++ pom.xml
>
> +++ pom.xml
>
> ++payment-process
>
> ++…
>
> ++ pom.xml
>
> +…
>
> + pom.xml
>
> And this is notbecausewe love complexity but because the way JBI’s
> component concept of service assemblies being comprised of service units
> dictates it.
>
> In the versionsabove 0.10 m2eclipse not only leaves us with a mess
> ofhundreds ofsingle eclipse projectsall on the same flattened hierarchy
> level.
>
> What is even worse is, thatwhenm2eclipsetries to import the“data”modules
> of our applications/processes it fails becauseit tries to create eclipse
> projects of equal name.
>
> I am a huge fan of eclipse and would hate to see our
> organizationsstandard ide being moved to netbeans.
>
> Since I’m responsible fortheannualreleases of our EAI
> platform,includingthe tool chain,I have to present themidtermstrategy
> regarding this platform to our bosses.Staying with m2eclipse 0.10
> forever naturally isn’t an option.But upgrading to a higher version
> would render our whole EAI development impossible.
>
> So please please pleaseplease bring back the nested modules option.
> Don’tabandon meand force me to tell our management, we have to shift to
> another ide (Well, netbeansisfar from optimal regarding nested modules
> but at leastit has no problem with our“data”modules).
>
> I guess we are not the only ones with fine grained deployables in our
> release management process, relying on nested modules.
>
> Any consideration of bringing back this highly valuable feature would be
> greatly appreciated!
>
> Thanks in advance!
>
> Cheers
>
> Oliver