[jira] [Commented] (DIRMINA-919) Maven packaging is broken

["Julien Vermillard (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DIRMINA-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717508#comment-13717508 ] 

Julien Vermillard commented on DIRMINA-919:
-------------------------------------------

i'm agreeing here with Jeff, it's silly to force our user to load the maven-plugin-bundle when they want to gather simple jar for non OSGi coding.

Perhaps we should package 'jar' but with BND generated manifest for OSGi users ?
See : http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html 
"Adding OSGi metadata to existing projects without changing the packaging type"
                
> 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