You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Jonathan Valliere (JIRA)" <ji...@apache.org> on 2019/05/24 13:53:00 UTC

[jira] [Resolved] (DIRMINA-806) Maven dependencies for mina-integration-* for non-OSGi-users

     [ https://issues.apache.org/jira/browse/DIRMINA-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Valliere resolved DIRMINA-806.
---------------------------------------
    Resolution: Abandoned

> Maven dependencies for mina-integration-* for non-OSGi-users
> ------------------------------------------------------------
>
>                 Key: DIRMINA-806
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-806
>             Project: MINA
>          Issue Type: Bug
>          Components: Integration
>    Affects Versions: 2.0.0
>            Reporter: Thomas Vandahl
>            Priority: Major
>             Fix For: 2.0.14
>
>
> I'm trying to follow the JMX-integration example in the users guide. When I add mina-integration-jmx as a dependency, I get unresolved dependencies such as mina-core-2.0.1.bundle.
> 1. There are no such bundles in the central maven repository.
> 2. If I define the dependencies explicitly and exclude the bundles like follows, everything works ok.
> {code}
> ---8<---
>         <dependency>
>             <groupId>org.apache.mina</groupId>
>             <artifactId>mina-core</artifactId>
>             <version>2.0.1</version>
>         </dependency>
>         <dependency>
>             <groupId>org.apache.mina</groupId>
>             <artifactId>mina-integration-beans</artifactId>
>             <version>2.0.1</version>
>             <exclusions>
>                 <exclusion>
>                     <groupId>org.apache.mina</groupId>
>                     <artifactId>mina-core</artifactId>
>                 </exclusion>
>             </exclusions>
>         </dependency>
>         <dependency>
>             <groupId>org.apache.mina</groupId>
>             <artifactId>mina-integration-ognl</artifactId>
>             <version>2.0.1</version>
>             <exclusions>
>                 <exclusion>
>                     <groupId>org.apache.mina</groupId>
>                     <artifactId>mina-core</artifactId>
>                 </exclusion>
>                 <exclusion>
>                     <groupId>org.apache.mina</groupId>
>                     <artifactId>mina-integration-beans</artifactId>
>                 </exclusion>
>             </exclusions>
>         </dependency>
>         <dependency>
>             <groupId>org.apache.mina</groupId>
>             <artifactId>mina-integration-jmx</artifactId>
>             <version>2.0.1</version>
>             <exclusions>
>                 <exclusion>
>                     <groupId>org.apache.mina</groupId>
>                     <artifactId>mina-core</artifactId>
>                 </exclusion>
>                 <exclusion>
>                     <groupId>org.apache.mina</groupId>
>                     <artifactId>mina-integration-beans</artifactId>
>                 </exclusion>
>                 <exclusion>
>                     <groupId>org.apache.mina</groupId>
>                     <artifactId>mina-integration-ognl</artifactId>
>                 </exclusion>
>             </exclusions>
>         </dependency>
> ---8<---
> {code}
> Is this behavior intentional? If so, how do I use these dependencies in an non-OSGi environment and where do I get them from?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)