The requirement is that the bundle uses a maven snapshot url.
If that's the case, the bundle:watch command will look for updates in the
local repository.
The only command I'm using for the bundle:watch is "bundle:watch *" which
updates all maven snapshots whenever I rebuild something.
se Bundles are used from the system folder.
>>
>> regards, Achim
>>
>>
>> 2017-04-04 10:41 GMT+02:00 Cristiano Costantini <
>> cristiano.costant...@gmail.com>:
>>
>> Hello all,
>>
>> I am trying to use for the first time the bundle:wat
rds, Achim
>
>
> 2017-04-04 10:41 GMT+02:00 Cristiano Costantini <
> cristiano.costant...@gmail.com>:
>
> Hello all,
>
> I am trying to use for the first time the bundle:watch command,
> however I cannot get it to work correctly...
>
> I watch a bundle with b
m trying to use for the first time the bundle:watch command,
> however I cannot get it to work correctly...
>
> I watch a bundle with bundle:watch ID, I also start explicitly watching
> with bundle:watch --start, the bundle is correctly listed when I execute
> bundle:watch --list ,
Hello all,
I am trying to use for the first time the bundle:watch command,
however I cannot get it to work correctly...
I watch a bundle with bundle:watch ID, I also start explicitly watching
with bundle:watch --start, the bundle is correctly listed when I execute
bundle:watch --list , but when
ra about that ?
>
> Thanks
> Regards
> JB
>
> On 01/15/2017 02:50 PM, Erwin Hogeweg wrote:
>> Hi,
>>
>> I noticed that bundle:watch kept restarting the same bundles
>> over-and-over again. After some digging I believe this behavior is
>> caused b
Hi Erwin,
it looks you found a bug. Do you mind to create a Jira about that ?
Thanks
Regards
JB
On 01/15/2017 02:50 PM, Erwin Hogeweg wrote:
Hi,
I noticed that bundle:watch kept restarting the same bundles
over-and-over again. After some digging I believe this behavior is
caused
Hi,
I noticed that bundle:watch kept restarting the same bundles over-and-over
again. After some digging I believe this behavior is caused by
BundleWatchImpl:163
if (location != null && location.exists() && location.lastModified() >
bun
11-23 10:59:52,294 | DEBUG | Thread-72|
BundleWatcherImpl| 23 - org.apache.karaf.bundle.core -
4.0.7 | Bundle watcher thread started
Regards,
Erwin
Regards
JB
On 11/23/2016 12:13 AM, Erwin Hogeweg wrote:
Hi,
Is there a reason why bundle:watch won’t work in the following scenario?
- Instal
| Thread-72|
> BundleWatcherImpl| 23 - org.apache.karaf.bundle.core - 4.0.7
> | Bundle watcher thread started
>
>
> Regards,
>
> Erwin
>
>
>>
>> Regards
>> JB
>>
>> On 11/23/2016 12:13 AM, Erwin Hogeweg wrote:
>
11/23/2016 12:13 AM, Erwin Hogeweg wrote:
>> Hi,
>>
>> Is there a reason why bundle:watch won’t work in the following scenario?
>>
>> - Install and start SNAPSHOT bundle from maven.
>> - execute bundle:'watch —start '
>> - rebuild bundle with ‘clean install’
>>
>>
JB,
> Hmmm, and I guess that it contains SNAPSHOT in the version, right ?
Correct.
bundle:watch *
Watched URLs/IDs:
*
karaf@root>bundle:watch --start
Starting watch
Watched URLs/IDs:
*
karaf@root>la
START LEVEL 100 , List Threshold: 0
ID | State| Lvl | Version
Christian,
> Do you have any issues when just using bundle:watch *
Yes, same issue.
Erwin
>
> Christian
>
> On 23.11.2016 00:13, Erwin Hogeweg wrote:
>> Hi,
>>
>> Is there a reason why bundle:watch won’t work in the following scenario?
>>
>> -
just works with SNAPSHOT updated in your local .m2/repository.
That's where it is.
Erwin
Regards
JB
On 11/23/2016 12:13 AM, Erwin Hogeweg wrote:
Hi,
Is there a reason why bundle:watch won’t work in the following scenario?
- Install and start SNAPSHOT bundle from maven.
- execute bundle
Never tried this style.
Do you have any issues when just using bundle:watch *
Christian
On 23.11.2016 00:13, Erwin Hogeweg wrote:
Hi,
Is there a reason why bundle:watch won’t work in the following scenario?
- Install and start SNAPSHOT bundle from maven.
- execute bundle:'watch —start
.
That's where it is.
Erwin
Regards
JB
On 11/23/2016 12:13 AM, Erwin Hogeweg wrote:
Hi,
Is there a reason why bundle:watch won’t work in the following scenario?
- Install and start SNAPSHOT bundle from maven.
- execute bundle:'watch —start '
- rebuild bundle with ‘clean install’
Expect
JB,
> I guess your SNAPSHOT is on a remote repo.
Nope, local.
> For now, watch just works with SNAPSHOT updated in your local .m2/repository.
That's where it is.
Erwin
>
> Regards
> JB
>
>> On 11/23/2016 12:13 AM, Erwin Hogeweg wrote:
>> Hi,
>>
&
Hi,
Is there a reason why bundle:watch won’t work in the following scenario?
- Install and start SNAPSHOT bundle from maven.
- execute bundle:'watch —start '
- rebuild bundle with ‘clean install’
Expect bundle to be updated, but nothing happens… (Executing 'update '
does load the new version
So it is looking in the local .m2/repository path or elsewhere? If the
former, then I suppose this should be sufficient as the built JAR will be
uploaded to .m2/repository/path/to/bundle.jar.
jbonofre wrote
> Hi,
>
> bundle:watch works only for mvn URL containing SNAPSHOT b
I am currently using the following cmd to update an existing bundle:
update 384 file:/path/to/bundleFoo.jar
refresh 384
According to this doc:
https://karaf.apache.org/manual/latest/commands/bundle-watch.html
The param for the bundle:watch cmd is URLs (bundle IDs or URLs)
I'd like to have
Hi,
bundle:watch works only for mvn URL containing SNAPSHOT by default.
Regards
JB
On 11/20/2015 06:32 AM, asookazian2 wrote:
I am currently using the following cmd to update an existing bundle:
update 384 file:/path/to/bundleFoo.jar
refresh 384
According to this doc:
https
By the way, you can specify the URL patterns to watch in the
bundle:watch command (see command options).
Regards
JB
On 11/20/2015 06:32 AM, asookazian2 wrote:
I am currently using the following cmd to update an existing bundle:
update 384 file:/path/to/bundleFoo.jar
refresh 384
According
Thank you Marco. But that is not the case. The sift logger is not activated
in org.ops4j.pax.logging.cfg:
--
View this message in context:
http://karaf.922171.n3.nabble.com/bundle-watch-with-Karaf-3-0-4-tp4042175p4042185.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Hello,
In Karaf 2.x each automatic bundle update via dev:watch was logged to the
karaf shell. Now with Karaf 3.0.4 no successful update is logged to the
shell anymore. Is it possible to configure the bundle:watch so the behaviour
is as dev:watch was? Of course I can see the logging
to configure the bundle:watch so the behaviour
is as dev:watch was? Of course I can see the logging in
org.apache.karaf.bundle.core.log but it was very convenient when that
message was shown on the shell too.
Thanks for any help.
Kind regards,
Hilderich
--
View this message in context:
http://karaf
Hi Jochen,
1. if you enable bundle:watch the status will be store in the data
folder. So even if you restart, if you don't remove the data folder, the
bundle:watch will be enabled.
2. it's the case by default: bundle:watch * will watch all SNAPSHOT
bundles, even the new installed (it's
is configured in
org.ops4j.pax.url.mvn.cfg). To avoid additional copying and/or
installing/starting/refreshing bundles, the bundle:watch command comes in
handy.
Now my questions:
1. Is there a way to automatically issue the bundle:watch * command after
startup of the container *and* installation and startup
I just hit the same issue and, as it's a really nice feature in a dev
environment, it would be great to patch it to continue working with 3.0.2 if
possible.
--
View this message in context:
http://karaf.922171.n3.nabble.com/karaf-3-0-2-bundle-watch-not-working-tp4035923p4036010.html
Sent from
Yes, I will push the patch today and expose a patched 3.0.2 bundle (on
my repo) for you.
As reminder, you can do the same using bundle:update periodically
(waiting for the patch).
Regards
JB
On 10/17/2014 10:54 AM, siwatson wrote:
I just hit the same issue and, as it's a really nice
a patched version of the bundle:
http://maven.nanthrax.net/org.apache.karaf.bundle.core-3.0.2.jar
You can download this one and replace the existing one in the Karaf
system folder.
Regards
JB
On 10/14/2014 10:56 PM, maroshi wrote:
Using karaf 3.0.2 bundle:watch fails
See bellow
Hi.
First off, congratulations with the Karaf 3.0.2 release!
And, now the sad part. I have trouble with bundle:watch and get this error:
Exception in thread Thread-32 java.lang.NoClassDefFoundError:
org/apache/karaf/util/maven/Parser
trouble with bundle:watch and get this error:
Exception in thread Thread-32 java.lang.NoClassDefFoundError:
org/apache/karaf/util/maven/Parser
at
org.apache.karaf.bundle.core.internal.BundleWatcherImpl.getBundleExternalLocation(BundleWatcherImpl.java:195
FYI
https://issues.apache.org/jira/browse/KARAF-3283
Regards
JB
On 10/14/2014 08:23 AM, Sten Roger Sandvik wrote:
Exception in thread Thread-32 java.lang.NoClassDefFoundError:
org/apache/karaf/util/maven/Parser
at
Wow. That was a quick reply :-) Thanks.
- Original Message -
From: Jean-Baptiste Onofré j...@nanthrax.net
To: user@karaf.apache.org
Sent: Tuesday, October 14, 2014 8:44:34 AM
Subject: Re: Problems with bundle:watch [Karaf 3.0.2]
Hi Sten,
Actually, karaf.util should be as private
Yes, see https://issues.apache.org/jira/browse/KARAF-3283
As reminder, you can use bundle:update (manually) if you want to stay
with 3.0.2.
Anyway, it will be fixed in 3.0.3.
Regards
JB
On 10/14/2014 10:56 PM, maroshi wrote:
Using karaf 3.0.2 bundle:watch fails
See bellow
Update: In order to work properly the following property has also to be added
to etc/system.properties:
openejb.deployments.classpath.filter.descriptors = true
Regards,
Jochen
--
View this message in context:
Hi,
I thought responsibility for the OSGi version of OpenEJB moved to the Karaf
team (mentioned here: https://issues.apache.org/jira/browse/OPENEJB-2086).
Perhaps it should be described on the OpenEJB page at the Karaf manual?
Regards,
Jochen
--
View this message in context:
Well,
the OpenEJB support kind of stalled right now.
AFAIK the transition to Karaf isn't fullfilled yet.
There have also been some discussions if it wouldn't be best to move it to
ServiceMix instead.
But it's safe to open an issue for the Karf documentation to clearer
specify this
sentence in the
Hi Jochen,
the OpenEJB moves to Karaf is pending, it's not yet done.
I still plan to work on it as soon as the new Karaf releases will be out.
Regards
JB
On 06/24/2014 10:20 AM, jkraushaar wrote:
Hi,
I thought responsibility for the OSGi version of OpenEJB moved to the Karaf
team (mentioned
Thank you Achim and JB. I created an issue and added some further
configuration information I stumbled upon:
https://issues.apache.org/jira/browse/KARAF-3066
Regards,
Jochen
--
View this message in context:
Hi Jochen,
thanks for that. I took the Jira and I will enhance the manual for 3.0.2.
Regards
JB
On 06/24/2014 11:27 AM, jkraushaar wrote:
Thank you Achim and JB. I created an issue and added some further
configuration information I stumbled upon:
Sorry for the late answer:
I was not clear enough regarding the updated bundle. The process is as
follows:
- Karaf is watching all urls with 'bundle:watch *'
- I build a SNAPSHOT osgi bundle with 'mvn clean install' (NOT the
org.apache.openejb.core-osgi 4.5.2 bundle)
- Karaf tries to update
sample for reproduction?
regards, Achim
2014-06-23 8:41 GMT+02:00 sprinz simon.pr...@doubleslash.de:
Sorry for the late answer:
I was not clear enough regarding the updated bundle. The process is as
follows:
- Karaf is watching all urls with 'bundle:watch *'
- I build a SNAPSHOT osgi bundle
The cause of this error is method
org.apache.openejb.config.DeploymentsResolver.loadFromClasspath(...) in
Release 4.5.2 of OpenEJB. Here the URLs of all JARs loaded by the given
ClassLoader are collected. Then the system JARs get removed from the list.
Normally also the OpenEJB JARs should be
Hi,
as I haven't used EJB/OpenEJB in Karaf yet I wasn't aware of this. But this
doesn't seem to be a bug in Karaf. It looks a lot more like it's something
that needs documentation at the OpenEJB project, if not already done there
:)
regards, Achim
2014-06-23 17:07 GMT+02:00 jkraushaar
Hi,
how did you install the bundle in question?
is it a maven coordinate? Like, mvn:groupId/artifactId/version
or is it a file:
or is it a combination of wrap and file or maven?
cause I think the later is hard for the bundle:watch to determine if it's
updated.
regards, Achim
2014-06-18 15
Hi,
the bundle in question is org.apache.openejb.core-osgi 4.5.2.
It is installed as a maven coordinate:
mvn:org.apache.openejb/openejb-core-osgi/4.5.2.
Regards,
Simon
--
View this message in context:
Looks good so far, the only thing that puzzles me, it's a released version,
why would you want to do a bundle:watch / dev:watch on that. I'm not even
sure this works.
regards, Achim
2014-06-18 15:56 GMT+02:00 sprinz simon.pr...@doubleslash.de:
Hi,
the bundle in question
48 matches
Mail list logo
