Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Duplicate
    • Component/s: unleash-plugin
    • Labels:
      None
    • Environment:
    • Similar Issues:

      Description

      Created a simple maven project, ticked Unleash, left the defaults as is, triggered the plugin, left the defaults as is:

      [ERROR] Failed to execute goal com.itemis.maven.plugins:unleash-maven-plugin:2.2.3:perform (default-cli) on project promotion-parent: Execution default-cli of goal com.itemis.maven.plugins:unleash-maven-plugin:2.2.3:perform failed: An API incompatibility was encountered while executing com.itemis.maven.plugins:unleash-maven-plugin:2.2.3:perform: java.lang.LinkageError: loader constraint violation: when resolving overridden method "org.jboss.weld.AbstractCDI.select(Ljavax/enterprise/util/TypeLiteral;[Ljava/lang/annotation/Annotation;)Ljavax/enterprise/inject/Instance;" the class loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm) of the current class, org/jboss/weld/AbstractCDI, and its superclass loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm), have different Class objects for the type /annotation/Annotation;)Ljavax/enterprise/inject/Instance; used in the signature
      [ERROR] -----------------------------------------------------
      [ERROR] realm = plugin>com.itemis.maven.plugins:unleash-maven-plugin:2.2.3
      [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
      [ERROR] urls[0] = file:/home/jenkins/.m2/repository/com/itemis/maven/plugins/unleash-maven-plugin/2.2.3/unleash-maven-plugin-2.2.3.jar
      [ERROR] urls[1] = file:/home/jenkins/.m2/repository/com/itemis/maven/plugins/unleash-scm-provider-git/2.0.2/unleash-scm-provider-git-2.0.2.jar

        Attachments

          Activity

          Hide
          alevinetx Adam L added a comment -

          had the plugin in the pom in pluginmanagement, not plugins. sorry, pebcak

          Show
          alevinetx Adam L added a comment - had the plugin in the pom in pluginmanagement, not plugins. sorry, pebcak
          Hide
          alevinetx Adam L added a comment -

          nope.. subsequent runs produced the same error.

          Please let me know what I can set/provide to help figure out what's wrong.. It could very well be user error again.

          The one time it did run successfully, after i moved the plugin to the proper location, there were no changes in the artifacts. The pom versions were still the same as before i ran the promotion process.

          Show
          alevinetx Adam L added a comment - nope.. subsequent runs produced the same error. Please let me know what I can set/provide to help figure out what's wrong.. It could very well be user error again. The one time it did run successfully, after i moved the plugin to the proper location, there were no changes in the artifacts. The pom versions were still the same as before i ran the promotion process.
          Hide
          shillner Stanley Hillner added a comment -

          Hi, listing the plugin in the plugin-management is the way to go!
          I think the error is not related to the Jenkins plugin but rather a plugin issue.
          Can you try to run the release process (without installing and deploying the artifacts) locally without Jenkins? Furthermore I'd need some more details like the Maven version, the log output from your local invocation and maybe the project setup (POM).

          I'll close this issue because I've created a new issue for the plugin itself: unleash-maven-plugin (#58)

          Show
          shillner Stanley Hillner added a comment - Hi, listing the plugin in the plugin-management is the way to go! I think the error is not related to the Jenkins plugin but rather a plugin issue. Can you try to run the release process (without installing and deploying the artifacts) locally without Jenkins? Furthermore I'd need some more details like the Maven version, the log output from your local invocation and maybe the project setup (POM). I'll close this issue because I've created a new issue for the plugin itself: unleash-maven-plugin (#58)

            People

            • Assignee:
              shillner Stanley Hillner
              Reporter:
              alevinetx Adam L
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: