Each project (defined shortly) needs to have the url, scm, and site distributionManagement elements defined explicitly.
Project here = * Not a module of a parent project * May or may not have modules within it. Justin -----Original Message----- From: Lesaint Sébastien [mailto:sebastien.lesa...@ginerativ.fr] Sent: Tuesday, January 27, 2009 9:55 AM To: Maven Users List Subject: RE: Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue) Thanks for you answer, Brian. How do I "redefine at the top of my project" so that the URLs are generated the way I want (not appending the artifactId)? Sébastien Lesaint -----Message d'origine----- De : Brian E. Fox [mailto:bri...@reply.infinity.nu] Envoyé : mardi 27 janvier 2009 15:06 À : Maven Users List Objet : RE: Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue) 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.lesa...@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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
