Stack trace?
On Friday, October 25, 2013, David Bosschaert wrote:
Just rebuilt using a fresh new .m2 on OSX, but am still getting the
same error. Although the NoSuchMethodError reports being on
org.codehaus.plexus.util.cli.CommandLineUtils I wonder could it have
something to do that I'm
So, start 4.x now! :) Release early, release often.
On Mon, Feb 3, 2014 at 12:09 PM, j...@nanthrax.net wrote:
Good points Ioannis,
my point is just about the message for we send to the users and community.
You are right, it took long time to release Karaf 3.0.0, but it doesn't mean
that
Yes, I reported that one. That was quite a nasty one to figure out.
On Thu, Feb 19, 2015 at 5:49 AM, Achim Nierbeck bcanh...@googlemail.com wrote:
Hi,
I've found the issue.
https://issues.apache.org/jira/browse/KARAF-1545
regards, Achim
2015-02-19 11:44 GMT+01:00 Guillaume Nodet
For illustrative purposes, please refer to this github example:
https://github.com/jwcarman/karaf-assembly-example
On Wed, May 13, 2015 at 3:43 PM James Carman ja...@carmanconsulting.com
wrote:
I'm trying to use filtered resources to create a custom distro.
Unfortunately, no matter what I
I figured it out. It was indeed not going after the filtered resources. I
created a pull request against 3.0.x and I can whip something up against
master if you want also:
https://github.com/apache/karaf/pull/61
Please let me know.
On Wed, May 13, 2015 at 4:10 PM James Carman ja
No Karaf 3.0.4?
On Sun, May 31, 2015 at 12:06 PM Jamie G. jamie.goody...@gmail.com wrote:
Sounds good :)
On Sun, May 31, 2015 at 1:16 PM, Jean-Baptiste Onofré j...@nanthrax.net
wrote:
Hi guys,
sorry, I was very busy this week with a customer in the US, and I'm a bit
late with the
Okay great! Sorry, I was reading on my phone and did not see the previous
message
On Sun, May 31, 2015 at 12:11 PM Jean-Baptiste Onofré j...@nanthrax.net
wrote:
Hey James,
see my previous e-mail:
The plan is to submit Karaf 3.0.4 and 4.0.0.M3 to vote end of this week.
--
Jean-Baptiste
+1 (non-binding) tested on some of our current apps in a custom
distribution built using the maven plugin. We're all fine here. Although
I'd like to see the region jar fiasco fixed in 3.0.x. Perhaps I'll provide
a patch.
On Tue, Jun 30, 2015 at 2:25 AM Morgan Hautman morgan.haut...@gmail.com
The jar needs to be upgraded to come from central at least.
On Tue, Jun 30, 2015 at 7:29 AM Jean-Baptiste Onofré j...@nanthrax.net
wrote:
Hi James,
I worked on a fix about region/bundle cache corruption, but I postponed
to 3.0.5.
Regards
JB
On 06/30/2015 01:24 PM, James Carman wrote
There is a newer version in central and master branch uses that right?
On Tue, Jun 30, 2015 at 7:33 AM Jean-Baptiste Onofré j...@nanthrax.net
wrote:
The region jar comes from SMX m2-repo. We can push on oss (Central is a
different story).
Regards
JB
On 06/30/2015 01:30 PM, James Carman
I didn't see Achim's vote either. I still don't.
On Sun, Jul 12, 2015 at 7:34 AM Jamie G. jamie.goody...@gmail.com wrote:
Yes, 3 binding votes is the minimum - that being said, somehow your
vote got caught in my gmail spam filter?! Didn't see it until I was
processing through that folder this
I tried downloading karaf yesterday and it wasn't working. Apparently we
need to fix our download scripts:
https://reference.apache.org/pmc/mirror_scripts
Here is our custom Karaf build against 4.0.x and it is working. I know we
faced some issues also, but they are resolved now. I do not remember the
details.
https://github.com/savoirtech/aetos/tree/4.0.x?files=1
On Mon, Jun 20, 2016 at 6:48 AM Roedl Lukas wrote:
> Hi!
>
>
When Jenkins tried to merge in my patch, it failed the build:
https://builds.apache.org/job/karaf-pr/327/console
Why are we depending upon a SNAPSHOT of CXF in Karaf?
James
<j...@nanthrax.net> wrote:
> IMHO, it's not a Karaf issue but more a blueprint-cm issue.
>
> Regards
> JB
>
> On 08/03/2016 12:48 PM, James Carman wrote:
> > Right, what I'm saying is that Karaf doesn't behave very nicely when two
> > ManagedService's try
man/karaf-whiteboard
The README shows how to install it. Now, keep in mind that this behavior
isn't consistent. But, try it a few times and you will see the looping it
does in the logs.
On Wed, Aug 3, 2016 at 6:48 AM James Carman <ja...@carmanconsulting.com>
wrote:
> Right, what I'm
Are we past the 72 hours on this one?
On Mon, Aug 8, 2016 at 3:59 AM Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Karaf Container 3.0.8 release to your vote.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12335948
>
>
On Fri, Jul 8, 2016 at 2:35 PM Marc Durand wrote:
> I am not sure how a CXF annotation can work in my case - I am not using CXF
> at all. I am using Jersey and OSGI-JAX-RS-Connector.
>
>
Oh, then my suggestion won't work either. Sorry. :(
You can also just add the GZIPFeature to your JAX-RS server.
On Fri, Jul 8, 2016 at 1:46 PM Benson Margulies
wrote:
> @GZIP on the resource class works for me.
>
>
> On Fri, Jul 8, 2016 at 1:44 PM, Marc Durand wrote:
> > I have successfully added a
+1 (non-binding)
Tested by installing some of our current applications and everything
appears to be working properly. Nice work! Thanks for getting this out so
quickly, JB.
On Mon, Aug 8, 2016 at 3:59 AM Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Karaf Container
When implementing the fix for KARAF-4642, I noticed that the
FeaturesService's installFeatures() method takes a Set
(Set in 3.0.x). I propose we change that when we can to
Iterable to indicate that we will iterate through what they give us
and install them *in order*. It would be a source
When two different bundles use the same configuration pid, you can get into
a very weird restart loop (at least with blueprint). It violates the
specification for two bundles to try to use the same configuration.
Shouldn't we just fail to start the second bundle if the pid is already
"claimed"?
What blood type are you in case we need to donate to get you back in shape
in two weeks? ;). Have a great vacation. Is there anything any of us can
do to help with the release stuff so you can continue with the tequila
without distractions?
On Thu, Feb 2, 2017 at 9:20 AM Jean-Baptiste Onofré
oon as the vote period
> is complete and we have 3 binding votes, I will promote the artifacts,
> and update Jira. I will do that, no worries.
>
> If (for any reason), I'm not able to do it from the hotel, I will let
> you know.
>
> Thanks,
> Regards
> JB
>
> On 02/02/2
when the configuration change especially).
>
> Regards
> JB
>
> On 08/02/2016 09:53 PM, James Carman wrote:
> > When two different bundles use the same configuration pid, you can get
> into
> > a very weird restart loop (at least with blueprint). It violates
I am +1 on removing it, especially if nobody wants to maintain it. I tried
to use it at one point and it just never really worked well. Hand-crafted
features files are always the best option, IMHO. It might be nice to have
a Maven archetype or something that would generate a "features module"
We've been working on a Microservices framework called "Microbule" which
leverages CXF and Karaf (hence the cross-post):
https://github.com/jwcarman/microbule
The idea is to make writing Microservices easy and fun, by providing many
of the oft-requested features for you out-of-the-box (CORS,
ithub.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
>
> > We've been working on a M
By the way, I should give credit to Benson Margulies for giving me the
"secret sauce" of creating CXF servers on-the-fly! Thanks, Benson!
On Mon, Nov 21, 2016 at 1:03 PM James Carman <ja...@carmanconsulting.com>
wrote:
> We've been working on a Microservices framework calle
FYI, Microbule has now moved:
https://microbule.github.io/microbule/
On Mon, Nov 21, 2016 at 1:03 PM James Carman <ja...@carmanconsulting.com>
wrote:
> We've been working on a Microservices framework called "Microbule" which
> leverages CXF and Karaf (hence the
Small update. Microbule 0.1.0 release has been cut and will soon be
available in Maven Central (awaiting sync from Nexus OSS). Enjoy, folks!
On Mon, Nov 21, 2016 at 1:03 PM James Carman <ja...@carmanconsulting.com>
wrote:
> We've been working on a Microservices framework called &
org> wrote:
> I've raised KARAF-4825 with a proposal for a fix, let me know what you
> think.
>
> 2016-11-18 17:41 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
>
> > This was when using the features:install after getting into the console.
> > It really seems
-maven-plugin
> ${meecrowave.version}
>
>
>
>
> Then start with
>
> $> mvn clean install meecrowave:run
>
> Will push a sample project soon.
>
> LieGrue,
> strub
>
> > Am 21.11.2016 um 22:41 schrieb James Carman <ja...@carmanconsulting.c
ion I was about
> to ask in a "What's in a Name" section at the end :-)
>
> Microbule, Meecrowave - the massive wave is coming :-)
>
> Cheers, Sergey
>
>
> On 21/11/16 18:11, James Carman wrote:
> > The header names are configurable, so you can use
Karaf 3.0.8+ now provides predictable boot feature startup order, but the
4.0.x line does not provide that guarantee. It apparently tries to be
smart and figure out what you need, but sometimes it just works better if
we can let the user control things explicitly. Is there, perhaps, a
compromise
You mean installing the features one by one instead of all in one go ?
> Have you tried using
> (myfeature1,myfeature2),(myfeature3,myfeature4)
> so that you end up with 2 stages ?
> Ultimately, you can use
> (myfeature1),(myfeature2),(myfeature3),(myfeature4)
>
> 2016-11-1
not much tied to karaf and
> could be reused in 3.x I think.
>
> 2016-11-18 17:33 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
>
> > Another issue I'm seeing with 4.0.7 right now is that the install order
> > doesn't really seem to make sense. For example, I've
e the same. If the
> problem is a wiring problem because you have packages exported by multiple
> bundles, I've tried to fix some of this problem in 4.1 by ensuring that the
> same wiring is reused after a reboot.
>
> 2016-11-18 17:13 GMT+01:00 James Carman <ja...@carmanconsulti
t;core" bundle, but for some
reason, Karaf is installing "core" first and then installing "spi" much
later. Is that expected behavior? It seems strange to me.
On Fri, Nov 18, 2016 at 11:30 AM James Carman <ja...@carmanconsulting.com>
wrote:
> The main issue I faced
features);
> for (Set features : stagedFeatures) {
> featuresService.installFeatures(features,
> EnumSet.of(FeaturesService.Option.NoFailOnFeatureNotFound));
> }
> featuresService.bootDone();
>
>
>
> 2016-11-18 17:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
Oh, cool! Thanks, Guillaume! I'll take a look when I get some cycles
(hopefully soon).
On Fri, Nov 18, 2016 at 3:33 PM Guillaume Nodet <gno...@apache.org> wrote:
> I've raised KARAF-4825 with a proposal for a fix, let me know what you
> think.
>
> 2016-11-18 17:41 GMT+01:0
We have a little library we use called Eos to do ManagedServiceFactories
(ManagedService is a bit easier):
https://github.com/savoirtech/eos
The "itest" module(s) have an example of how to wire it up using Blueprint:
You can run the SNAPSHOT to try it out, right?
https://repository.apache.org/content/groups/snapshots/org/apache/karaf/apache-karaf/4.0.8-SNAPSHOT/
On Mon, Dec 12, 2016 at 9:56 AM Kai Kreuzer wrote:
> Hi JB,
>
> Sounds great - are you confident enough that the ARM support
Well, what are you waiting for! ;) My bad, I thought it was already there.
Never mind me! :)
On Mon, Dec 12, 2016 at 11:05 AM Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:
> Correct, but the fix is not yet there ;)
>
> Regards
> JB
>
> On 12/12/2016 04:24 PM, James C
Oftentimes you can avoid it entirely. What is your use case?
On Thu, Jun 22, 2017 at 6:07 AM Dominik Marciniszyn <
marciniszyn.domi...@gmail.com> wrote:
> Hi,
>
> I have two osgi bundles and I would like to get some resources files from
> one bundle to another. I've used BundleContext to get
I'm trying to automatically enable asynchronous logging by default and the
config file says:
# uncomment to use asynchronous loggers, which require
mvn:com.lmax/disruptor/3.3.2 library
log4j2.rootLogger.type = asyncRoot
So, I uncommented it (as you can see), but "disruptor" isn't visible at
Renaming subject. By the way, I tried adding disruptor as a compile-scoped
dependency (after looking at the AssemblyMojo code) and it appears to do
the same thing.
On Thu, May 18, 2017 at 12:24 PM James Carman <ja...@carmanconsulting.com>
wrote:
> I'm trying to automatically enable asy
First of all, yes, I'm impatient! :) Anyway, I used to be able to hit the
up arrow while a command was executing (say feature:install or something)
so that I could bring up the next command I was going to run. Now, it just
starts printing "[A[A[A" characters to the console. Is there some way to
r?
Thanks,
James
On Tue, May 23, 2017 at 7:03 PM James Carman <ja...@carmanconsulting.com>
wrote:
> I am trying to use a custom layout and I'm following the examples (I
> think). We had one that worked in Karaf 3.0.x. Anyway, I set up the
> fragment host like this:
>
>
I am trying to use a custom layout and I'm following the examples (I
think). We had one that worked in Karaf 3.0.x. Anyway, I set up the
fragment host like this:
org.apache.felix
maven-bundle-plugin
3.3.0
true
true
org.ops4j.pax.logging.pax-logging-service
However,
this is a new
> issue or an existing one.
>
> On 24 May 2017 at 05:43, James Carman <ja...@carmanconsulting.com> wrote:
>
> > I tried adding pax-logging-service to startup.properties (after putting
> it
> > into the system repo) and I still have the issue. So, the ultimate
an option you can set to scan a particular list of
> packages for additional plugins, though I think that uses the context
> ClassLoader which might not work properly in your scenario.
>
> On 24 May 2017 at 11:22, James Carman <ja...@carmanconsulting.com> wrote:
>
> > A
into karaf to see if it works for me?
On Wed, May 24, 2017 at 3:20 PM Matt Sicker <boa...@gmail.com> wrote:
> I mostly work on Log4j2, though I try to answer questions about it on ops4j
> and karaf due to pax-logging.
>
> On 24 May 2017 at 14:17, James Carman <ja...@carman
activator in both
> log4j-api and log4j-core from what I recall, so pax-logging might need
> something custom as well.
>
> On 24 May 2017 at 17:41, James Carman <ja...@carmanconsulting.com> wrote:
>
> > So, I've done a bit of digging. Log4j2 ships with an Activator that sets
doesn't run. Perhaps we should delegate to Log4j's internal Activator
during the start() method of the Pax Logging Activator
(org.ops4j.pax.logging.log4j2.internal.Activator)? Do we cover this
behavior in some other way?
On Wed, May 24, 2017 at 3:32 PM James Carman <ja...@carmanconsulting.
+1 for GSON.
On Thu, May 25, 2017 at 10:18 AM Matt Sicker wrote:
> From what I understand, this only applies to the org.json dependency. Most
> people tend to use Jackson or Gson in my experience which are appropriately
> licensed.
>
> On 25 May 2017 at 08:41, Jean-Baptiste
Nice! Thanks!
On Fri, Jun 2, 2017 at 7:30 AM Guillaume Nodet <gno...@apache.org> wrote:
> Actually, I just fixed it:
> https://issues.apache.org/jira/browse/KARAF-5176
>
> 2017-05-23 15:00 GMT+02:00 James Carman <ja...@carmanconsulting.com>:
>
> > First of all,
I'm also cool with "dog-fooding" Apache Johnzon. I just have a lot of
experience with GSON and have found it to be a breeze to work with (that's
why I use it in Microbule by default).
On Thu, May 25, 2017 at 12:56 PM Achim Nierbeck
wrote:
> I'm not a friend of
On Tue, Jan 8, 2019 at 12:59 PM Jean-Baptiste Onofré
wrote:
> Hi James,
>
> no the startup.properties is generated by the plugin, using the scope.
> So, karaf framework kar is probably missing in your project.
>
>
You mean this?
ue, Jan 8, 2019 at 2:24 PM Jean-Baptiste Onofré wrote:
> Exactly, the scope should be provided ;)
>
> Regards
> JB
>
> On 08/01/2019 19:11, James Carman wrote:
> > On Tue, Jan 8, 2019 at 12:59 PM Jean-Baptiste Onofré
> > wrote:
> >
> >> Hi James,
>
ple as it should. I will simplify this.
>
> Regards
> JB
>
> On 08/01/2019 20:50, James Carman wrote:
> > When I change the kar scope to "provided", I get:
> >
> > Failed to execute goal
> > org.apache.karaf.tooling:karaf-maven-plugin:4.2.2:assembly
> >
We are trying to build our own custom Karaf 4.2.2 distribution and
when we include the enterprise feature repository along with the
ActiveMQ 5.15.8 feature repository, we get an invalid
org.apache.karaf.features.cfg file which includes 4.2.3-SNAPSHOT
versions of some of the boot features. I have
Oh, guess I have some reading to do! Thanks, JB!
On Tue, Jan 8, 2019 at 8:29 AM Jean-Baptiste Onofré wrote:
> It's already possible via cap/req in features (as we do in Pax Web for
> instance).
>
> Regards
> JB
>
> On 08/01/2019 13:50, James Carman wrote:
> > I see
I am trying to create a custom distribution:
https://github.com/jwcarman/custom-karaf-example/tree/vanilla
When I cd into the target/assembly directory and do:
bin/karaf
the logs stop after this:
Jan 08, 2019 11:11:01 AM org.apache.karaf.main.Main launch
INFO: Installing and starting initial
he.felix/org.apache.felix.fileinstall/3.6.4 = 11
> mvn\:org.apache.karaf.features/org.apache.karaf.features.core/4.2.2 = 15
> mvn\:org.apache.servicemix.specs/org.apache.servicemix.specs.activation-api-1.1/2.5.0
> = 30
>
> and it looks nicer.
>
>
>
> > On Jan 8, 2019, at 9:12 AM, James
But, that begs the question, should we really have to do that? Is
something wrong with the plugin that it isn't copying the "standard"
startup.properties file from the base distro?
On Tue, Jan 8, 2019 at 11:56 AM James Carman
wrote:
> That got it working for me. Thanks, Johan!
the karaf-assembly.
> >>
> >> I created a PR on your project fixing the issues.
> >>
> >> Anyway, it confirms what I sent some weeks ago: creating a custom
> >> distribution is not as simple as it should. I will simplify this.
> >>
> >> Reg
ures repo is used in the standard
> Karaf
> > distribution, so it's weird that it works here. It's maybe a
> combination
> > of features.
> >
> > For the tracking I created:
> https://issues.apache.org/jira/browse/KARAF-6075
> >
> > Rega
ose" features or custom distribution is convenient.
>
> Generally speaking, I prefer "open" features repo, and eventually create
> my own custom distro (as the "kloud" one).
>
> Regards
> JB
>
> On 08/01/2019 12:42, James Carman wrote:
> > I’m r
69 matches
Mail list logo