Bob, I suggest you look through MRELEASE. There's a number of issues which sound like they cover your problems.
-----Original Message----- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 25, 2006 6:44 PM To: Maven Users List Subject: RE: Repository Problem with Release Plugin Hey, Brett! I see that you are making a bunch of changes on the release plugin. Is this problem something that is likely to be fixed already, something that I need to file a JIRA on, or a problem with something other than the release plugin? -----Original Message----- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Monday, April 03, 2006 05:47 To: Maven Users List Subject: RE: Repository Problem with Release Plugin Anybody have any ideas? I can file a JIRA on this but I don't know if the problem is that the release plugin is building a bad POM or if the POM is not getting parsed correctly (or if I'm just doing something stupid which is always a possibility). -----Original Message----- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 29, 2006 12:23 To: Maven Users List Subject: Repository Problem with Release Plugin I am starting to try to use the release plugin to do releases, and I am finding a problem. I'm not sure if this is a bug with the release plugin, some other part of Maven 2.0.3, or just a bad POM. My original POM defined the deployment repository as: <repository> <id>theid</id> <name>thename</name> <url>file:///the/url</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>true</enabled> <updatePolicy>daily</updatePolicy> <checksumPolicy>fail</checksumPolicy> </snapshots> </repository> When the release plugin gets done making the new POM, the <id>, <name>, and <url> get moved to the end of the <repository> stanza and the <releases>...</releases> lines are converted to "<releases />" (diff attached below). Once this happens, modules of this project are no longer looking at any repositories other than "central" for releases. I discovered this when I upgraded from 2.0.2 to 2.0.3 and cleared my local repository to ensure that I had the latest plugins; my released projects failed to even parse because the released parent project could no longer be found (those projects access the repository via http; the diff below came from a sample I created to test the problem which accesses a temporary repository via file). Does anybody have a clue what might be wrong? ---------- Diff of changes made by release plugin ---------- --- ../../save/parent-pom.xml.orig 2006-03-29 08:55:22.000000000 -0700 +++ pom.xml 2006-03-29 09:03:07.000000000 -0700 @@ -1,12 +1,11 @@ -<?xml version="1.0" encoding="UTF-8"?> -<project> +<?xml version="1.0" encoding="UTF-8"?><project> <modelVersion>4.0.0</modelVersion> <groupId>test</groupId> <artifactId>parent</artifactId> <packaging>pom</packaging> <name>Release Test Parent</name> - <version>1.0</version> - <url>http://www.home.com/</url> + <version>1.1-SNAPSHOT</version> + <url>http://www.home.com</url> <inceptionYear>2004</inceptionYear> <developers> <developer> @@ -43,94 +42,81 @@ </modules> <repositories> <repository> - <id>dev</id> - <name>Test Development Repository</name> - <url>file:///tmp/snapshot</url> <releases> <enabled>false</enabled> </releases> <snapshots> - <enabled>true</enabled> <updatePolicy>daily</updatePolicy> <checksumPolicy>fail</checksumPolicy> </snapshots> + <id>dev</id> + <name>Test Development Repository</name> + <url>file:///tmp/snapshot</url> </repository> <repository> - <id>rel</id> - <name>Test Release Repository</name> - <url>file:///tmp/release</url> - <releases> - <enabled>true</enabled> - </releases> + <releases /> <snapshots> <enabled>false</enabled> </snapshots> + <id>rel</id> + <name>Test Release Repository</name> + <url>file:///tmp/release</url> </repository> </repositories> <pluginRepositories> <pluginRepository> - <id>rel</id> - <name>Test Release Repository</name> - <url>file:///tmp/release</url> - <releases> - <enabled>true</enabled> - </releases> + <releases /> <snapshots> <enabled>false</enabled> </snapshots> + <id>rel</id> + <name>Test Release Repository</name> + <url>file:///tmp/release</url> </pluginRepository> <pluginRepository> - <id>dev</id> - <name>Test Development Repository</name> - <url>file:///tmp/snapshot</url> <releases> <enabled>false</enabled> </releases> <snapshots> - <enabled>true</enabled> <updatePolicy>daily</updatePolicy> <checksumPolicy>fail</checksumPolicy> </snapshots> + <id>dev</id> + <name>Test Development Repository</name> + <url>file:///tmp/snapshot</url> </pluginRepository> <pluginRepository> - <id>codehaus-plugins</id> - <url>http://dist.codehaus.org/</url> + <releases /> <snapshots> - <enabled>true</enabled> <updatePolicy>daily</updatePolicy> <checksumPolicy>fail</checksumPolicy> </snapshots> - <releases> - <enabled>true</enabled> - </releases> + <id>codehaus-plugins</id> + <url>http://dist.codehaus.org/</url> </pluginRepository> </pluginRepositories> <reporting> <plugins> <plugin> - <groupId>org.codehaus.mojo</groupId> - <artifactId>surefire-report-maven-plugin</artifactId> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-project-info-reports-plugin</artifactId> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-checkstyle-plugin</artifactId> </plugin> <plugin> - <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-javadoc-plugin</artifactId> </plugin> <plugin> - <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-pmd-plugin</artifactId> </plugin> <plugin> + <artifactId>maven-project-info-reports-plugin</artifactId> + </plugin> + <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jxr-maven-plugin</artifactId> </plugin> + <plugin> + <groupId>org.codehaus.mojo</groupId> + <artifactId>surefire-report-maven-plugin</artifactId> + </plugin> </plugins> </reporting> <distributionManagement> --------------------------------------------------------------------- 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] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. --------------------------------------------------------------------- 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]
