You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jeff Thomas (Jira)" <ji...@apache.org> on 2023/07/19 12:38:00 UTC

[jira] [Created] (SCM-1010) Switching from JGit Maven SCM 2.0.0 to 2.0.1 breaks build - StringUtils

Jeff Thomas created SCM-1010:
--------------------------------

             Summary: Switching from JGit Maven SCM 2.0.0 to 2.0.1 breaks build - StringUtils
                 Key: SCM-1010
                 URL: https://issues.apache.org/jira/browse/SCM-1010
             Project: Maven SCM
          Issue Type: Bug
          Components: maven-scm-provider-jgit
    Affects Versions: 2.0.1
         Environment: Windows, Maven 3.9.2, JDK 17 (temurin 17.0.7)
            Reporter: Jeff Thomas


I have a strange behavior in our build when I upgrade the 'maven-scm-provider-jgit' from 2.0.0 to 2.0.1 which I believe might be related to the change MNG-6825.

If I use 2.0.0 everything works fine.

Using 2.0.1 causes this error in another plugin (I have changed nothing else in my POM).
{noformat}
[ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:3.0.0:create (default) on project pwc-webapp-pwcng: Execution default of goal org.codehaus.mojo:buildnumber-maven-plugin:3.0.0:create failed: A required class was missing while executing org.codehaus.mojo:buildnumber-maven-plugin:3.0.0:create: org/apache/commons/lang3/StringUtils{noformat}
I know the reported error is for the buildnumber-maven-plugin, but this plugin works fine until I switch to 2.0.1

I can't really explain how one plugin is affecting another plugin in this way...hopefully you folks have an idea. :)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)