I found the solution. It had nothing to do with ssh itself.
We have build a custom distribution and put a custom /bin/karaf file in
filtered-resources. Our build server builds this custom distribution and
installs it on an external system.
The problem was, that the build server replaced the
Thanks for the update.
As I wasn't able to reproduce your issue, I suspected something related
to your environment ;)
Regards
JB
On 07/15/2014 09:53 AM, sprinz wrote:
I found the solution. It had nothing to do with ssh itself.
We have build a custom distribution and put a custom /bin/karaf
Hi JB,
Thanks, I used LogService, it's works.
Thanks for your help.
Regards
Xav
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-2-3-5-Set-the-log-Level-programmatically-tp4034161p4034222.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Hi Xav,
no problem, we are dedicated for you guys ;)
Regards
JB
On 07/15/2014 12:15 PM, xav wrote:
Hi JB,
Thanks, I used LogService, it's works.
Thanks for your help.
Regards
Xav
--
View this message in context:
Hi all,
Just wondering whether this is possible. I'm using a Karaf feature at
runtime and want to make sure that at build time I'm picking up all
the dependencies exactly like they are in the feature (i.e. same
bundles at compile time as at runtime).
So I was wondering is there a way to use a
Hi David,
the features-maven-plugin/karaf-maven-plugin, with the
add-features-to-repo resolves the features and populate a system repo
with bundles.
Regards
JB
On 07/15/2014 06:46 PM, David Bosschaert wrote:
Hi all,
Just wondering whether this is possible. I'm using a Karaf feature at
Thanks JB!
This is useful, but it doesn't really put the features in my maven
dependency tree, AFAICS.
What I'm looking for is a way to simply refer to a Karaf feature
instead of specifying dependency entries in my pom. So that I'm sure
that what I'm building with maven has the same dependencies
Oh ok. You can create a kar based on the features and reference the kar
in dependency/.
Not sure it will work exactly as you expect.
Regards
JB
On 07/15/2014 07:15 PM, David Bosschaert wrote:
Thanks JB!
This is useful, but it doesn't really put the features in my maven
dependency tree,
Thanks for the confirmation, JB.
I had newbishly/foolishly assumed that any jar dropped in the
$KARAF_HOME/lib directory would be auto-magically added to the classpath.
One of the things that tripped me up was the less-than-informative message:
Exception instantiating lock class..., which I was
Hi David,
I don't know if this if helpful for you:
In Servicemix (last checked with SMX 4.5) the features are generated
inside a separate module based on declarations in dependencyManagement
section of the pom. I use this to import the pom of this module into
my project to gain access to all
Hi David,
A good thing could be to declare all your feature's dependencies on the
feature's pom with an exclusion*/ on them.
Then, you can reference that features pom on your business module
Example:
* In the feature's pom
artIdfeatArtId/artId
depMngmt
depcom.mycom:mydep:${myversion}
excl*/excl
11 matches
Mail list logo