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 <sebastien.lesa...@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-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
