Hi guys,
yes, KARAF-971 is in my TODO. It just requires an enhancement on Pax-URL
(to have a URL resolution service "transforming" an abstract version
range in a concrete URL).
I think "disabling" transitive features could address the problem.
It's really easy to do, but it's not the same as Karaf 971 IMHO.
A mix of both could address all the questions.
Regards
JB
On 01/26/2012 12:12 PM, Gert Vanthienen wrote:
Andreas,
For our ServiceMix features descriptors, we'll gladly migrate to using
version ranges but we'll need to get
https://issues.apache.org/jira/browse/KARAF-971 fixed in order for those
to work when we move from one version of Camel/CXF/... to the next one.
That should fix most of the issues Christoforos is seeing as well, I
guess.
How about adding a control flag to completely disable transitive feature
repositories? It's a bit more coarse-grained than the solution you're
suggesting, but it would allow people to completely control the list of
repository URLs being used within their own assembly or distribution
without having to go through the features descriptor and figuring out
which ones to blacklist. E.g. for ServiceMix, we already have all the
URLs listed for CXF, Camel, ActiveMQ, ... so this might even be a good
alternative to KARAF-971 for us as well.
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Thu, Jan 26, 2012 at 10:29 AM, Andreas Pieber <[email protected]
<mailto:[email protected]>> wrote:
OK, now I get it. The problem is
https://search.maven.org/remotecontent?filepath=org/apache/servicemix/apache-servicemix/4.4.0/apache-servicemix-4.4.0-features.xml
which
references features directly using the <repository> tag. Well,
currently there is no way to "blackout" some repositories, but an
additional "blackedoutFeaturesRepository" tag could be definitely of
use in such cases.
Can you please create a feature request for this in the JIRA?
Thanks and kind regards,
Andreas
On Thu, Jan 26, 2012 at 10:00, christoforos.vasilatos
<[email protected]
<mailto:[email protected]>> wrote:
No, I am definetely using karaf 2.2.5. The downloaded archive
with maven
dependency is definitely 2.2.5 There is a part of the list -t 0
command
[ 38] [Active ] [Created ] [ ] [ 30] Apache
Karaf ::
Features :: Management (2.2.5)
[ 39] [Active ] [Created ] [ ] [ 30] Apache
Karaf :: Shell
:: Log Commands (2.2.5)
[ 40] [Active ] [Created ] [ ] [ 30] Apache
Karaf :: JAAS
:: Modules (2.2.5)
[ 41] [Active ] [Created ] [ ] [ 30] Apache
Karaf :: Shell
:: ConfigAdmin Commands (2.2.4)
[ 42] [Active ] [Created ] [ ] [ 30] Apache
Karaf :: Shell
:: SSH (2.2.4)
[ 43] [Active ] [Created ] [ ] [ 30] Apache
Karaf ::
Management (2.2.4)
[ 44] [Active ] [Created ] [ ] [ 30] Apache
Karaf ::
Management :: MBeans :: System (2.2.4)
which indicates that some bundles are 2.2.5 but others are 2.2.4
while if i do not include my custon org.apache.karaf.features.cfg
configuration file all the above bundles have 2.2.5 version
This is the prefiltered configuration file:
http://karaf.922171.n3.nabble.com/file/n3689989/org.apache.karaf.features.cfg
org.apache.karaf.features.cfg
and this is the deployed configuration file after maven filter
http://karaf.922171.n3.nabble.com/file/n3689989/org.apache.karaf.features.cfg
org.apache.karaf.features.cfg
Best Regards,
Christoforos
--
View this message in context:
http://karaf.922171.n3.nabble.com/featuresRepositories-is-overriden-by-defined-feature-repositories-tp3688482p3689989.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
