Application Server 3  4  5 and 6
  1. Application Server 3 4 5 and 6
  2. JBAS-6988

versions for jboss-ejb3-proxy-spi and jboss-ejb3-proxy-impl jars are not declared in the jboss-as-parent pom's dependency management

    Details

    • Type: Bug Bug
    • Status: Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: JBossAS-5.1.0.GA
    • Fix Version/s: 6.0.0.M1
    • Component/s: Build System
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      Versions for the following two deps are not declared in the jboss-as-parent pom's dependency management:

      <dependency>
      <groupId>org.jboss.ejb3</groupId>
      <artifactId>jboss-ejb3-proxy-spi</artifactId>
      <version>1.0.1-SNAPSHOT</version>
      <classifier>client</classifier>
      </dependency>

      <dependency>
      <groupId>org.jboss.ejb3</groupId>
      <artifactId>jboss-ejb3-proxy-impl</artifactId>
      <version>1.0.3-SNAPSHOT</version>
      <classifier>client</classifier>
      </dependency>

      Note, this needs to be fixed in both the 5.1.x branch and the EAP5 branch (and possibly in trunk).

        Gliffy Diagrams

          Activity

          Hide
          Paul Gier added a comment -

          Those are purposely not declared in the jboss-as-parent pom. They are defined in the component-matrix (parent of jboss-as-parent) with all the external AS components. The goal is/was that the component-matrix could be used to sync dependency versions with the versions that AS is using. The only dependency versions in the jboss-as-parent pom are the actual AS modules.

          Show
          Paul Gier added a comment - Those are purposely not declared in the jboss-as-parent pom. They are defined in the component-matrix (parent of jboss-as-parent) with all the external AS components. The goal is/was that the component-matrix could be used to sync dependency versions with the versions that AS is using. The only dependency versions in the jboss-as-parent pom are the actual AS modules.
          Hide
          Ian Springer added a comment -

          Ah, ok.

          So what I was trying to do to pull all the versions for AS modules as well as external components into the jboss-as-5 plugin's pom was:

          <dependencyManagement>
          <dependencies>
          <dependency>
          <groupId>org.jboss.jbossas</groupId>
          <artifactId>jboss-as-parent</artifactId>
          <version>$

          {jbossas.version}</version>
          <type>pom</type>
          <scope>import</scope>
          </dependency>
          </dependencies>
          </dependencyManagement>

          I would have thought this would also pull in jboss-as-parent's ancestor pom's, but it looks like the import is not transitive in that sense. Changing to:

          <dependencyManagement>
          <dependencies>
          <dependency>
          <groupId>org.jboss.jbossas</groupId>
          <artifactId>jboss-as-parent</artifactId>
          <version>${jbossas.version}

          </version>
          <type>pom</type>
          <scope>import</scope>
          </dependency>
          <dependency>
          <groupId>org.jboss.jbossas</groupId>
          <artifactId>jboss-as-component-matrix</artifactId>
          <version>$

          {jbossas.version}

          </version>
          <type>pom</type>
          <scope>import</scope>
          </dependency>
          </dependencies>
          </dependencyManagement>

          did the trick (i.e. I was able to declare the two ejb3-proxy deps without specifying versions).

          Thanks,
          Ian

          Show
          Ian Springer added a comment - Ah, ok. So what I was trying to do to pull all the versions for AS modules as well as external components into the jboss-as-5 plugin's pom was: <dependencyManagement> <dependencies> <dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-parent</artifactId> <version>$ {jbossas.version}</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> I would have thought this would also pull in jboss-as-parent's ancestor pom's, but it looks like the import is not transitive in that sense. Changing to: <dependencyManagement> <dependencies> <dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-parent</artifactId> <version>${jbossas.version} </version> <type>pom</type> <scope>import</scope> </dependency> <dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-component-matrix</artifactId> <version>$ {jbossas.version} </version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> did the trick (i.e. I was able to declare the two ejb3-proxy deps without specifying versions). Thanks, Ian
          Hide
          Ian Springer added a comment -

          Paul,

          What about this one?

          <dependency>
          <groupId>org.jboss.ejb3</groupId>
          <artifactId>jboss-ejb3-ext-api</artifactId>
          <!-<version>1.0.0</version>->
          <scope>runtime</scope>
          </dependency>

          Its version is still not being resolved even when I import both jboss-as-parent and component-matrix.

          Show
          Ian Springer added a comment - Paul, What about this one? <dependency> <groupId>org.jboss.ejb3</groupId> <artifactId>jboss-ejb3-ext-api</artifactId> <!- <version>1.0.0</version> -> <scope>runtime</scope> </dependency> Its version is still not being resolved even when I import both jboss-as-parent and component-matrix.
          Hide
          Paul Gier added a comment -

          Looks like jboss-ejb3-ext-api is currently being pulled in transitively and is not dependency managed. I'm not sure if this was intentional or not.

          Show
          Paul Gier added a comment - Looks like jboss-ejb3-ext-api is currently being pulled in transitively and is not dependency managed. I'm not sure if this was intentional or not.
          Hide
          Andrew Rubinger added a comment -

          All server libraries (ie. not *-client artifacts) should be pulled in via org.jboss.ejb3:jboss-ejb3 (so long as they're transitive deps of jboss-ejb). The only reason the client classifiers are explicitly defined is because Maven doesn't lock the same version among all classifiers (and improper versions can leak out if we don't).

          Server libs to be explicitly-declared are currently:

          version.org.jboss.ejb3
          version.org.jboss.ejb3.endpoint.deployer

          S,
          ALR

          Show
          Andrew Rubinger added a comment - All server libraries (ie. not *-client artifacts) should be pulled in via org.jboss.ejb3:jboss-ejb3 (so long as they're transitive deps of jboss-ejb). The only reason the client classifiers are explicitly defined is because Maven doesn't lock the same version among all classifiers (and improper versions can leak out if we don't). Server libs to be explicitly-declared are currently: version.org.jboss.ejb3 version.org.jboss.ejb3.endpoint.deployer S, ALR
          Hide
          Jason Greene added a comment -

          This looks resolved

          Show
          Jason Greene added a comment - This looks resolved

            People

            • Assignee:
              Paul Gier
              Reporter:
              Ian Springer
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development