[jboss-jira] [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
Andrew Lee Rubinger (JIRA)
jira-events at lists.jboss.org
Fri May 29 09:39:56 EDT 2009
[ https://jira.jboss.org/jira/browse/JBAS-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12469915#action_12469915 ]
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
More information about the jboss-jira
mailing list