[
https://issues.apache.org/jira/browse/ARIES-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Hughes resolved ARIES-265.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.1
Each sample contains an assembly module. Users can get the pom.xml for that,
run maven to get the assembly and everything needed will be in the target dir.
> 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
> Fix For: 0.1
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
