You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by "Jeudy, Guillaume" <gj...@teksystems.com> on 2008/11/21 20:44:04 UTC

Maven multi-module setup hierarchical or flat folder hierarchy

Hi Maven gurus,
 
I would like to know what is the best recommended way of definining maven multi-module projects?
 
Is it the hierarchical ?
 
parent/pom.xml
parent/childA/pom.xml
parent/childB/pom.xml
 
or flat-structure ?
 
parent/pom.xml
childA/pom.xml
childB/pom.xml
 
 
I'm using eclipseIDE with m2eclipse and hierarchical multi-module structure and the maven release plugin to manage my release cycle. My setup works reasonably well but I have seen others using the flat-structure.
 
Can someone tell me what are the pros and cons of both approaches? I'm not sure which one is best.
 
Thanks,
-Guillaume


____________________________________________________________________________________________________
This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.

RE: Maven multi-module setup hierarchical or flat folder hierarchy

Posted by "Jeudy, Guillaume" <gj...@teksystems.com>.

Thanks for the reply,

I'm looking at using hot deploy(as described in this post: http://www.smies.com/blog/?p=30) and run tests from inside eclipseIDE. To me it seems like having a flat-structure where each submodule becomes its own eclipseIDE project would help me achieve that.

In my opinion if I can use hot deploy and run tests more easily (not having to tweak the working dir of my test runconfig) then I should adopt the flat-structure.

My main concern is the issue with the release plugin with flat-structure multi-module projects as described here: http://jira.codehaus.org/browse/MRELEASE-261. 

Apparently there is a workaround to the release plugin limitation (one needs to define a build pom and a parent pom). The release plugin uses the build pom.

Have others fulfilled the above requirements with a flat-structure multi-module project ?

Regards,
-Guillaume

________________________________

From: Walid "jo" Gedeon [mailto:wgedeon@gmail.com]
Sent: Fri 21/11/2008 7:14 PM
To: Maven Users List
Subject: Re: Maven multi-module setup hierarchical or flat folder hierarchy

Hello Guillaume,
I must say I've tried both with almost equal success, the one positive
advantage of the hierarchical option is that it allows the option of having
multiple depths of hierarchy without the quick growth of the number of
folders on a level. It also helps organize the structure when there's a
large number of sub-projects.

My 2 cents :-D
w

On Fri, Nov 21, 2008 at 8:44 PM, Jeudy, Guillaume <gj...@teksystems.com>wrote:

> Hi Maven gurus,
>
> I would like to know what is the best recommended way of definining maven
> multi-module projects?
>
> Is it the hierarchical ?
>
> parent/pom.xml
> parent/childA/pom.xml
> parent/childB/pom.xml
>
> or flat-structure ?
>
> parent/pom.xml
> childA/pom.xml
> childB/pom.xml
>
>
> I'm using eclipseIDE with m2eclipse and hierarchical multi-module structure
> and the maven release plugin to manage my release cycle. My setup works
> reasonably well but I have seen others using the flat-structure.
>
> Can someone tell me what are the pros and cons of both approaches? I'm not
> sure which one is best.
>
> Thanks,
> -Guillaume
>
>
>
> ____________________________________________________________________________________________________
> This electronic mail (including any attachments) may contain information
> that is privileged, confidential, and/or otherwise protected from disclosure
> to anyone other than its intended recipient(s). Any dissemination or use of
> this electronic email or its contents (including any attachments) by persons
> other than the intended recipient(s) is strictly prohibited. If you have
> received this message in error, please notify us immediately by reply email
> so that we may correct our internal records. Please then delete the original
> message (including any attachments) in its entirety. Thank you.
>

____________________________________________________________________________________________________
This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.

Re: Maven multi-module setup hierarchical or flat folder hierarchy

Posted by "Walid \"jo\" Gedeon" <wg...@gmail.com>.

Hello Guillaume,
I must say I've tried both with almost equal success, the one positive
advantage of the hierarchical option is that it allows the option of having
multiple depths of hierarchy without the quick growth of the number of
folders on a level. It also helps organize the structure when there's a
large number of sub-projects.

My 2 cents :-D
w

On Fri, Nov 21, 2008 at 8:44 PM, Jeudy, Guillaume <gj...@teksystems.com>wrote:

> Hi Maven gurus,
>
> I would like to know what is the best recommended way of definining maven
> multi-module projects?
>
> Is it the hierarchical ?
>
> parent/pom.xml
> parent/childA/pom.xml
> parent/childB/pom.xml
>
> or flat-structure ?
>
> parent/pom.xml
> childA/pom.xml
> childB/pom.xml
>
>
> I'm using eclipseIDE with m2eclipse and hierarchical multi-module structure
> and the maven release plugin to manage my release cycle. My setup works
> reasonably well but I have seen others using the flat-structure.
>
> Can someone tell me what are the pros and cons of both approaches? I'm not
> sure which one is best.
>
> Thanks,
> -Guillaume
>
>
>
> ____________________________________________________________________________________________________
> This electronic mail (including any attachments) may contain information
> that is privileged, confidential, and/or otherwise protected from disclosure
> to anyone other than its intended recipient(s). Any dissemination or use of
> this electronic email or its contents (including any attachments) by persons
> other than the intended recipient(s) is strictly prohibited. If you have
> received this message in error, please notify us immediately by reply email
> so that we may correct our internal records. Please then delete the original
> message (including any attachments) in its entirety. Thank you.
>