Thanks
-D
-- Forwarded message --
From: Dan Tran (JIRA)
Date: Sun, May 19, 2013 at 12:37 PM
Subject: [jira] [Commented] (KARAF-2003) Interrupt a running command in
shell
To: iss...@karaf.apache.org
[
https://issues.apache.org/jira/browse/KARAF-2003?page=com.atlassian.jira.
Hi Guillaume,
for the case of opensaml I think the real solution is to make the
dependency to xmlsec non optional.
Freeman already solved this. With my patch I did not yet change the
start levels but I hope to have all
wss4j bundles at the same start level 30.
I started this thread to discuss
The first rule when using start levels is "don't use them". When they are
*necessary*, it means the bundles misbehave, so if there's something to
explain to the users, that's really this rule (which does not prevent users
to actually use them, but this decision need to be taken wisely).
In the CX
It will be no immediate improvement but it will give us a clear concept
how to use start levels.
So I hope that people do not simply introduce new start levels without
checking the concept.
There is also a "side effect". I am currently building a CXF distro
based on a P2 Repository for a proje
I'm with Guillaume here.
Also about the duplicated bundles, as we have OBR resolver already, which can
prevent to install redundant bundles. And although some bundles are duplicated
in different features, I'd see features are more self-contained and some
features from cxf features.xml are used
Agree, it doesn't have impact to change the log level to use "simple"
ones, but I don't see a big value.
Regards
JB
On 05/23/2013 11:42 AM, Guillaume Nodet wrote:
Fwiw, having a more fine grained start level helps reducing the log
verbosity at start time and may slightly help with performance
Fwiw, having a more fine grained start level helps reducing the log
verbosity at start time and may slightly help with performance too. The
reason is that a correct start order will result in service dependencies
being satisfied correctly for most bundles, thus not having to wait until
those are s
Hi Christian,
I just looked through that feature file, since you need either the
http-whiteboard feature or the jetty feature for it to run, are you sure
about all those dependencies?
Cause some of them like the activation-api should already be inlcuded by
pax-jetty feature, no?
regards, Achim
Github user stephane-deraco closed the pull request at:
https://github.com/apache/karaf/pull/4
+1 to limit the start levels.
Regards
JB
On 05/23/2013 10:21 AM, Christian Schneider wrote:
I am currently working on:
https://issues.apache.org/jira/browse/CXF-5030
It seems that we use an incorrect start level and order for the xmlsec
dependency. I have just committed the fix for this.
Whil
I am currently working on:
https://issues.apache.org/jira/browse/CXF-5030
It seems that we use an incorrect start level and order for the xmlsec
dependency. I have just committed the fix for this.
While correcting this I found that we have a lot of different start
levels. I am quite sure we s
11 matches
Mail list logo
