Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 32BD0107CB for ; Fri, 21 Mar 2014 01:46:46 +0000 (UTC) Received: (qmail 24831 invoked by uid 500); 21 Mar 2014 01:46:44 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 24694 invoked by uid 500); 21 Mar 2014 01:46:43 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 24679 invoked by uid 99); 21 Mar 2014 01:46:43 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Mar 2014 01:46:43 +0000 Date: Fri, 21 Mar 2014 01:46:43 +0000 (UTC) From: "Corey J. Nolet (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-2518) Make accumulo-core 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/ACCUMULO-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Corey J. Nolet updated ACCUMULO-2518: ------------------------------------- Description: Many Apache projects (and other projects) are beginning to make packages that play nice with OSGi containers. The OSGi compendium http://www.osgi.org/Specifications/HomePage defines some constraints on how bundles should be packaged. For instance, service loading is not allowed in OSGi and packages shouldn't be split over different jars/bundles. It would be extremely useful if we could provide a ready-to-go bundle with solid documentation on how to deploy it. Another notable feature would be to build a karaf-friendly features file where a user could more easily load in the required dependencies. Integrating the "accumulo" commands into the karaf client shell would be another good possiblity. was: Many Apache projects (and other projects) are beginning to do make packages that play nice with OSGi containers. The OSGi compendium http://www.osgi.org/Specifications/HomePage defines some constraints on how bundles should be packaged. For instance, service loading is not allowed in OSGi and packages shouldn't be split over different jars/bundles. It would be extremely useful if we could provide a ready-to-go bundle with solid documentation on how to deploy it. Another notable feature would be to build a karaf-friendly features file where a user could more easily load in the required dependencies. Integrating the "accumulo" commands into the karaf client shell would be another good possiblity. > Make accumulo-core OSGi friendly > -------------------------------- > > Key: ACCUMULO-2518 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2518 > Project: Accumulo > Issue Type: New Feature > Components: client > Reporter: Corey J. Nolet > Priority: Minor > Labels: proposal > Fix For: 1.7.0 > > > Many Apache projects (and other projects) are beginning to make packages that play nice with OSGi containers. The OSGi compendium http://www.osgi.org/Specifications/HomePage defines some constraints on how bundles should be packaged. For instance, service loading is not allowed in OSGi and packages shouldn't be split over different jars/bundles. It would be extremely useful if we could provide a ready-to-go bundle with solid documentation on how to deploy it. > Another notable feature would be to build a karaf-friendly features file where a user could more easily load in the required dependencies. Integrating the "accumulo" commands into the karaf client shell would be another good possiblity. -- This message was sent by Atlassian JIRA (v6.2#6252)