You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Nick Stolwijk <ni...@planet.nl> on 2007/06/11 17:06:51 UTC
Best Practices for Maven multi multi module
I've a question about Best Practices.
We have a maven project with 4 submodules. Now we want to add three, but
those are more related to each other then the other ones.
Is it better to let that be in the name, like:
parent-project
child-common
child-core
child-web
child-datatransfer-webapp
child-datatransfer-child1
child-datatransfer-child2
Or to make them sub sub modules, like:
parent-project
child-common
child-core
child-web
child-datatransfer
child-datatransfer-webapp
child-datatransfer-child1
child-datatransfer-child2
In this second case is there also the problem with the groupsId, does
the sub sub children have the same groupsId as the superparent or
something with the artifactId of the their parent (child-datatransfer).
Has someone experience with this or any Tips and Tricks?
With regards,
Nick Stolwijk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Best Practices for Maven multi multi module
Posted by Brett Porter <br...@gmail.com>.
I would suggest considering how you intend to build the application.
- Would you ever work on datatransfer as a subset?
- Would you ever build just those modules?
- Would these modules have their own group ID?
- Do the modules share common elements that the rest of the projects
don't (ie, do you need another level of inheritence)?
If you're answering yes here, I'd break it into a module with submodules.
- Brett
On 12/06/07, Nick Stolwijk <ni...@planet.nl> wrote:
> I've a question about Best Practices.
>
> We have a maven project with 4 submodules. Now we want to add three, but
> those are more related to each other then the other ones.
>
> Is it better to let that be in the name, like:
>
> parent-project
> child-common
> child-core
> child-web
> child-datatransfer-webapp
> child-datatransfer-child1
> child-datatransfer-child2
>
> Or to make them sub sub modules, like:
>
> parent-project
> child-common
> child-core
> child-web
> child-datatransfer
> child-datatransfer-webapp
> child-datatransfer-child1
> child-datatransfer-child2
>
> In this second case is there also the problem with the groupsId, does
> the sub sub children have the same groupsId as the superparent or
> something with the artifactId of the their parent (child-datatransfer).
>
> Has someone experience with this or any Tips and Tricks?
>
> With regards,
>
> Nick Stolwijk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org