[
http://issues.ops4j.org/browse/PAXRUNNER-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974#action_12974
]
mcculls commented on PAXRUNNER-305:
-----------------------------------
Just to clarify: it's not a fixed list... pax-construct picks up whatever
repos/mirrors you have configured in your maven project and passes them onto
pax-runner.
At the time this was the only way to pass Maven specific information (such as
repo settings) onto pax-runner, and setting the list of repos also gave Maven
control over what lookups were made (handy if using Nexus) - unfortunately when
the profiles were externalized their update location was just another entry on
the list of internal repos which then got overwritten when we set the explicit
list of Maven repos. Thankfully there are a couple of potential solutions*,
and the workaround is the ongoing sync to Maven central.
* the simplest is to merge the Maven and internal repo lists, but this could
might lead to more lookups than is strictly necessary if you're using a repo
manager.
Anyway as Alin said, this will be fixed one way or another.
> 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: 0.5.0, 0.5.1, 0.5.2, 0.5.3, 0.5.4, 0.5.5, 0.5.6, 0.6.0,
> 0.7.0, 0.7.1, 0.7.2, 0.8.0, 0.9.0, 0.10.0, 0.11.0, 0.12.0, 0.13.0, 0.14.0,
> 0.14.1, 0.14.2, 0.15.0, 0.16.0, 0.17.0, 0.17.1, 0.17.2, 0.18.0, 0.19.0,
> 0.20.0, 1.0.0, 1.1.0, 1.1.1
> 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
