I just do it this way for the company pom (-DperformRelease=true) because it would be pain if the version number for the company pom has been increased and all other projects defining this one as parent has to be edited.
When i edit and doing "mvn clean deploy -DperformRelease=true -U -X" for the company pom i can see that the local repository has got the change. This is good so far. But what is about the other developers still having the old company pom in their local repository (using the same version number)? brgds Dominique Boeckli -----Original Message----- From: Siegmann Daniel, NY [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 10:30 PM To: Maven Users List Subject: RE: How to deploy corporate-pom? <<How do I package the corporate pom? Do I just upload it to archiva in a directory called corporate-pom with just the pom.xml file in there?>> No. This is a Maven project like any other. Just have the following in your POM: <project> <packaging>pom</packaging> ... </project> Then use the Maven deploy plugin ("mvn deploy"). Note that you should follow standard release procedure. i.e. if you are not releasing a snapshot you should set "-DperformRelease=true" and you should have this tagged in your version control system (or just use the release plugin). -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 --------------------------------------------------------------------- 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]