ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Angelo van der Sijpt (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace platforms
Date Sat, 10 Oct 2009 15:20:31 GMT

    [ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764355#action_12764355
] 

Angelo van der Sijpt commented on ACE-32:
-----------------------------------------

Well, we still have a dependency on the felix shell bundle, but I see no reason why we couldn't
move that to an ext directory.

Would it perhaps be possible to let pax runner take care of other libraries, like e.g. the
event admin? If possible, I would like to have those 'fixed' to some version, and not always
just use the newest one.

> Use Pax Runner to bootstrap ace platforms
> -----------------------------------------
>
>                 Key: ACE-32
>                 URL: https://issues.apache.org/jira/browse/ACE-32
>             Project: Ace
>          Issue Type: New Feature
>            Reporter: Toni Menzel
>            Assignee: Marcel Offermans
>         Attachments: ACE-32-2009-10-06.patch, pax-runner-1.2.1.jar
>
>
> Currently, the codebase+ant scripts create a fixed set of felix "deployments". Because
Pax Runner:
> - eliminiates the need to create bulky config files (for felix)
> - enables the use of many more (new+old) felix versions and frameworks (equinox+knopflerfish)
> i think it is a good thing to at least offer.
> Contribution will probably include a changed build.xml that adds tasks to create an "pax
runner starter" folder.
> This includes predifined paxrunner.args files that should be functionally identical to
the current deployment-folders.

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


Mime
View raw message