I didn't find much explaining how the tagBase works or what it is.
Basically, the Parent-POM defines a variable based SCM string:
"scm:cvs:pserver:u...@[host]:/CVSROOT:${cvs_projectName}".
It resolves in the child project in a SCM string such as this one
"scm:cvs:pserver:u...@[host]:/CVSROOT:CVS_CHILD".
The scm string I get is "scm:cvs:pserver:u...@[host]:/CVSROOT:CVS_CHILD/child"
("child" being the artifactId of the child project).
(note: artifactId is usually different from the CVS module name)
I tried to set the tagBase to both
"scm:cvs:pserver:u...@[host]:/CVSROOT:CVS_CHILD" and
"scm:cvs:pserver:u...@[host]:/CVSROOT:CVS_CHILD/tags" but the resulting String
is the same.
I understand how it works in the SVN paradigm, but does tagBase work for CVS at
all?
Sébastien Lesaint
-----Message d'origine-----
De : Lesaint Sébastien [mailto:[email protected]]
Envoyé : mardi 27 janvier 2009 15:16
À : Maven Users List
Objet : RE: Does having a parent POM mean the current POM is a module ? (or a
possible release plugin issue)
Indeed, no, I didn't set the tagBase. Even though I don't understand what it is
yet, I guess it will solve my problem.
I had seen that when reading the documentation but I though it didn't apply to
CVS (the SCM we use).
Thanks Baptiste
Sébastien Lesaint
-----Message d'origine-----
De : [email protected] [mailto:[email protected]] De la part de Baptiste MATHUS
Envoyé : mardi 27 janvier 2009 15:07
À : Maven Users List
Objet : Re: Does having a parent POM mean the current POM is a module ? (or a
possible release plugin issue)
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 <[email protected]>
> 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: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
