Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9688711B50 for ; Thu, 22 May 2014 08:44:06 +0000 (UTC) Received: (qmail 82899 invoked by uid 500); 22 May 2014 08:36:44 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 82807 invoked by uid 500); 22 May 2014 08:36:44 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 82799 invoked by uid 99); 22 May 2014 08:36:44 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 May 2014 08:36:44 +0000 Date: Thu, 22 May 2014 08:36:44 +0000 (UTC) From: "Steve Loughran (JIRA)" To: common-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HADOOP-8446) make hadoop-core jar OSGi friendly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)