Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <10334418.18241274733023576.JavaMail.jira@thor>
Date: Mon, 24 May 2010 16:30:23 -0400 (EDT)
From: "zoe slattery (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Assigned: (ARIES-265) Find a way to make it easy to run the
 samples outside the Aries source tree
In-Reply-To: <1118278088.462081269445047192.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

zoe slattery reassigned ARIES-265:
----------------------------------

    Assignee: Jeremy Hughes  (was: zoe slattery)

Jeremy - I think you dealt with this as part of the release - but I don't remember what the solution was. Please would you delete or let me know if I need to do anything?

> Find a way to make it easy to run the samples outside the Aries source tree
> ---------------------------------------------------------------------------
>
>                 Key: ARIES-265
>                 URL: https://issues.apache.org/jira/browse/ARIES-265
>             Project: Aries
>          Issue Type: Improvement
>            Reporter: zoe slattery
>            Assignee: Jeremy Hughes
>
> Each sample requires a platform assembly so that it can be run. The assembly usually comprises:
> (1) A minimal OSGi framework
> (2) Just the Aries components required to run the sample.
> The samples each have an assembly project that pulls this platform together in the projects' target directory and creates the configuration files needed to load the platform and aries jars.
> At release time all that the platform assembly produces is a pom, this can be executed by a user outside the Aries build tree and it will install the required jars in a target directory. Unfortunately, without the configuration files, the user still has a fair amount of 'file install'ing to do before the platform will actually run.
> The most useful thing we could supply would be a zip and/or tar file which contains the assembly pom, configuration files and legal files.
> The user can simply unzip, java -jar osgi-blah -console, to get a fully configured platform on which to run the sample.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.