Hi Paul,
right now, bundle:update just update the bundle from the specified
location, or the same location (when using a SNAPSHOT for instance).
The point is how to know what's the next version ? You have myBundle
1.0, but also 1.1 and 2.0. So, to which one you want to upgrade ?
That's why you specify the new version location.
Regards
JB
On 05/05/2015 04:41 PM, Paul Spencer wrote:
Karaf v3.0.3
Can the command "bundle:update" update to the latest version of the bundle
without specifying a location?
If so, what is needed on the repository to support this functionality?
***
* Use Case
***
myBundle version 1.0 is installed and running. I have loaded version 1.1 in a
Maven repository. Currently I use the following command:
bundle:update myBundle mvn:foo.bar/myBundle/1.1
Preferred command :
bundle:update myBundle
Additional environment information:
- The myBundle version 1.0 was included in a custom build Karaf distribution.
- Cave and OBR base patching solution is not working because the bundle contains a
service requirement that orb:update considers "unsatisfied".
http://karaf.922171.n3.nabble.com/obr-deploy-fail-due-to-an-quot-Unsatisfied-requirement-quot-that-exist-when-bundle-requires-a-DataSo-td4040122.html
- The Maven repository is simply an Apache web server exposing a directory
following the Maven directories structure
(groupId/artifactId/version/artifactId-version[-classifier].type).
- The Maven repository is configured in etc/org.ops4j.pax.url.mvn.cfg with the ID
"patch_repo"
Paul Spencer
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
