Hi,
the maven-release-plugin uses the scm-api[1] to do the tagging and
committing.
The implementation for perforce can be found at
http://maven.apache.org/scm/maven-scm-providers/maven-scm-provider-perforce/index.html
Also I would try to run Maven with an additional -X (or --debug) to switch
to debug logging.
This should show the commands executed by the scm-provider for perforce.
Robert
[1] http://maven.apache.org/scm/maven-scm-api/index.html
Op Thu, 16 Jan 2014 01:22:40 +0100 schreef Jeff <[email protected]>:
I'm stuck. I don't normally use Perforce. I don't know why the Maven
release process doesn't work with Perforce.
I can pull and build the source. When I use the Jenkins Maven Release
plugin, I give it my personal credentials. My user owns the
Jenkins_master
work space I created. It is the same user used to check out the source
initially.
The error I get is:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare
(default-cli) on project webpulse-parent-pom: Error writing POM:
/home/tomcat7/.jenkins/jobs/my-parent-pom/workspace/pom.xml
(Permission denied) -> [Help 1]
I thought it was because it was read-only but after adding the 'allwrite'
option, I get the error:
[INFO] Checking in modified POMs...
[ERROR] CommandLineException Exit code: 1 - Error in change
specification.
Can't include file(s) not already opened.
Open new files with p4 add, p4 edit, etc.
Doesn't the Maven Perforce connector do a 'p4 edit' before trying to
change/submit the POM?
What am I doing wrong?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
