[JBoss JIRA] Created: (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
3:12 p.m.
versions for jboss-ejb3-proxy-spi and jboss-ejb3-proxy-impl jars are not declared in the
jboss-as-parent pom's dependency management
------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6988
URL: https://jira.jboss.org/jira/browse/JBAS-6988
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build System
Affects Versions: JBossAS-5.1.0.GA
Reporter: Ian Springer
Assignee: Paul Gier
Fix For: JBossAS-5.2.0.Beta1
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:27 p.m.
New subject: [JBoss JIRA] Commented: (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
[
https://jira.jboss.org/jira/browse/JBAS-6988?page=com.atlassian.jira.plug...
]
Paul Gier commented on JBAS-6988:
---------------------------------
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.
versions for jboss-ejb3-proxy-spi and jboss-ejb3-proxy-impl jars are
not declared in the jboss-as-parent pom's dependency management
------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6988
URL: https://jira.jboss.org/jira/browse/JBAS-6988
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build System
Affects Versions: JBossAS-5.1.0.GA
Reporter: Ian Springer
Assignee: Paul Gier
Fix For: JBossAS-5.2.0.Beta1
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:45 p.m.
New subject: [JBoss JIRA] Resolved: (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
[
https://jira.jboss.org/jira/browse/JBAS-6988?page=com.atlassian.jira.plug...
]
Ian Springer resolved JBAS-6988.
--------------------------------
Resolution: Rejected
versions for jboss-ejb3-proxy-spi and jboss-ejb3-proxy-impl jars are
not declared in the jboss-as-parent pom's dependency management
------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6988
URL: https://jira.jboss.org/jira/browse/JBAS-6988
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build System
Affects Versions: JBossAS-5.1.0.GA
Reporter: Ian Springer
Assignee: Paul Gier
Fix For: JBossAS-5.2.0.Beta1
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:45 p.m.
New subject: [JBoss JIRA] Commented: (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
[
https://jira.jboss.org/jira/browse/JBAS-6988?page=com.atlassian.jira.plug...
]
Ian Springer commented on JBAS-6988:
------------------------------------
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
versions for jboss-ejb3-proxy-spi and jboss-ejb3-proxy-impl jars are
not declared in the jboss-as-parent pom's dependency management
------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6988
URL: https://jira.jboss.org/jira/browse/JBAS-6988
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build System
Affects Versions: JBossAS-5.1.0.GA
Reporter: Ian Springer
Assignee: Paul Gier
Fix For: JBossAS-5.2.0.Beta1
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:48 p.m.
New subject: [JBoss JIRA] Reopened: (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
[
https://jira.jboss.org/jira/browse/JBAS-6988?page=com.atlassian.jira.plug...
]
Ian Springer reopened JBAS-6988:
--------------------------------
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.
versions for jboss-ejb3-proxy-spi and jboss-ejb3-proxy-impl jars are
not declared in the jboss-as-parent pom's dependency management
------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6988
URL: https://jira.jboss.org/jira/browse/JBAS-6988
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build System
Affects Versions: JBossAS-5.1.0.GA
Reporter: Ian Springer
Assignee: Paul Gier
Fix For: JBossAS-5.2.0.Beta1
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:15 a.m.
New subject: [JBoss JIRA] Commented: (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
[
https://jira.jboss.org/jira/browse/JBAS-6988?page=com.atlassian.jira.plug...
]
Paul Gier commented on JBAS-6988:
---------------------------------
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.
versions for jboss-ejb3-proxy-spi and jboss-ejb3-proxy-impl jars are
not declared in the jboss-as-parent pom's dependency management
------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6988
URL: https://jira.jboss.org/jira/browse/JBAS-6988
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build System
Affects Versions: JBossAS-5.1.0.GA
Reporter: Ian Springer
Assignee: Paul Gier
Fix For: JBossAS-5.2.0.Beta1
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:39 a.m.
New subject: [JBoss JIRA] Commented: (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
[
https://jira.jboss.org/jira/browse/JBAS-6988?page=com.atlassian.jira.plug...
]
Andrew Lee Rubinger commented on JBAS-6988:
-------------------------------------------
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
versions for jboss-ejb3-proxy-spi and jboss-ejb3-proxy-impl jars are
not declared in the jboss-as-parent pom's dependency management
------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6988
URL: https://jira.jboss.org/jira/browse/JBAS-6988
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build System
Affects Versions: JBossAS-5.1.0.GA
Reporter: Ian Springer
Assignee: Paul Gier
Fix For: JBossAS-5.2.0.Beta1
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:12 p.m.
New subject: [JBoss JIRA] Closed: (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
[
https://jira.jboss.org/jira/browse/JBAS-6988?page=com.atlassian.jira.plug...
]
Jason T. Greene closed JBAS-6988.
---------------------------------
Resolution: Done
This looks resolved
versions for jboss-ejb3-proxy-spi and jboss-ejb3-proxy-impl jars are
not declared in the jboss-as-parent pom's dependency management
------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6988
URL: https://jira.jboss.org/jira/browse/JBAS-6988
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build System
Affects Versions: JBossAS-5.1.0.GA
Reporter: Ian Springer
Assignee: Paul Gier
Fix For: JBossAS-5.2.0.Beta1
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5614
days inactive
5707
days old
7 comments
4 participants
participants (4)
-
Andrew Lee Rubinger (JIRA) -
Ian Springer (JIRA)
-
Jason T. Greene (JIRA)
-
Paul Gier (JIRA)