Hi,
It looks like a bug, maybe related to default configuration in
etc/org.ops4j.pax.url.mvn.cfg and resolver.
Let me try to reproduce with a simple test case, and eventually create a
Jira.
By the way, I think it's better to post this kind of question on the
user mailing list.
Regards
JB
On 01/12/2016 04:41 PM, drdwo wrote:
Regarding karaf 4 feature caching, what is the intended behavior?
I would expect for releases, that a changed feature will be installed in
case of a version change.
But for snapshots I would expect, that a changed feature will be installed
even in case
the snapshot version didn't change.
Seems this isn't the case, is this a bug or a feature of karaf?
Did the following:
create SimpleRoute-feature, version = 5.0.0.SNAPSHOT
publish SimpleRoute-feature to Nexus
feature:install SimpleRoute-feature
feature:uninstall SimpleRoute-feature
change SimpleRoute-feature (no version change)
publish SimpleRoute-feature to Nexus
feature:repo-refresh
feature:install SimpleRoute-feature
expected: changed feature deployed, but it is still the old one.
--
View this message in context:
http://karaf.922171.n3.nabble.com/karaf-4-feature-caching-for-SNAPSHOT-versions-tp4044790.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
