You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Haug Bürger (JIRA)" <ji...@apache.org> on 2010/12/01 16:24:11 UTC
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12965714#action_12965714 ]
Haug Bürger commented on DIRMINA-806:
-------------------------------------
This hack of my pom solved the issue. Am I the only one who thinks that maven creates more issues than it solves?
...
<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>
<!-- The mina-integration-beans has a bundle dependency which does not work for me -->
<exclusions>
<exclusion>
<groupId>org.apache.mina</groupId>
<artifactId>mina-core</artifactId>
</exclusion>
</exclusions>
</dependency>
...
> 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
> Fix For: 2.0.3
>
>
> 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.
> ---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<---
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.