I just want to point people at
http://njbartlett.name/2011/02/09/uses-constraints.html because I
think the last part is clearly related to the discussion we had around
which packages should the system bundle export, mostly for the CXF
deployment issue. It doesn't solve our problem, but it's
commons-log is not deployed.
As it works with value = slf4j instead of log4, openjpa can be
configured to use log appender. So we do not to modify for the moment
pax-logging
On Wed, Feb 9, 2011 at 6:32 PM, Guillaume Nodet gno...@gmail.com wrote:
Why isn't the package wired to pax-logging ?
I'm not sure but does issues.apache.org automatically process ansers to
iss...@karaf.apache.org? If not I think it would be great to set the reply-to
address to dev@karaf.apache.org.
WDYT?
kind regards,
andreas
pgp2REvu0We1w.pgp
Description: PGP signature
I've just seen the following issue in our JIRA. The problem is that there is no
version 1.0.0, but rather ${karaf.version} :). How do we like to handle this
problem? Set ${project.version} vars into the docu and pre-process them or
rather use ${karaf.version} as text-tag making this situation
+1
AFAIR, in ServiceMix, Jira e-mails are also sent to
d...@servicemix.apache.org.
Regards
JB
On 02/11/2011 08:26 AM, Andreas Pieber wrote:
I'm not sure but does issues.apache.org automatically process ansers to
iss...@karaf.apache.org? If not I think it would be great to set the reply-to
I'm not sure to follow you.
What do you mean ?
Regards
JB
On 02/11/2011 08:28 AM, Andreas Pieber wrote:
I've just seen the following issue in our JIRA. The problem is that there is no
version 1.0.0, but rather ${karaf.version} :). How do we like to handle this
problem? Set ${project.version}
This issue is for the old manual which isn't svn based, only
confluence, so we can't really post-process it.
For the new one, we could easily reuse maven to filter the sources
before the html transformation I think.
On Fri, Feb 11, 2011 at 08:28, Andreas Pieber anpie...@gmail.com wrote:
I've
mhm, from my point of view we can go ahead with this release. IMHO we've
included a bunch of fixes and there are no further critical fixes on the list
-- +1 for going ahead
kind regards,
andreas
On Tue, Feb 08, 2011 at 06:56:47PM -0330, Jamie G. wrote:
Hi,
Now that we have Karaf 2.2.0
Ah oky :)
It's related to the old manual, it's not really possible to fix that :/
For the new one, maven resources filtering should do the job :)
Regards
JB
On 02/11/2011 08:36 AM, Andreas Pieber wrote:
KARAF-456 mentioned the problem that no 1.0.0 version of
org.apache.karaf.shell.console
ok, as I've expected :) I'll rename KARAF-456 and assign it to 2.x and 3.x
thanks and kind regards,
andreas
On Fri, Feb 11, 2011 at 08:38:46AM +0100, Guillaume Nodet wrote:
This issue is for the old manual which isn't svn based, only
confluence, so we can't really post-process it.
For the new
10 matches
Mail list logo
