You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Lesaint Sébastien <se...@ginerativ.fr> on 2009/01/27 15:01:02 UTC

Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue)

Hello,

I want to use a parent POM as a way to easily give some organisation specific information to the new projects in our company or the old one being mavenized.

I don't want to declare all the projects of my company as being a module of this parent POM. It doesn't make much sense. So the parent POM has no <modules> tag.

When using the release plugin, though, I realized it is considering the project having a parent POM as a module (therefore adding the module name to the SCM string).

So, I am wondering:
 - does having a parent POM make the current POM a module ?
 - If so, how can I implement this organisation POM stuff I need ?
 - If not, is there something wrong with the way I use the release plugin or is there an option to avoid the SCM string problem ?

Thanks for any insight on this matter,

Sébastien Lesaint


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue)

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
The parent / child relationship != modules. That is a given pom can inherit from one parent and be aggregated as a module via another. It is true that usually they are the same, but for top level poms (corporate poms or team poms we call them) you usually would not have any modules even though everything inherits from it.

However, urls are generated using the inheritance tree and each artifactId is inserted along the way. If this isn't what you want, then it needs to be redefined at the top of your project. Then the modules of that project would correctly inherit the url.

-----Original Message-----
From: Lesaint Sébastien [mailto:sebastien.lesaint@ginerativ.fr] 
Sent: Tuesday, January 27, 2009 9:01 AM
To: Maven Users List
Subject: Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue)

Hello,

I want to use a parent POM as a way to easily give some organisation specific information to the new projects in our company or the old one being mavenized.

I don't want to declare all the projects of my company as being a module of this parent POM. It doesn't make much sense. So the parent POM has no <modules> tag.

When using the release plugin, though, I realized it is considering the project having a parent POM as a module (therefore adding the module name to the SCM string).

So, I am wondering:
 - does having a parent POM make the current POM a module ?
 - If so, how can I implement this organisation POM stuff I need ?
 - If not, is there something wrong with the way I use the release plugin or is there an option to avoid the SCM string problem ?

Thanks for any insight on this matter,

Sébastien Lesaint


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


Re: Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue)

Posted by Baptiste MATHUS <ml...@batmat.net>.
We have a parent pom for the exact kind of things you speak about. But our
projects are not modules (at least not all). So no.
Your problem with scm tag might just be related to the fact you didn't set
the maven-release-plugin tagBase configuration?

See http://maven.apache.org/plugins/maven-release-plugin/usage.html for more
information.

Cheers.

2009/1/27 Lesaint Sébastien <se...@ginerativ.fr>

> Hello,
>
> I want to use a parent POM as a way to easily give some organisation
> specific information to the new projects in our company or the old one being
> mavenized.
>
> I don't want to declare all the projects of my company as being a module of
> this parent POM. It doesn't make much sense. So the parent POM has no
> <modules> tag.
>
> When using the release plugin, though, I realized it is considering the
> project having a parent POM as a module (therefore adding the module name to
> the SCM string).
>
> So, I am wondering:
>  - does having a parent POM make the current POM a module ?
>  - If so, how can I implement this organisation POM stuff I need ?
>  - If not, is there something wrong with the way I use the release plugin
> or is there an option to avoid the SCM string problem ?
>
> Thanks for any insight on this matter,
>
> Sébastien Lesaint
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !