[
https://issues.apache.org/jira/browse/DIRMINA-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503688#comment-13503688
]
Pierre-Arnaud Marcelot commented on DIRMINA-919:
------------------------------------------------
Hi Jeff,
Did you add the following to your main pom?
=========================================
<build>
<plugins>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<extensions>true</extensions>
</configuration>
</plugin>
</plugins>
</build>
=========================================
It is mandatory for 'bundle' type artifacts to be resolved correctly ('bundle'
not being a standard Maven type).
Hope this helps.
> Maven packaging is broken
> -------------------------
>
> Key: DIRMINA-919
> URL: https://issues.apache.org/jira/browse/DIRMINA-919
> Project: MINA
> Issue Type: Improvement
> Affects Versions: 2.0.7
> Reporter: Jeff MAURY
> Labels: Maven, packaging
> Fix For: 2.0.8, 3.0.0-trunk
>
>
> Maven packaging is broken on several parts: core has bundle packaging where a
> jar is deployed to Central so having a core dependency with Maven needs to
> have<type>jar</type> in the dependency otherwise build fails.
> Can be ok but more problems arise if you use mina-http:
> 1) it embeds classes from core in its jar file but not the source jar so it
> is problematic to use in an IDE
> 2) mina-http has a dependency on mina-core but as it does not specify
> <type>jar</type> dependency resolution fails and you need to play with
> exclusions
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
