[ 
https://jira.codehaus.org/browse/MRELEASE-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MRELEASE-764:
------------------------------------

    Description: 
Although this was fixed in MRELEASE-759 for Jazz, we still have the same 
problem with SVNKit SVM Provider 
(http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/). The 
logs says something like: 
{noformat}
[INFO] [release:prepare {execution: default-cli}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Verifying that there are no local modifications...
[INFO]   ignoring changes on: **/pom.xml.backup, **/release.properties, 
**/pom.xml.branch, **/pom.xml.next, **/pom.xml.releaseBackup, **/pom.xml.tag
[INFO] SVN status directory: /opt/jenkins_home/.jenkins/jobs/Logica 
Parent/workspace

log4j:WARN No appenders could be found for logger 
(org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.

[JENKINS] Archiving /opt/jenkins_home/.jenkins/jobs/Logica 
Parent/workspace/pom.xml to /opt/jenkins_home/.jenkins/jobs/Logica 
Parent/modules/com.logica$logica-parent/builds/2012-05-29_15-15-41/archive/com.logica/logica-parent/0.0.8-SNAPSHOT/logica-parent-0.0.8-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Cannot prepare the release because you have local modifications : 
[/opt/jenkins_home/.jenkins/jobs/Logica 
Parent/workspace/pom.xml.releaseBackup:unknown]
{noformat}

This is clearly a regression, since it worked with the maven-release-plugin 2.2 
and earlier.

  was:
Although this was fixed in MRELEASE-759 for Jazz, we still have the same 
problem with SVNKit SVM Provider 
(http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/). The 
logs says something like: 

[INFO] [release:prepare {execution: default-cli}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Verifying that there are no local modifications...
[INFO]   ignoring changes on: **/pom.xml.backup, **/release.properties, 
**/pom.xml.branch, **/pom.xml.next, **/pom.xml.releaseBackup, **/pom.xml.tag
[INFO] SVN status directory: /opt/jenkins_home/.jenkins/jobs/Logica 
Parent/workspace

log4j:WARN No appenders could be found for logger 
(org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.

[JENKINS] Archiving /opt/jenkins_home/.jenkins/jobs/Logica 
Parent/workspace/pom.xml to /opt/jenkins_home/.jenkins/jobs/Logica 
Parent/modules/com.logica$logica-parent/builds/2012-05-29_15-15-41/archive/com.logica/logica-parent/0.0.8-SNAPSHOT/logica-parent-0.0.8-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Cannot prepare the release because you have local modifications : 
[/opt/jenkins_home/.jenkins/jobs/Logica 
Parent/workspace/pom.xml.releaseBackup:unknown]

This is clearly a regression, since it worked with the maven-release-plugin 2.2 
and earlier.

    
> Default excludes are not recognized by SVNKit SCM provider
> ----------------------------------------------------------
>
>                 Key: MRELEASE-764
>                 URL: https://jira.codehaus.org/browse/MRELEASE-764
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3.1
>            Reporter: Konrad Windszus
>
> Although this was fixed in MRELEASE-759 for Jazz, we still have the same 
> problem with SVNKit SVM Provider 
> (http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/). 
> The logs says something like: 
> {noformat}
> [INFO] [release:prepare {execution: default-cli}]
> [INFO] Change the default 'svn' provider implementation to 'javasvn'.
> [INFO] Verifying that there are no local modifications...
> [INFO]   ignoring changes on: **/pom.xml.backup, **/release.properties, 
> **/pom.xml.branch, **/pom.xml.next, **/pom.xml.releaseBackup, **/pom.xml.tag
> [INFO] SVN status directory: /opt/jenkins_home/.jenkins/jobs/Logica 
> Parent/workspace
> log4j:WARN No appenders could be found for logger 
> (org.apache.commons.beanutils.converters.BooleanConverter).
> log4j:WARN Please initialize the log4j system properly.
> [JENKINS] Archiving /opt/jenkins_home/.jenkins/jobs/Logica 
> Parent/workspace/pom.xml to /opt/jenkins_home/.jenkins/jobs/Logica 
> Parent/modules/com.logica$logica-parent/builds/2012-05-29_15-15-41/archive/com.logica/logica-parent/0.0.8-SNAPSHOT/logica-parent-0.0.8-SNAPSHOT.pom
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Cannot prepare the release because you have local modifications : 
> [/opt/jenkins_home/.jenkins/jobs/Logica 
> Parent/workspace/pom.xml.releaseBackup:unknown]
> {noformat}
> This is clearly a regression, since it worked with the maven-release-plugin 
> 2.2 and earlier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to