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
Hi Thomas,
regarding your ideas, we have the same:
1/ the blacklist/filtering is already on the road
2/ the SLA for alerting is also already in the plan.
Regards
JB
On 10/17/2014 11:42 AM, Walzer, Thomas wrote:
Hi all,
I like the idea. The name is cool. Karaf could benefit from a standalone
Hi,
2014-10-08 13:24 GMT+03:00 Jean-Baptiste Onofré j...@nanthrax.net:
No,
it's not Apache compliant ;)
An Apache release has to respect rules (verification, etc): sign, legal
checks, etc.
Regards
JB
Technically, the Apache Foundation is only concerned about source
releases. Binaries
This is for apache foundation, but don't forget the engagements of the
apache license (in terms of legal).
Regards
JB
On 10/17/2014 01:24 PM, Ioan Eugen Stan wrote:
Hi,
2014-10-08 13:24 GMT+03:00 Jean-Baptiste Onofré j...@nanthrax.net:
No,
it's not Apache compliant ;)
An Apache release
As you can see in:
https://issues.apache.org/jira/browse/KARAF-3283
it's a typo mistake (my bad, I'm very sorry about that :().
It's already fixed on Karaf 3.0.3-SNAPSHOT.
For 3.0.2 user, you can edit the MANIFEST of the bundle.core bundle to
fix that.
Else, I deployed on my server a
Hi all,
following up on the latest issue with bundle:watch I have a related
question. I am using the standard (as in documented here
http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html)
way to construct a Karaf instance which would run my feature (and a few
related
Hi Oliver,
what ever you put into the system folder, if you use a SNAPSHOT
artifact, you can update on the fly with bundle:update and bundle:watch.
By default, bundle:update/bundle:watch take the bundle location
(containing the mvn URL), and check in your local maven repository
FYI: https://issues.apache.org/jira/browse/KARAF-3324
Regards
JB
On 10/17/2014 08:39 PM, Oliver Pajonk wrote:
Hi all,
following up on the latest issue with bundle:watch I have a related
question. I am using the standard (as in documented here
