Hugo Lassiège created JENKINS-12877:
---------------------------------------
Summary: Problem to configure perforce plugin and maven release
plugin
Key: JENKINS-12877
URL: https://issues.jenkins-ci.org/browse/JENKINS-12877
Project: Jenkins
Issue Type: Bug
Components: perforce, release
Affects Versions: current
Environment: unix (centos)
jenkins 1.447
perforce plugin 1.3.7
jenkins maven release plugin 0.9.0
Reporter: Hugo Lassiège
Assignee: Peter Hayes
Hi,
I try to use jenkins maven release plugin on Jenkins with a perforce SCM.
However, I have a weird error. In debug mode I see the following messages :
[DEBUG] SCM path in pom: //depot/AirTravelServer/main/
[DEBUG] Executing: /bin/sh -c p4 -p srvpar5p4p01:1992 where
/home/www-data/.jenkins/jobs/ATS-TRUNK-RELEASE/workspace/pom.xml
[DEBUG] p4 can not support a wide charset unless
and the stacktrace :
{code}
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: -2
at java.lang.String.substring(String.java:1937)
at
org.apache.maven.scm.provider.perforce.command.PerforceWhereCommand.getDepotLocation(PerforceWhereCommand.java:117)
at
org.apache.maven.scm.provider.perforce.command.PerforceWhereCommand.getDepotLocation(PerforceWhereCommand.java:61)
at
org.apache.maven.scm.provider.perforce.PerforceScmProvider.getRepoPath(PerforceScmProvider.java:466)
at
org.apache.maven.scm.provider.perforce.command.status.PerforceStatusCommand.executeStatusCommand(PerforceStatusCommand.java:57)
at
org.apache.maven.scm.command.status.AbstractStatusCommand.executeCommand(AbstractStatusCommand.java:44)
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
{code}
The problem is due to : "p4 can not support a wide charset unless"
I've configured P4CHARSET to utf16le-bom and I've tried several different
charsets for P4COMMANDCHARSET : winansi, utf8, none
The problem exists only for maven release plugin. I don't have this error with
mvn install.
Do you know what is the right configuration to make it works ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
