Re: Confused about feature dependency="true"

Ready: https://issues.apache.org/jira/browse/KARAF-5542 I've replicated that behaviour with the following feature set: https://github.com/llech/karaf-refresh-demo/tree/master -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

Re: Confused about feature dependency="true"

Please raise a JIRA, explain which bundle is updated when you think it should not, and attach the full log, I'll try to have a quick look. 2017-12-13 15:51 GMT+01:00 lechlukasz : > So it doesn't look like my case. The update happens when the subsequent > features are

Re: Confused about feature dependency="true"

So it doesn't look like my case. The update happens when the subsequent features are batch-updated, there is no change of snapshot in the meantime. If it can be disabled, how? How is that mechanism called and which part of code is responsible for that? I'd like to take look on java sources to

Re: Confused about feature dependency="true"

There's a checksum verification, so if the snapshot has changed, it will be updated whenever the FeaturesService resolver kicks in. In short, if the snapshot has been rebuilt, it will be updated (not only refreshed). This can be disabled though. 2017-12-11 19:49 GMT+01:00 Seth Leger

Re: Confused about feature dependency="true"

On 12/8/17 10:47 AM, lechlukasz wrote: > I'm able to do a 'fake' release to our local maven repository. I didn't > thought there's some logic in feature refreshing bound to that. Thanks for > explaining. Is this true? Does Karaf (or something inside Karaf) assume that SNAPSHOT versions should

Re: Confused about feature dependency="true"

OK so the code would not refresh if aries-jpa was not a snapshot? Quite unfortunately, there is a HUGE (for us) bug in aries-jpa is fixed in 2.7.0 version, which is not released... I'm able to do a 'fake' release to our local maven repository. I didn't thought there's some logic in feature

Re: Confused about feature dependency="true"

So your bundle is refreshed because it's wired to the glassfish jersey-container-servlet-core bundle, which itself is wired to javax.persistence bundle, refreshed because: Should be wired to: org.apache.aries.jpa.container/2.7.0.SNAPSHOT (through [javax.persistence/2.1.1.v201509150925]

Re: Confused about feature dependency="true"

Bundles to install: here are only my private bundles listed Bundles to refresh: com.eclipsesource.jaxrs.jaxrs-publisher/5.3.1 (Wired to org.glassfish.jersey.containers.jersey-container-servlet-core/2.22.2 which is being refreshed) javax.persistence/2.1.1.v201509150925 (Should be wired

Re: Confused about feature dependency="true"

You should have a line saying why javax.persistence/2.1.1.v201509150925 is being refreshed. Can you paste the whole output ? Guillaume 2017-12-08 13:53 GMT+01:00 lechlukasz : > I think I've found the offender. > > The message says: > >

Re: Confused about feature dependency="true"

I think I've found the offender. The message says: org.glassfish.jersey.containers.jersey-container-servlet-core/2.22.2 (Wired to javax.persistence/2.1.1.v201509150925 which is being refreshed) However, there's no indicator why it should be refreshed. The exact bundle is already installed in

Re: Confused about feature dependency="true"

2017-12-08 12:15 GMT+01:00 lechlukasz : > Ok thank you, all my features are verified by maven plugin. > > So you say that no matter if I have features with dependency="true" or not, > if the feature is already installed, it will not be touched? > So the observed behavior,

Re: Confused about feature dependency="true"

Ok thank you, all my features are verified by maven plugin. So you say that no matter if I have features with dependency="true" or not, if the feature is already installed, it will not be touched? So the observed behavior, that after installing new feature the blueprint context from bundles from

Re: Confused about feature dependency="true"

It's all about constraints. If something does not work when installed, it means that the constraints are not correctly expressed. If you use the maven bundle plugin for example, it should generate service requirements for the various namespace handlers used. Those will be used at resolution time,

Re: Confused about feature dependency="true"

Does the same appply to features? Because I've noticed an improvement, after marking the dependent features as dependency="true": service1-core However, if I've done the same for all my features, including system ones (jpa, transaction-api, transaction etc.) I've ended up with my bundles

Re: Confused about feature dependency="true"

So first, bundles are only updated / refreshed / restarted if necessary. If there's no change for a given bundle, it won't be touched at all. The dependency="true" flag means that the artifact can be used by karaf to solve some constraints, but it won't be installed if not needed. This is mainly

Confused about feature dependency="true"

Hello, I'm quite confused about feature dependencies. The documentation about provisioning doesn't explain much how the dependency="true" is expected to work. I've tried adding or removing it, but I experience unexpected behavior... I have a core feature and other features that depend on it.