aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bartosz Kowalewski (JIRA)" <>
Subject [jira] Commented: (ARIES-265) Find a way to make it easy to run the samples outside the Aries source tree
Date Tue, 13 Jul 2010 20:28:49 GMT


Bartosz Kowalewski commented on ARIES-265:

Hi Zoe,

Have you thought of using Pax Runner directly or Pax Runner wrapped into maven-pax-plugin:provision?
Both of these are alternatives for the current approach. While I haven't done a thorough comparison,
I think that especially maven-pax-plugin:provision might be useful. All configuration can
be contained inside pom.xml - Maven dependencies (bundles) + a simplistic config for maven-pax-plugin.
This should also allow the user to change the container to Felix (or ...) by modifying a single
The 'load' directory for eba would still be avaialable, so the environment should look exactly
ilke the one that is now started by the assembly project.

This would require changing: 
java -jar osgi-blah -console
mvn org.ops4j:maven-pax-plugin:provision

Best regards,

> Find a way to make it easy to run the samples outside the Aries source tree
> ---------------------------------------------------------------------------
>                 Key: ARIES-265
>                 URL:
>             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
> (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
> 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.

View raw message