[jboss-jira] [JBoss JIRA] Closed: (JBAS-8326) Invalid dependency in jboss-as-jmxpom
Paul Gier (JIRA)
jira-events at lists.jboss.org
Fri Dec 17 15:20:18 EST 2010
[ https://issues.jboss.org/browse/JBAS-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier closed JBAS-8326.
---------------------------
Fix Version/s: 6.0.0.Final
Resolution: Out of Date
The jmx module was refactored out of jbossas in JBAS-6539, so I believe the relevant POMs are working now.
> Invalid dependency in jboss-as-jmxpom
> -------------------------------------
>
> Key: JBAS-8326
> URL: https://issues.jboss.org/browse/JBAS-8326
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: JBossAS-5.1.0.GA
> Environment: Maven 2.0.10, JBossAS 5.1.0.GA
> Reporter: Martin Höller
> Assignee: Paul Gier
> Labels: dependency, jboss-as-j2se, jboss-as-jmx, maven, test, test-jar
> Fix For: 6.0.0.Final
>
>
> The maven module with groupId "org.jboss.jbossas" and artifactId "jboss-as-jmx" has a dependency to jboss-as-j2se. This might be ok. However, the dependency is declared twice, the second time with a type of "test-jar" but not with scope test. This prevents it from beeing used as a dependency in an EAR, as the maven-ear-plugin doesn't know (and shouldn't need to know) how to handle artifacts of type test-jar. It probably should't be packaged in an EAR anyway, but the dependency nevertheless seems wrong.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list