Do not provision OSGi Alliance Compendium bundle automatically
--------------------------------------------------------------
Key: PAXRUNNER-305
URL: http://issues.ops4j.org/browse/PAXRUNNER-305
Project: Pax Runner
Issue Type: Improvement
Affects Versions: 1.1.1, 1.1.0, 1.0.0, 0.20.0, 0.19.0, 0.18.0, 0.17.2,
0.17.1, 0.17.0, 0.16.0, 0.15.0, 0.14.2, 0.14.1, 0.14.0, 0.13.0, 0.12.0, 0.11.0,
0.10.0, 0.9.0, 0.8.0, 0.7.2, 0.7.1, 0.7.0, 0.6.0, 0.5.6, 0.5.5, 0.5.4, 0.5.3,
0.5.2, 0.5.1, 0.5.0
Reporter: Alin Dreghiciu
Assignee: Alin Dreghiciu
Fix For: 1.2.0
Right from the beginning Pax Runner provisioned the OSGi compendium bundle
automatically into the started framework. The problem is that it provisions a
certain version like 4.1 lately, and next it should go to 4.2 and this could
interfere with what user wants.
What I want to do is to not provision that bundle anymore and let the user
decide if he wants it or not. And if he does then he can decide the version.
So, a simple solution is to create profiles for all versions of compendium and
then user will just have to specify:
{code}
pax-run compendium // this will provision latest version available
pax-run compedium/4.1 // this will provision version 4.1
{code}
This I think is a good middle ground. Easy to use and flexible.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
