Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-24460

Update the maven-jira-plugin to work in Maven 3.

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Tracked Elsewhere
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      When we updated our in-house continuous integration system to use Maven 3 instead of Maven 2, we discovered that one of the plugins was not written in a way that would allow it to function in a Maven 3 environment. Below is the debug output of the build failure.

      I'd very much appreciate it if this could be remedied. There is really no reason that we've seen that would require us to support both Maven 2 (or the 'JIRA SDK') and Maven 3 in our system. Our system builds many different Maven applications and plugins and this is the only plugin that we are blocked on.

      Is there a plan to have this fixed in the future? If so, please give me a rough idea as to when. If not, can I be provided with the source to see if I can submit a patch to fix this?

      [ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-jira-plugin:3.4-SNAPSHOT:copy-bundled-dependencies (default-copy-bundled-dependencies) on project caris-jira-blockinglinks-plugin: Unable to execute mojo: UnsupportedOperationException -> [Help 1]
      org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.atlassian.maven.plugins:maven-jira-plugin:3.4-SNAPSHOT:copy-bundled-dependencies (default-copy-bundled-dependencies) on project caris-jira-blockinglinks-plugin: Unable to execute mojo
              at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
              at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
              at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
              at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
              at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
              at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
              at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
              at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
              at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
              at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
              at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
              at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:597)
              at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
              at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
              at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
              at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
      Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to execute mojo
              at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojo(MojoExecutor.java:106)
              at com.atlassian.maven.plugins.amps.MavenGoals.copyBundledDependencies(MavenGoals.java:167)
              at com.atlassian.maven.plugins.amps.CopyBundledDependenciesMojo.execute(CopyBundledDependenciesMojo.java:21)
              at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
              at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
              ... 19 more
      Caused by: java.lang.UnsupportedOperationException
              at org.apache.maven.plugin.internal.DefaultPluginManager.executeMojo(DefaultPluginManager.java:90)
              at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojo(MojoExecutor.java:104)
              ... 23 more
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              c694693401f4 Tim Astle
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: