[arquillian-issues] [JBoss JIRA] (ARQ-740) jboss-as-arquillian-container-managed 7.0.2.Final ships with jboss-logging 3.0.0.GA, but some of its modules require a higher version: jboss-logging 3.0.1.GA. Same for xnio-api and jbosgi-vfs.

[Aslak Knutsen (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665455#comment-12665455 ] 

Aslak Knutsen commented on ARQ-740:
-----------------------------------

Is this the same for 7.1.0.CR1?
                
> jboss-as-arquillian-container-managed 7.0.2.Final ships with jboss-logging 3.0.0.GA, but some of its modules require a higher version: jboss-logging 3.0.1.GA. Same for xnio-api and jbosgi-vfs.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARQ-740
>                 URL: https://issues.jboss.org/browse/ARQ-740
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Geoffrey De Smet
>            Priority: Trivial
>
> The xnio-api is probably the most dangerous one of these 3.
> It ships with xnio-api 3.0.0.Beta2, but some code requires 3.0.0.Beta3.
> {code}
> IncompatibleDependencyOverwrite error for org.jboss.logging:jboss-logging:3.0.0.GA paths to dependency are:
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.sasl:jboss-sasl:1.0.0.Beta2
>       +-org.jboss.logging:jboss-logging:3.0.0.GA
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.as:jboss-as-arquillian-testenricher-msc:7.0.2.Final
>         +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
>         +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
>         +-org.jboss.as:jboss-as-protocol:7.0.2.Final
>           +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
>         +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.5
>           +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
>         +-org.jboss.as:jboss-as-protocol:7.0.2.Final
>           +-org.jboss.remoting3:jboss-remoting:3.2.0.Beta2
>             +-org.jboss.logging:jboss-logging:3.0.0.Beta5
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.as:jboss-as-jmx:7.0.2.Final
>         +-org.jboss.as:jboss-as-server:7.0.2.Final
>           +-org.jboss.as:jboss-as-controller:7.0.2.Final
>             +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.as:jboss-as-jmx:7.0.2.Final
>         +-org.jboss.as:jboss-as-server:7.0.2.Final
>           +-org.jboss.as:jboss-as-domain-http-api:7.0.2.Final
>             +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.as:jboss-as-jmx:7.0.2.Final
>         +-org.jboss.as:jboss-as-server:7.0.2.Final
>           +-org.jboss.as:jboss-as-deployment-repository:7.0.2.Final
>             +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.as:jboss-as-jmx:7.0.2.Final
>         +-org.jboss.as:jboss-as-server:7.0.2.Final
>           +-org.jboss.as:jboss-as-process-controller:7.0.2.Final
>             +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
>       +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
>         +-org.jboss.osgi.resolver:jbosgi-resolver-api:1.0.9
>           +-org.jboss.osgi.resolver:jbosgi-resolver-metadata:1.0.9
>             +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> , 
> IncompatibleDependencyOverwrite error for org.jboss.xnio:xnio-api:3.0.0.Beta2 paths to dependency are:
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
>         +-org.jboss.as:jboss-as-protocol:7.0.2.Final
>           +-org.jboss.remoting3:jboss-remoting:3.2.0.Beta2
>             +-org.jboss.xnio:xnio-api:3.0.0.Beta2
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
>         +-org.jboss.as:jboss-as-protocol:7.0.2.Final
>           +-org.jboss.xnio:xnio-nio:3.0.0.Beta3
>             +-org.jboss.xnio:xnio-api:3.0.0.Beta3
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.as:jboss-as-jmx:7.0.2.Final
>         +-org.jboss.as:jboss-as-server:7.0.2.Final
>           +-org.jboss.as:jboss-as-remoting:7.0.2.Final
>             +-org.jboss.xnio:xnio-api:3.0.0.Beta3
> , 
> IncompatibleDependencyOverwrite error for org.jboss.osgi.vfs:jbosgi-vfs:1.0.5 paths to dependency are:
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
>       +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
>         +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.5
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
>       +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
>         +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.6
> and
>   +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
>     +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
>       +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
>         +-org.jboss.osgi.framework:jbosgi-framework-core:1.0.0.CR8
>           +-org.jboss.osgi.vfs:jbosgi-vfs30:1.0.6
>             +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.6
> {code}
> Maybe JBoss modules makes this not as bad as it is with normal maven projects.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira