I'm trying to get started with Karaf, and am having a few issues.
I have created a simple OSGi enroute project using bndtools in eclipse. I have
created a feature.xml file for it and have installed it in karaf. So far so
good.
The default project that bndtools generates includes a gogo command.
I started using Karaf yesterday. Version 4.0.6.
Not aware of shell-compat. What does it do? I can't see it mentioned in any
documentation.
Naively tried installing it. Doesn't seem to change my ability to run a gogo
shell command that I can see?
> On 19 September 2016 at 17:08 Benson Margulies
What's the best way of deploying an application from a CI build such as Jenkins,
into Karaf, for the purposes of testing?
I was hoping to set something up so that I have a jenkins job that builds my
application and then deploys the built application to a test instance on karaf.
The karaf would be
Up until now I've been developing code using bndtools in eclipse, writing bndrun
files, resolving them, and running my application that way. The resolution step
resolves all the requirements from the set of OBR repositories. All very easy
(well, it is now, once I got over the learning curve :-) )
> you can use Pax Exam[1] for that and start Karaf embedded, this will give
> you a clean state for every run.
Initially I want to do it for testing, but I then want to deploy a "snapshot"
and "release" version of the actual application for general internal demo use. I
currently already have an in
According to the documentation, the OSGi Log service is supported.
I'm trying to install a bundle that uses it, and I get:
missing requirement [bundleid/1.0.0.201609201024] osgi.service;
filter:="(objectClass=org.osgi.service.log.LogService)"; effective:=active]]
My use is with DS, so:
I'm really struggling to get my bundles installed in Karaf, so I'd appreciate
some hints on how to diagnose some issues. I'm trying to do a feature:install of
a features.xml file I've written to install my bundles.
My latest is:
missing requirement osgi.wiring.package;
filter:="(&(osgi.wiring.pac
> On 20 September 2016 at 12:52 Benson Margulies wrote:
>
>
> I build all my features with the karaf-maven-plugin.
>
I don't use Maven, I use eclipse and bndtools, hence gradle as my build
environment. Since I didn't have to do anything at all to get the gradle command
line build set up, it w
016 at 13:19 David Daniel
> wrote:
>
>
> Tom integrating karaf development and bndtools development has been tricky
> but it is getting better. Karaf development is centered around Mavens
> build process while bndtools is centered around a custom workspace in cnf.
> This releas
I'm tracking down a rather odd problem trying to deploy a bundle into Karaf. The
issue appears to be with the osgi.enroute.dto.api package.
I'm getting this resolution error from Karaf:
missing requirement: osgi.wiring.package;
filter:="(&(osgi.wiring.package=osgi.enroute.dto.api)(version>=1.0.0)
Achim,Thanks.
I'm trying to use mvn, as it does seem the best option. If I can get it to do
what I want though.
What I'm trying to work out is how to ensure that I get exactly the bundle
that's just been published, and nothing gets cached.
I'm publishing SNAPSHOT builds to our artifactory reposit
How do I create and then manage a new instance using jolokia?
I can execute the commands on my root instance to create and start a new
instance fine. On create I specify that I want "jolokia" as a feature.
Fundamentally, in order to manage the second instance I have to connect directly
to it don'
For test purposes we have a small java program that automatically deploys our
built bundles into a Karaf container as part of the build and test process.
However, the deployment process is unreliable.
Basically what we do is connect to the main Karaf container and create a new
instance. Then conne
I'm trying to use the Karaf maven plugin to build a custom Karaf distribution
(so "karaf-assembly" packaging type)
I'm stuck on the following error though:
Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:4.1.1:assembly (default-assembly)
on project karaf-distro: Unable to bu
With regard to the "wrap/0.0.0" error, running Maven with -X gives me:
Caused by:
org.apache.karaf.features.internal.service.Deployer$CircularPrerequisiteException:
[wrap/0.0.0]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:266)
at org.apache.karaf.
OK, I've "solved" this by creating an additional bundle that simply has the
required:
Provide-Capability: osgi.contract;osgi.contract=JavaServlet;version:Vers
ion="3.1";uses:="javax.servlet,javax.servlet.http,javax.servlet.descrip
tor,javax.servlet.annotation"
line in the MANIFEST.
I say "sol
I've attempted to build a simple custom Karaf distribution using the maven
plugin and the karaf-assembly packaging.
I can build the assembly, but when I start the result I get an exception.
My pom configuration is currently very simple, just:
org.apache.karaf.features
> On 13 June 2017 at 09:08 Jean-Baptiste Onofré wrote:
>
>
> Hi Tom,
>
> Here's a pom.xml to do what you want:
As far as I can see that's the same as the "minimal example" in the docs.
If I use your example, I still get errors:
2017-06-13T09:46:01,6
> On 13 June 2017 at 12:32 Jean-Baptiste Onofré wrote:
>
>
> I don't understand why you have the pax-web feature.
>
> Do you have it defined in bootFeatures ? Or do you install it by hand ?
>
> I can confirm that I don't have pax-web feature on my custom distro.
So I created a completely fres
Start up Karaf with the "bin/karaf.bat" shell script.
At the console type
help bundle:info
You get:
gogo: NullPointerException: "in" is null!
If I run this from the official 4.1.1 install, it looks like this is trying to
"more" the help contents or something. I get a colon, and if you press q it
> On 13 June 2017 at 15:02 Jean-Baptiste Onofré wrote:
>
>
> Hi Tom
>
> It has been fixed and will be included in 4.1.2.
>
Ah, good. 4.1 seems unusable as far as I can see otherwise.
I've been looking around, but I can't find where I might get a snapshot build
> On 13 June 2017 at 15:50 Jean-Baptiste Onofré wrote:
>
>
> Do you have a chance to test with 4.1.2-SNAPSHOT ?
That's what I'm wanting to do, I just can't work out where to get it. I naively
put
4.1.2-SNAPSHOT
as my karaf version in the pom, but it doesn't find it, as I presumably need to
Windows, yes.
> On 13 June 2017 at 15:51 Jean-Baptiste Onofré wrote:
>
>
> By the way, are you on Windows ?
>
> Regards
> JB
>
> On 06/13/2017 04:44 PM, t...@quarendon.net wrote:
> >
> >> On 13 June 2017 at 15:02 Jean-Baptiste Onofré wrote:
> &g
> On 13 June 2017 at 16:50 Jean-Baptiste Onofré wrote:
>
>
> Yeah, you have to add the snapshot repository in your pom.xml:
OK, yes, that's better.
Thanks.
Now all I need to do is work out why I can't apparently satisfy
(&(osgi.extender=osgi.component)(version>=1.3.0)(!(version>=2.0.0)))"
I'm trying to build a custom karaf distribution with the "karaf-assembly" maven
packaging.
I am making slow progress :-)
My latest issue comes about through trying to resolve lack of a javax.servlet
package requirement.
So I naively included the org.apache.felix:org.apache.felix.http.servlet-
> the easiest would be to actually remove that "new" requirement for those
> components.
> A fix for this is on it's way for Pax Web, so you'll have something that'll
> work for you.
Sorry Achim, you'll need to spell that out. What is that you'd fix? Create a
pax-web bundle that contains and expo
I'm trying to build a custom karaf distribution using the maven karaf-assembly
packaging type.
My latest issue is that the build fails with
missing requirement osgi.extender;
filter:="(&(osgi.extender=osgi.component)(version>=1.3.0)(!(version>=2.0.0)))"
I interpret this as meaning the bundle
> Can you share your sample project ?
I will try to put together a simple standalone test case. In fact I'll do that
for something else as well that I can't get past.
I have put together a simple example of the problem I'm been encountering
attempting to create a custom karaf distribution.
If you attempt to include a bundle such as
org.apache.felix:org.apache.felix.http.servlet-api in a feature, you get this
build error:
missing requirement [org.ops4j.pax.u
Oddly I can no longer reproduce the issue.
I thought it might have gone away because I'd added:
scr
into my feature in the features.xml file. However I take that out again and it
still works. Odd.
If I encounter it again, I'll reduce to a simple test case.
> On 14 June 2017 at 09:45 Jean-Bap
> I propose to share the code and chat directly (on hangout/skype/private
> e-mail).
Any help you can give me would be greatly appreciated.
I have many issues that I'm trying to resolve, as you can tell.
I've been struggling to get our code that uses Hibernate to work within Karaf
4.1 today.
I have created a simple test case, which is on github:
https://github.com/tomq42/karaf-tests-hibernate. There are a variety of
branches, each with a different combination of hibernate and karaf. The
branche
Forgive my maven ignorance, but I’d like to retrofit some source with a maven
build that uses the felix maven bundle plugin, it’s just my source isn’t in
src/main/java.
Can I do that?
If so, can someone provide a simple example?
It’s not clear how the source even gets compiled to me. I’ve used t
There was a thread recently related to this, but I have a different question.
I'm confused about the shell situation, and what is "standard" and what is not.
I have naively written some commands for the felix gogo shell. We develop using
bndtools (obviously) and use the OSGI enRoute templates, a
Yes, but what's the actual situation from a standards point of view?
Is a shell defined by a standard at all? OSGi enroute seems to require a gogo
shell and appears to rely on felix gogo shell command framework.
Is it just that Karaf happens to ship a shell that happens to be based on the
felix g
> If you look at Karaf >= 4.1.x, a bunch of commands are not coming from
> Karaf anymore, but from Gogo or JLine. I moved them when working on the
> gogo / jline3 integration. The main point that was blocking imho is that
> they did not have completion support. With the new fully scripted
> comp
I'm running this on Windows, I don't know whether the same is true on Linux.
I'm using Karaf 4.1.2.
If I run the karaf.bat file, I see my branding from my etc/branding.properties
file appear.
If I then run the client.bat file (or a standard SSH client), I see the normal
Karaf logo.
The effect
The Karaf user guide section 4.1 says:
The Apache Karaf security framework is used internally to control the access
to:
the OSGi services (described in the developer guide)
However the developer guide doesn't say anything that I can see about what that
means. 5.15 in the Karaf user guide
If I'm logged on to the console as user, the list of commands I can execute is
controlled by access control lists.
So, if I'm logged on as a user who has only got the "viewer" role, then I can't
shut karaf down, the system:shutdown command requires the "admin" role.
Great.
However, I still ap
I just wanted to check that in the absence of an explicit access control list
for commands in the console, the default is to be to allow anyone access.
Can that be altered at all? Is there a way of providing a default access
control list at all? Or do I have to make sure I provide one for each co
Any user that can log on to the karaf console appears to be able to run the
"shell:cat" command (among others), and hence view any file that the operating
system user that's running the karaf process can see. Whilst there is access
control on a few of the shell scope commands, it seems that the
Well that was a supplemental question actually.
Within a single access control list for a particular scope, I can presumably
provide a catch all "*" entry at the bottom of that file, so that I can define
a default access control list for all commands *within that scope*, but can I
provide one th
nks anyway.
> On 31 August 2017 at 13:02 Jean-Baptiste Onofré wrote:
>
>
> Hi Tom,
>
> We don't use the ACL in the completers, only on the action step. That's why
> you
> can complete but not execute.
>
> Regards
> JB
>
> On 08/31/2017 12:35 PM,
OK, JIRA created.
I realise it's worse. I can *write* to files with "tac", so I can rewrite the
users.properties file if I want to and create new users with admin priviledges.
Cool.
> On 31 August 2017 at 13:04 Jean-Baptiste Onofré wrote:
>
>
> I agree: as we did for vi/edit command, we sh
I'm trying to get an idea of how people go about developing for karaf, from a
practical point of view.
So karaf is maven focused. There are archetypes for creating command, general
bundles and so on.
I can then use maven to generate some eclipse project files that allow me to
write and compile
f the current situation anyhow.
> On 05 September 2017 at 13:07 Jean-Baptiste Onofré wrote:
>
>
> Hi Tom,
>
> You can also create your own Karaf custom distro.
>
> We are also discussing about Karaf Boot to simplify the bootstrapping/ramp up
> on
> Karaf. Short
Clearly this can't be true, since karaf ships with features containing bundles
containing commands, but I can't get it to work.
I've created a simple karaf shell command, following the tutorial in the
documentation. As per the example, it just says "hello world".
If I build that as an isolated b
There's a complete example here:
https://github.com/tomq42/karaf-command-feature
Thanks.
> On 07 September 2017 at 09:15 Jean-Baptiste Onofré wrote:
>
>
> Hi Tom,
>
> can you share the pom.xml you use to create your custom distro ?
>
> It looks like some resour
> Thanks, I'm checking out and I will take a look (and eventually submit a PR
> ;)).
OK, thanks.
So although moving
eventadmin
out of startupFeatures makes the command work, it seems to break a bunch of
other things, so doesn't seem wise afterall. E.g, I get things like the
following that only seem to happen if I've moved that line:
Bundle org.ops4j.pax.web.pax-web-extender-whiteboard [115
Really? I find this somewhat hard to believe, but I'm fairly sure this is the
case.
Anyway. I'm using config admin to update a configuration from within a karaf
command. One of the properties is a string that contains a filename. I'm on
Windows. Filename therefore contains backslashes.
I type i
I'm trying to establish some alternative configuration behaviour than what
felix-fileinstall gives me.
I have written a very simple component that reads configuration files in from
/etc and updates config admin with the information, much like fileinstall does.
I can run this and it appears to wo
I can see KARAF-418, but that's pretty old, and sounds like it was considered
unnecessary? Is there anything else I can't find?
I don't necessarily want to store things in a database, I just want different
behaviour to normal, to provide my own implementation of something that listens
to config
> You can implement your own PersistenceManager (ConfigAdmin service).
OK, I'm actually super confused now (not hard).
felix configadmin appears to have logic in it that persists configurations to
and from files. It's unclear in the karaf environment where the
FilePersistenceManager is attempti
Documentation indicates I can do this. Pax logging indicates I can do this.
Yet when I try, I can't.
I have some code that uses java.util.logging. If I log at level SEVERE, it
comes out on the console, and only the console, and doesn't come out in the
karaf.log file. Anything less than that and
> Yet when I try, I can't.
OK, so that's frustrating.
If I try a simple "hello world" bundle that just logs a message, run in a clean
karaf, it DOES come out in the karaf.log file.
Run it in our application though and it doesn't.
So some bundle is interfering with the logging configuration in som
> can you check if JUL packages really comes from Pax Logging ?
Err, how can they? Perhaps I'm misunderstanding.
Surely the java.util.logging packages are provided by the JRE?
I DO have one log message that DOES come out. Very odd.
If I step through the code in the debugger, I appear to have tw
> I don't believe we explicitly list that anywhere as a requirement
Correction. We DID include this as a bundle in one of our features:
mvn:org.ops4j.pax.logging/pax-logging-service/1.10.1
but it doesn't seem to be required, removing it doesn't introduce any
resolution issues.
Removing it ma
We've seen the same thing. 4.1.3 had a problem, 4.1.5 has a different problem,
4.1.4 is the sweetspot at the moment. I can't recall the details, I'll dig them
out.
> On 05 March 2018 at 13:02 Jean-Baptiste Onofré wrote:
>
>
> Hi Nicolas,
>
> the big issue is just Windows ;)
>
> Without kidd
There was an incompatibility I believe in 4.1.3, where a dependency introduced
a breaking change in a point release that was picked up by karaf. 4.1.5 has
similar problems, though I don't know what the exact cause is there yet. We
jumped to 4.1.5 and then back down to 4.1.4 as that one worked. I
For largely historical reasons we have ended up with a setup where we use the
standard karaf HTTP whiteboard service, and then run jersey on top of that with
our own homebrew whiteboard service to register JAXRS endpoints.
I'm looking to replace this with a better solution, presumably based arou
> You should then be able to get away with relatively few bundles. The JAX-RS
> Whiteboard API, OSGi Promises + function, the Aries wrapping of the JAX-RS
> API and the Aries JAX-RS Whiteboard implementation should be enough. This is
> by far preferable to using CXF directly, where you don’t hav
> that won't work out of the box as Karaf 4.2.x is still R6.
>
> It will work with Karaf 4.3.x that will be R7.
>
> In the mean time, I'm creating a very simply rest whiteboard pattern for
> CXF.
> It doesn't use all the JAXRS whiteboard spec, but just works fine for
> most of the use cases.
OK,
> Honestly, it sounds like you’re about 30 minutes away from having the Aries
> JAX-RS Whiteboard working...
OK, Understand your reference to servicemix annotation earlier.
I had to pick up the org.apache.felix.http.servlet-api-1.1.2.jar to get the
JavaServlet contract version 3.1.
I've now go
> The SSE from JAX-RS 2.1 definitely works (client and server side) with the
> Aries implementation, so hopefully that will give you everything that you
> need.
I have it all working now. I've had to make one or two changes though, as a
result of the change from jersey to cxf.
Generally, th
> Did you notice that the JAX-RS Whiteboard provides a ClientBuilder
> (prototype scoped) service?
>
> e.g.
> @Reference
> ClientBuilder clientBuilder;
>
Ah, no, I hadn't. I had read the words, but obviously not understood the
significance.
Thanks for the pointer.
> as I'm creating the Aries JAXRS feature for Karaf, I'm currently using
> the one from Aries.
That's the one I used.
I'm trying to experiment with an alternative way of loading up configuration.
So my goal is to disable felix fileinstall and provide an alternative
implementation of the org.apache.felix.cm.PersistenceManager interface.
However, so far I'm having great difficulty either blacklisting fileinstall
> I've implemented a SQL mechanism for persisting configurations. I started
> by trying to implement a custom persistence mechanism for Felix CM. This
> didn't work (see
> http://karaf.922171.n3.nabble.com/Custom-PersistenceManager-configurations-not-instantiating-components-td4052786.html#a4052799
> You should remove fileinstall from etc/startup.properties to remove it.
So how would I do that from a maven build? We're using the karaf maven plugin,
so the startup.properties file gets generated automagically. I'm guessing I'd
have to either put a version of it in my filtered_resources/etc o
> I'm working on a Karaf Configuration persistence layer to "abstract"
> fileinstall, (especially to deal with encryption, AWS keys, etc). It
> will help you to implement your own backend.
That will be awesome. Any targeted release date?
Thanks.
> You have to create a custom framework features that you use at
> startupFeature instead of the "standard" karaf feature.
OK I see. I've been reluctant to do this in the past as I have to make sure to
track changes that occur in the versions of the "normal" one. But it sounds
like the simplest
Just as an update, this is what I've ended up doing, at least for a PoC.
I struggled for a while to try and completely remove fileinstall. I'm sure it's
probably possible, but in the end it was easier to "move it out of the way".
In custom.properties, I set:
* felix.fileinstall.enableConfigSave to
I'm wanting to automate some setup of a karaf based product. I want to create a
docker image that is pre-configured for internal testing.
In order to do this I need to run some karaf shell commands.
What I was naively hoping to do is do something like:
/opt/karaf/bin/start && /opt/karaf/bin/clie
> No way to use etc/shell.init.script ?
Sorry, not sure I understand how that would help. That's a way I could get
shell commands to be run automatically I'm assuming. That's part of my problem.
The main problem is establishing whether the commands are available to run.
> FYI, I fixed an issue i
> By the way, you can also add a delay to have shell available. You can do
> this by adding karaf.delay.console=true in etc/config.properties.
That looks promising.
Can I set that other than in etc/config.properties? Can I set it in
custom.properties for example (no), or somewhere similar?
I don
> FYI, I fixed an issue in client, now you can inject directly a script.
Do you mean there's a way of using the "karaf" command and running a script?
With the karaf.delay.console=true setting you can't pipe a script in to the
karaf command, as it misinterprets the end of line as "Press Enter to
> Using "start && client -f commands.txt && stop" a) seems unreliable and b)
> would seem to need a sleep anyway as otherwise the client tries to connect
> while karaf is still starting.
Note that trying the "-d" and "-r" options on the bin/client along with -f
seems to result in either "miss t
> Did you try with 4.2.4 (as I did the fix on the client thread in this
> version) ?
Not sure what issue you have fixed (perhaps you could expand?) but the problem
I have still remains.
The problem I have is the number of arguments that are passed from the BAT file
to java:
ARGS=%2 %3 %4 %5 %6
> Not sure what issue you have fixed (perhaps you could expand?) but the
> problem I have still remains.
Note also that the client appears to forget the password set on the command
line if it has to retry (JIRA raised):
> client -u admin -p admin -r 30
> Logging in as admin
> retrying (attempt
> No way to use etc/shell.init.script ?
I've understood this comment now.
The best method seems to be to use the pattern of:
set EXTRA_JAVA_OPTS=-Dkaraf.shell.init.script=
-Dkaraf.delay.console=true
bin\karaf
(or equivalent)
Then ensure that the file ends with "shutdown -f".
This seems to wo
We've tried to upgrade to karaf 4.2.3/4 and have hit a problem.
I don't believe we explicitly use org.glassfish.jaxb ourselves, but karaf has a
dependency on it. Karaf 4.2.3 updated this dependency to 2.3.2, and that's a
java 9 module.
So with a fresh karaf 4.2.4, if you do:
bundle:install -s
7;t work it out, where those errors come from and whilst my
bundle does come up my beans aren't injected, does anyone have a good idea?
Thanks
Tom
Boo, actually I resolved that weirdness, that was due to me overriding the
default classpath, but when it starts I don't get any beans injected which
gives me a sad face...
Tom
On Wed, Jul 29, 2015 at 10:38 PM, Achim Nierbeck
wrote:
> Hi Tom,
>
> I'm not sure what hap
.
> I just pushed the changes and deployed the snapshot to the ops4j snapshot
> repo.
>
> regards, Achim
>
> 2015-07-30 0:02 GMT+02:00 Tom Barber :
>
>> Boo, actually I resolved that weirdness, that was due to me overriding
>> the default classpath, but when it starts
Okay gang,
I've tried 0.13.0-SNAPSHOT and I still can't for the life of me figure out
why I don't get my dependency injected.
Here is a stripped out version: https://github.com/buggtb/broken-cdi-example
I'm sure its something obvious but I can't figure it out.
Thanks
Thanks Andreas,
That was a hangover from when I tried it without an interface.
I've checked it and its still not firing.
Tom
On Thu, Jul 30, 2015 at 11:54 AM, Andreas Kuhtz
wrote:
> Hi,
>
> Might be a problem of injecting the impl instead of the interface in
> Fi
t.
Anyway, the get works and responds correctly with my injected CDI object,
the Web socket endpoint still bombs with an NPE. I'm gonna guess its some
weird Web Socket classloading issue, but I have absolutely no clue.
tom
On Thu, Jul 30, 2015 at 12:03 PM, Tom Barber
wrote:
> Thanks And
Thanks Jens
When I figured it wasn't CDI at complete fault I went googling and came
across a bunch of similar stuff, which is nuts. If you want to run
websockets and have some system beans, how on earth do you communicate with
them?! :)
Tom
On Thu, Jul 30, 2015 at 3:00 PM, Jens J Parapp
That said, I do find plenty of posts where they say it does work:
For example:
http://stackoverflow.com/questions/30332043/inject-an-application-scoped-managed-bean-in-a-websocket
On Thu, Jul 30, 2015 at 3:24 PM, Tom Barber wrote:
> Thanks Jens
>
> When I figured it wasn't C
#x27;t managed by blueprint or anything anyone got any
good ideas as to how to get the valid object?
Code here:
https://github.com/buggtb/broken-cdi-example/blob/master/src/main/java/com/mytool/filemanager/websocket/FileManagerEndpoint.java#L49
Thanks
Tom
On Thu, Jul 30, 2015 at 4:05 PM, Tom Barber
Yeah I had one in there as well. CDI does run by there is a disconnect
between websockets and CDI that seems to be a blocker at the moment.
Tom
On 30 Jul 2015 18:21, "Christian Schneider" wrote:
> Your beans.xml should be in src/main/resources/META-INF
>
> Christian
> Am
Cancel that, in my first test I must have been running the wrong jar and
not casting to the interface... doh
good news, it all seems to work(after 2 days of head scratching)
Thanks guys, your interfaces rock even if the spec doesn't!
Tom
On Thu, Jul 30, 2015 at 5:07 PM, Tom Barber
Haha! I didn't see that one yesterday. Whoop, but late though :)
https://themagicaltrout.wordpress.com/2015/07/30/accessing-your-beans-in-a-serviceendpoint-class-using-apache-karaf/
this late night blog rambling explains my current solution, although CDI
would be nicer.
Thanks Andreas.
To
You need *user*-unsubscr...@karaf.apache.org I think.
Tom
On Mon, Sep 21, 2015 at 10:15 AM, Milan Tomic wrote:
> unsubscribe
>
>
good ideas as to how to bootstrap Cellar.
I looked at the Cellar ITests but they use a "manual" installation of
Cellar not a boot time spin up.
I also started the PAX Exam test instance and all the bundles seemed to be
installed and running normally when I start it from ./bin/karaf.
Thanks
Tom
Thanks Achim I thought I shipped most of them I'll double check.
Tom
On Mon, Dec 14, 2015 at 7:17 PM, Achim Nierbeck
wrote:
> Hi,
>
> just recently I discovered that a custom distribution just using
> featuresBoot is lacking certain libs, which a std.
> Karaf distribution
error already exists in the logs at
this point.
Weird how it works in manual mode.
Tom
On Mon, Dec 14, 2015 at 7:29 PM, Tom Barber wrote:
> Thanks Achim I thought I shipped most of them I'll double check.
>
> Tom
>
> On Mon, Dec 14, 2015 at 7:17 PM, Achim Nierbeck
>
Transpires I was pulling in javax.inject which it was taking a deep
disliking to.
You live and learn. My one bug bear with OSGI is the amount of completely
random or unrelated error messages that make debugging harder than it could
be.
Anyway, mystery solved.
Thanks
Tom
On Mon, Dec 14, 2015
ect a lot are caused by side effects of the dynamic nature
of OSGI so there is probably not a great deal that can be done.
Thanks for the help Achim.
Tom
On Tue, Dec 15, 2015 at 7:23 AM, Achim Nierbeck
wrote:
> sorry to hear you had a hard time,
> but I think with Pax-Exam we have some
1 - 100 of 150 matches
Mail list logo
