Hi,
I've solved that on my machine.
You can try the following:
Create the file /etc/osmosis/log4j.properties with a simple line (file
attached)
log4j.logger.org.java.plugin=WARN
I've tried an empty file, because log4j is configured by osmosis (or a
library osmosis uses), but it doesn't work
reassign 579206 osmosis
thanks
Hi all.
Il 07/06/2010 07:04, tony mancill ha scritto:
Hi Giovanni, Gregor:
I've been looking into this, but I don't think there's any issue with the
libjpf-java package distributed in Debian.
Ok, then I'm reassigning the bug to my package.
Finally,
On Sun, 06 Jun 2010 22:04:39 -0700, tony mancill wrote:
I've been looking into this, but I don't think there's any issue with the
libjpf-java package distributed in Debian.
Thanks Tony for this thorough analysis!
Cheers,
gregor
--
.''`. http://info.comodo.priv.at/ -- GPG key IDs:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Giovanni, Gregor:
I've been looking into this, but I don't think there's any issue with the
libjpf-java package distributed in Debian.
First, the Debian jpf.jar does contain the default jpf.properties file:
$ dget libjpf-java
$ dpkg -x
On Mon, May 24, 2010 at 05:11, tony mancill tmanc...@debian.org wrote:
I'm not sure what your minimal test case is meant to exhibit. The warnings
you're seeing from log4j are normal warnings you see when there isn't a
log4j.properties file. That is, log4j is simply letting us know that a
Hi Tony.
Il 24/05/2010 07:11, tony mancill ha scritto:
I'm not sure what your minimal test case is meant to exhibit. The warnings
you're seeing from log4j are normal warnings you see when there isn't a
log4j.properties file. That is, log4j is simply letting us know that a
component
On Mon, 24 May 2010 18:10:42 +0200, Giovanni Mascellani wrote:
Thanks for the info, I didn't know this. Anyway, it's not entirely clear
to me whom is the responsibility to furnish the jpf.properties. I
noticed that the jpf jarball distributed with the osmosis binary
tarball[1] contains a
On 05/18/2010 08:50 AM, Giovanni Mascellani wrote:
reassing 579206 libjpf-java
thanks
Hi all.
Hi Gregor and Tony, I'm reassigning a bug to libjpf-java. The bug is
rather minor and the log is really short. Please, let me know if you
don't agree about the reassignment! :-)
Il 27/04/2010
reassing 579206 libjpf-java
thanks
Hi all.
Hi Gregor and Tony, I'm reassigning a bug to libjpf-java. The bug is
rather minor and the log is really short. Please, let me know if you
don't agree about the reassignment! :-)
Il 27/04/2010 10:37, Giovanni Mascellani ha scritto:
Il 26/04/2010 10:58,
tag 579206 + confirmed
thanks
Hi.
Il 26/04/2010 10:58, v.nix.is ha scritto:
After upgrading osmosis I get output like this from cron jobs using it:
log4j:WARN No appenders could be found for logger
(org.java.plugin.ObjectFactory).
log4j:WARN Please initialize the log4j system
Package: osmosis
Version: 0.34+ds1-1
Severity: minor
After upgrading osmosis I get output like this from cron jobs using it:
log4j:WARN No appenders could be found for logger
(org.java.plugin.ObjectFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN No
11 matches
Mail list logo
