You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/05/22 10:36:44 UTC

[jira] [Resolved] (HADOOP-8446) make hadoop-core jar OSGi friendly

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

Steve Loughran resolved HADOOP-8446.
------------------------------------

    Resolution: Duplicate

> make hadoop-core jar OSGi friendly
> ----------------------------------
>
>                 Key: HADOOP-8446
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8446
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>            Reporter: Freeman Fang
>
> hadoop-core isn't OSGi friendly, so for those who wanna use it in OSGi container, must wrap it with tool like bnd/maven-bundle-plugin. Apache Servicemix always wrap 3rd party jars which isn't OSGi friendly,  you can see we've done it for lots of jars here[1], more specifically for several hadoop-core versions[2].  Though we may keep this way doing it, the problem is that we need do it for every new released version for 3rd party jars, more importantly we need ensure other Apache projects communities are aware of we're doing it.
> In Servicemix we just wrap hadoop-core 1.0.3, issues to track it in Servicemix is[3].
> We hope Apache Hadoop can offer OSGi friendly jars, in most cases, it's should be straightforward, as it just need add OSGi metadata headers to MANIFEST.MF, this could be done easily with maven-bundle-plugin if build with maven.  There's also some other practice should be followed like different modules shouldn't share same package(avoid split pacakge). 
> thanks
> [1]http://repo2.maven.org/maven2/org/apache/servicemix/bundles
> [2]http://repo2.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.hadoop-core/
> [3]https://issues.apache.org/jira/browse/SMX4-1147



--
This message was sent by Atlassian JIRA
(v6.2#6252)