bundle:update myBundle mvn:groupId/artifactId/1.1
It will look for the artifact in:
1/ system repo
2/ user repo
3/ all repos defined in etc/org.ops4j.pax.url.mvn.cfg
Regards
JB
On 05/05/2015 06:01 PM, Paul Spencer wrote:
JB,
If OBR worked, I would use the command "orb:deploy myBundl
JB,
If OBR worked, I would use the command "orb:deploy myBundle,1.1". Is there an
equivalent with bundle:update what would search all Maven repositories define
in etc/org.ops4j.pax.url.mvn.cfg?
Paul Spencer
> On May 5, 2015, at 10:45 AM, Jean-Baptiste Onofré wrote:
>
>
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&
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 versio
I'm not sure how that would help with the refresh issue, or am I missing
something? :)
On Apr 5, 2015 10:23 AM, "Charlie Mordant" wrote:
> Hi,
> You can reference your services with service listeners (bind and unbind)
> to overcome this issue. Doing this, you won't encounter that issue
>
> Regar
Hi,
You can reference your services with service listeners (bind and unbind) to
overcome this issue. Doing this, you won't encounter that issue
Regards,
2015-04-05 0:33 GMT+02:00 Ryan Moquin :
> Out of curiosity, sometimes if I do a global refresh with Karaf 3.0.3, it
> will appear to reload eve
Out of curiosity, sometimes if I do a global refresh with Karaf 3.0.3, it
will appear to reload everything, even the ssh bundle. When that happens
sometime the Karaf features bundle will fail to refresh which causes other
Karaf bundles to be shutdown. I'm not sure what causes this (it seems like
Global refresh could be a good advice to re-wire the packages.
On 02/26/2015 11:05 PM, asookazian2 wrote:
ok what about refresh, restart, resolve after update? are those
recommended/required?
--
View this message in context:
http://karaf.922171.n3.nabble.com/bundle-update-tp4038534p4038716.
This solely depends on your use-case. If you have bundles that import other
bundles and don't depend on services make sure your dependent bundles do
get a refresh.
Just a simple example. If you have camel routes in your bundles, you need
to do a bundle:refresh [camel-core-bundle-id] so that the cam
ok what about refresh, restart, resolve after update? are those
recommended/required?
--
View this message in context:
http://karaf.922171.n3.nabble.com/bundle-update-tp4038534p4038716.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Package-Imports only, services are usually stopped and started again.
regards, Achim
2015-02-13 20:15 GMT+01:00 asookazian2 :
> Hi with karaf 3.0.2.
>
> assume we have bundleA (a REST API) which uses bundleB (a DAO API). I have
> new versions of these bundles from a maven build. I b
Hi with karaf 3.0.2.
assume we have bundleA (a REST API) which uses bundleB (a DAO API). I have
new versions of these bundles from a maven build. I bundle:update B then
bundle:update A. Cmd is update file:/path/to/bundle.
Do I need to also subsequently issue bundle:refresh and/or
12 matches
Mail list logo
