Mailing-List: contact ace-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ace-dev@incubator.apache.org
Message-ID: <175521080.1255094191849.JavaMail.jira@brutus>
Date: Fri, 9 Oct 2009 06:16:31 -0700 (PDT)
From: "Marcel Offermans (JIRA)" <jira@apache.org>
To: ace-dev@incubator.apache.org
Subject: [jira] Resolved: (ACE-32) Use Pax Runner to bootstrap ace platforms
In-Reply-To: <1985529573.1246695887162.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Marcel Offermans resolved ACE-32.
---------------------------------

    Resolution: Fixed

Last patch was applied.

> 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.