Maven
  1. Maven
  2. MNG-4843

maven-glassfish-plugin does not work with maven 3.0-RC3 (works with 2.2.1)

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Not A Bug
    • Affects Version/s: 3.0-beta-3
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      maven 3.0-RC3
      Ubuntu Linux
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      Deployments to glassfish don't work with maven 3 (the same steps work with maven 2.2.1). Seems that there is a dependency missing.

      I'm using the following plugin:

      <build>
      <plugins>
      <plugin>
      <groupId>org.glassfish.maven.plugin</groupId>
      <artifactId>maven-glassfish-plugin</artifactId>
      <version>2.1</version>
      ...
      (URL: http://download.java.net/maven/2/org/glassfish/maven/plugin/maven-glassfish-plugin/2.1/)

      mvn org.glassfish.maven.plugin:maven-glassfish-plugin:deploy

      [INFO] Scanning for projects...
      [INFO]
      [INFO] ------------------------------------------------------------------------
      [INFO] Building FIPS 4 FSPM Product Data Service EAR 1.0.0-SNAPSHOT
      [INFO] ------------------------------------------------------------------------
      [INFO]
      [INFO] — maven-glassfish-plugin:2.1:deploy (default-cli) @ com.f10.ips4fspm.connect.prdservices.ear —
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.9-RC4-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.9-RC5-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.9-RC6-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.9-RC7-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.9-RC8-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.9-RC9-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.10-RC3-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.10-RC4-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.10-RC5-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.10-RC6-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.10-RC7-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.12-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.1.0-M2-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.1-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.maven.artifact:maven-artifact:jar:3.0-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.apache.xbean:xbean-reflect:jar:3.4-20080418.173627-4 is missing, no dependency information available
      [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:3.0-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.codehaus.plexus:plexus-component-annotations:jar:1.2.1-SNAPSHOT is missing, no dependency information available
      [WARNING] The POM for org.codehaus.plexus:plexus-container-default:jar:1.2.1-SNAPSHOT is missing, no dependency information available
      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD FAILURE
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 4.227s
      [INFO] Finished at: Thu Sep 30 10:23:21 CEST 2010
      [INFO] Final Memory: 9M/171M
      [INFO] ------------------------------------------------------------------------
      [ERROR] Failed to execute goal org.glassfish.maven.plugin:maven-glassfish-plugin:2.1:deploy (default-cli) on project com.f10.ips4fspm.connect.prdservices.ear: Execution default-cli of goal org.glassfish.maven.plugin:maven-glassfish-plugin:2.1:deploy failed: Plugin org.glassfish.maven.plugin:maven-glassfish-plugin:2.1 or one of its dependencies could not be resolved: Failed to collect dependencies for org.glassfish.maven.plugin:maven-glassfish-plugin:jar:2.1 (): Failed to read artifact descriptor for org.apache.maven:maven-plugin-api:jar:3.0-SONATYPE-688946: Failure to find org.apache.maven:maven-parent:pom:9-SNAPSHOT in http://www.faktorlogik.de:8082/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced -> [Help 1]
      [ERROR]
      [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
      [ERROR] Re-run Maven using the -X switch to enable full debug logging.
      [ERROR]
      [ERROR] For more information about the errors and possible solutions, please read the following articles:
      [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

        Activity

        Hide
        Benjamin Bentmann added a comment - - edited

        The plugin depends on several Maven APIs using the unbounded version range [2.0,). Apart from the fact that this itself is a bad idea, in your environment the range happens to select an unofficial release of maven-plugin-api which inherits from maven-parent:9-SNAPSHOT which is apparently mising in your repo manager.

        So either get the plugin maintainers to use a specific version for their dependencies, override the plugin dependencies in your project with proper versions or ensure your repo mananager doesn't expose broken artifacts to the build.

        Show
        Benjamin Bentmann added a comment - - edited The plugin depends on several Maven APIs using the unbounded version range [2.0,) . Apart from the fact that this itself is a bad idea, in your environment the range happens to select an unofficial release of maven-plugin-api which inherits from maven-parent:9-SNAPSHOT which is apparently mising in your repo manager. So either get the plugin maintainers to use a specific version for their dependencies, override the plugin dependencies in your project with proper versions or ensure your repo mananager doesn't expose broken artifacts to the build.
        Hide
        Vetle Leinonen-Roeim added a comment -
        Show
        Vetle Leinonen-Roeim added a comment - FYI, I have reported it here: https://glassfish.dev.java.net/issues/show_bug.cgi?id=14411

          People

          • Assignee:
            Benjamin Bentmann
            Reporter:
            Ulli Hafner
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: