You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by "Toni Menzel (JIRA)" <ji...@apache.org> on 2009/07/04 10:24:47 UTC
[jira] Created: (ACE-32) Use Pax Runner to bootstrap ace platforms
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
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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: ace32-1.patch
Patch adds two new things to the "ant package" phase for dev-server.
I just went for one particuar target to let you cross check which direction we go and what to expect.
1. core/deploy/target/dev-server/paxrunner/
A folder with just a script that calls the original pax runner at runtime.
just call "./run.sh" on the folder stated above.
2. core/deploy/target/dev-server/standalone
this calls pax runner at build-time (inside ant) and let it construct a particuar platform output.
The final folder contains routly (or should at least) an output that very much looks like the current target output.
So, you also can call "run.sh" here. Look inside to see that there is no pax runner involved anymore.
Benefit when compared to the current approach: framework independence
Where is the configuration ?
No real user configuration is done in the build scripts.
All configurations are read from core/conf/<target>/
For Pax Runner we have two configurations there:
--> platform.setup
There you specify the normal pax runner options. This includes the selection of the framework (felix,equinox,knopflerfish,concierge)
and its versions.
--> platform.properties
additional properties that are needed to be configured as "environment" properties (-D)
like http.port and others.
> 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
> Attachments: ace32-1.patch, pax-runner-1.1.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.
[jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace
platforms
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731445#action_12731445 ]
Marcel Offermans commented on ACE-32:
-------------------------------------
Seems to be working just fine, all bundles start without problems both on Equinox and Felix. Great work Toni! The next step is to apply a similar patch to the other targets we use. My suggestion there would be to upgrade the targets we actively use instead of all of them (perhaps throwing away unused ones finally).
> 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: ace32-2.patch, pax-runner-1.1.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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: (was: ACE-32-October2009.patch)
> 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-October2009.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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: ACE-32-October2009.patch
> 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-October2009.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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: (was: ACE-32-October2009.patch)
> 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: Angelo van der Sijpt
> 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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: (was: ACE-32-2009-10-06.patch)
> 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: Angelo van der Sijpt
> Attachments: 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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: pax-runner-1.2.1.jar
> 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-October2009.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.
[jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace
platforms
Posted by "Angelo van der Sijpt (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace
platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762405#action_12762405 ]
Toni Menzel commented on ACE-32:
--------------------------------
Attached a patch that provides pax runner development and "production" targets for dev-gateway, dev-server-filebasesd, dev-server-webui.
This can (and should) fully replace all target-*.xml files on core.
Features:
1. Flexible Development Targets
with "ant package" you will get pax runner based configuration scripts for the afromentioned targets in the usual deploy/target/ folders.
(runDev.sh, runDev.bat)
2. Standalone Outputs (just as before, but flexible as paxrunner generates many things)
with "ant zip" a pax runner instance will pre-load all requirements and config files and zip them up at the usual release folder.
3. Single Point of Entry
All target relevant configuration now sits in conf/{target}/platform.properties (just parameters) and platform.setup (all bundles required as well as pax runner options).
Target Framework and Version "can" be set in platform.properties but is super-configured by settings made in "packageDevelopment" and "packageProduction" targets in build.xml.
(currently it is Felix 2.0.0)
> 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-October2009.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.
[jira] Assigned: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Angelo van der Sijpt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Angelo van der Sijpt reassigned ACE-32:
---------------------------------------
Assignee: Angelo van der Sijpt (was: Marcel Offermans)
> 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: Angelo van der Sijpt
> Attachments: ACE-32-October2009.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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: (was: ACE-32-3.patch)
> 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-October2009.patch
>
>
> 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.
[jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace
platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749561#action_12749561 ]
Toni Menzel commented on ACE-32:
--------------------------------
Agree with all but would like to annotate that "add new targets .. [by].. just point out the bundles that should be included":
This is usually dead simple, but components in ace rely on configuration supplied by files (currently), so it always involves adding certain configuration files.
But sure, adding a new target should be simple, and this is what i will concentrate on for next patch proposal.
So, concrete targets to be created are not so relevant, just the "how we can create and mantain" is important.
Thanks angelo for the input. Patch will be supplied when something is there to show ;)
> 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-3.patch, ace32-2.patch, pax-runner-1.1.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.
[jira] Resolved: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace
platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727207#action_12727207 ]
Toni Menzel commented on ACE-32:
--------------------------------
Just decided that the "deployments" should be Pax Runner Profiles.
This way, a profile can be started with
"./pax-run --profiles=org.apache.ace.server" for latest felix (1.8.1).
Once the ACE artifacts are deployed "somewhere" on a maven repository, we can also put the profiles into the official ops4j repository so pax runner can start the ace setups out of the box (no local ace sources/builds necessary)
> 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
>
> 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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: (was: ace32-2.patch)
> 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-October2009.patch
>
>
> 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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: ACE-32-2009-10-06.patch
fixed a small issue not removing an unncecceary file from production zip. (pax meta data)
> 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: Angelo van der Sijpt
> 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.
[jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace
platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727840#action_12727840 ]
Toni Menzel commented on ACE-32:
--------------------------------
With this patch, we can switch frameworks by changing core/config/dev-server/platform.setup
What i could think of as well is an automatic "all supported frameworks and versions" generation.
So, instead of just creating one "core/deploy/target/dev-server/standalone"
we could generate easily this:
core/deploy/target/dev-server/standaline_felix_1_8_1
core/deploy/target/dev-server/standaline_felix_1_8_0
core/deploy/target/dev-server/standaline_felix_1_6_0
core/deploy/target/dev-server/standaline_equinox_3_5_0
core/deploy/target/dev-server/standaline_equinox_3_4_2
..
but maybe this is more confusing that practical. Just wanted to show the option..
> 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
> Attachments: ace32-1.patch, pax-runner-1.1.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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: ACE-32-October2009.patch
> 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-October2009.patch
>
>
> 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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: pax-runner-1.1.1.jar
Pax Runner Release 1.1.1
Used in build scripts and for running targets.
> 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
> Attachments: pax-runner-1.1.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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: (was: pax-runner-1.1.1.jar)
> 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-October2009.patch
>
>
> 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.
[jira] Assigned: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans reassigned ACE-32:
-----------------------------------
Assignee: Marcel Offermans (was: Angelo van der Sijpt)
> 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.
[jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace
platforms
Posted by "Angelo van der Sijpt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749552#action_12749552 ]
Angelo van der Sijpt commented on ACE-32:
-----------------------------------------
It would be nice to have two versions of each target: one 'release' version which is as stand-alone as possible, featuring the Felix version of our choice, and a 'dev' version based on Pax Runner, so we can do some tweaking at run time. Furthermore, we might want to add some additional bundles to the dev version.
There are a lot of combinations we could dream up (see http://cwiki.apache.org/confluence/display/ACE/Overview+of+ACE+components for some inspiration), but to support the demo material on the wiki at the moment, we will need,
- server with deployment
- server with deployment and obr
- target with deployment
Note that this way, we don't have any demo's of the logging system, nor of the relaying capacities. It would be good if we can make it really easy to add new targets (as in, just point out the bundles that should be included).
> 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-3.patch, ace32-2.patch, pax-runner-1.1.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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: ace32-2.patch
fixed wrong folder name.
> 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
> Attachments: ace32-2.patch, pax-runner-1.1.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.
[jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace
platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764016#action_12764016 ]
Toni Menzel commented on ACE-32:
--------------------------------
thanks for applying!
I think now is also a good time to get rid of (now unused) checked in libraries like felix. Having them still in leads to the assumption that thats being used (which it is - at least shoud - not).
wdyt ?
> 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.
[jira] Assigned: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans reassigned ACE-32:
-----------------------------------
Assignee: Marcel Offermans
> 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: ace32-2.patch, pax-runner-1.1.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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: ACE-32-3.patch
Patch that provides paxrunner deployments for the following targets:
- dev-server-filebased
- dev-server-webui
- dev-gateway
Configuration is (as before) in core/conf/dev-X/platform.setup and platform.config.
Definition is made in main build.xml now (no more wrestling in dev-*.xmls).
Because there are now more targets affected, built takes a bit longer (pax runner runs multiple times).
Because of this, all of ths has been moved out of the package target and into the new cummulative "package2".
So, package is old and package2 is new. Just with package2 you get the standalone and paxrunner deployments for the afromentioned targets.
> 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-3.patch, ace32-2.patch, pax-runner-1.1.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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: (was: ace32-1.patch)
> 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
> Attachments: ace32-2.patch, pax-runner-1.1.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.
[jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-32:
---------------------------
Attachment: ACE-32-2009-10-06.patch
> 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: Angelo van der Sijpt
> 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.
[jira] Issue Comment Edited: (ACE-32) Use Pax Runner to bootstrap
ace platforms
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727840#action_12727840 ]
Toni Menzel edited comment on ACE-32 at 7/6/09 5:04 PM:
--------------------------------------------------------
With this patch, we can switch frameworks by changing core/config/dev-server/platform.setup
What i could think of as well is an automatic "all supported frameworks and versions" generation.
So, instead of just creating one "core/deploy/target/dev-server/standalone"
we could generate easily this:
core/deploy/target/dev-server/standalone_felix_1_8_1
core/deploy/target/dev-server/standalone_felix_1_8_0
core/deploy/target/dev-server/standalone_felix_1_6_0
core/deploy/target/dev-server/standalone_equinox_3_5_0
core/deploy/target/dev-server/standalone_equinox_3_4_2
..
but maybe this is more confusing that practical. Just wanted to show the option..
was (Author: tonit):
With this patch, we can switch frameworks by changing core/config/dev-server/platform.setup
What i could think of as well is an automatic "all supported frameworks and versions" generation.
So, instead of just creating one "core/deploy/target/dev-server/standalone"
we could generate easily this:
core/deploy/target/dev-server/standaline_felix_1_8_1
core/deploy/target/dev-server/standaline_felix_1_8_0
core/deploy/target/dev-server/standaline_felix_1_6_0
core/deploy/target/dev-server/standaline_equinox_3_5_0
core/deploy/target/dev-server/standaline_equinox_3_4_2
..
but maybe this is more confusing that practical. Just wanted to show the option..
> 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
> Attachments: ace32-1.patch, pax-runner-1.1.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.