Return-Path: X-Original-To: apmail-ace-commits-archive@www.apache.org Delivered-To: apmail-ace-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 57106EAED for ; Tue, 28 May 2013 07:36:30 +0000 (UTC) Received: (qmail 26868 invoked by uid 500); 28 May 2013 07:36:29 -0000 Delivered-To: apmail-ace-commits-archive@ace.apache.org Received: (qmail 26344 invoked by uid 500); 28 May 2013 07:36:29 -0000 Mailing-List: contact commits-help@ace.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ace.apache.org Delivered-To: mailing list commits@ace.apache.org Received: (qmail 26078 invoked by uid 99); 28 May 2013 07:36:29 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 07:36:28 +0000 Date: Tue, 28 May 2013 07:36:28 +0000 (UTC) From: "Bram de Kruijff (JIRA)" To: commits@ace.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (ACE-232) Make Management Agent self contained 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/ACE-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bram de Kruijff closed ACE-232. ------------------------------- > Make Management Agent self contained > ------------------------------------ > > Key: ACE-232 > URL: https://issues.apache.org/jira/browse/ACE-232 > Project: ACE > Issue Type: Improvement > Components: Management Agent > Affects Versions: 0.8.0-incubator > Reporter: Bram de Kruijff > Fix For: 1.0.0 > > Attachments: ACE-232-selfContainedMA.patch > > > The Management Agent introduced by ACE-91 I (no longer?) self contained as it does not embed its dependencies. As a result, deploying the management agent in an OSGi container requires deploying all its dependencies as well. This will then export all kinds off packages and expose all kinds off services to the environment that may seriously complicate things. > The Launcher solves this problem by embedding all the dependencies in the launcher jar providing a controlled way of managing what is (not) exposed into the container. > My suggestion is to move the embedding to the Management Agent itself providing the same level of control, but now we can deploy the Management Agent into any OSGi container without being forced to use the launcher. > Eg. This idea triggered cause I want to be able to deploy the Management Agent into a Pax Exam 2 test -- 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