I am using -DgenerateReleasePoms=true. When I run release:prepare, maven creates and adds the release-pom.xml to perforce. Then, when I run release:perform, maven deletes release-pom.xml from perforce. Then, when I run release:prepare for a subsequent release, maven fails to readd release-pom.xml to perforce and gives this error 'Unknown input: //pem_rd/portal/development/code/mainbea10/maven-jee-shared-lib-plugin/release-pom.xml - can't add (already opened for edit)' which comes directly from perforce.
Is this a bug? Anyone else using perforce + generateReleasePoms=true successfully? -- View this message in context: http://www.nabble.com/problem-with-release-plugin-%2B-perforce-tp14300591s177p14300591.html Sent from the Maven - SCM mailing list archive at Nabble.com.
