-----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 libjpf-java_1.5.1+dfsg-1_all.deb .
$ jar tvf usr/share/java/jpf.jar | grep jpf.properties
1098 Sun Dec 17 11:39:16 PST 2006 org/java/plugin/standard/jpf.properties
And the properties file is in a location that is resolved at by the classloader
at run time, as reported by the log4j output at DEBUG level when I run the
JPFTry test harness:
DEBUG [21:57:23] [main] (org.java.plugin.ObjectFactory::loadProperties:168) - no
jpf.properties file found in ${java.home}/lib
(/usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/jpf.properties) nor in CLASSPATH,
using standard properties
DEBUG [21:57:23] [main] (org.java.plugin.ObjectFactory::loadProperties:179) -
loaded jpf.properties from
jar:file:/usr/share/java/jpf.jar!/org/java/plugin/standard/jpf.properties
Finally, according to the jpf.properties file distributed with jpf, all of the
parameters in the file are optional.
Therefore, unless osmosis needs to override the default settings distributed
with JPF, the Debian-distributed jar should function as desired. Going back to
the original bug report, it's natural for log4j to emit warnings when it is
initialized and no log4j.properties is present, so I don't believe there is a
bug related to that. Would it be possible for osmosis to include a
log4j.properties file?
Cheers,
Tony
On 05/24/2010 09:48 AM, gregor herrmann wrote:
> 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 jpf.properties file, but the Debian one not.
>
> Good catch.
>
> Actually the libjpf-java source package contains
> source/org/java/plugin/standard/jpf.properties.
>
>> If so, then the second question is whether it is customary for projects
>> using JPF to distribute a jpf.properties, or whether they distribute one
>> only when they need to (and, thus, it's jpf's responsibility to have one
>> default fallback in order not to emit warning when one is not available).
>
> Amd where to put this file.
>
> Let's hope Tony has an answer :)
>
>
> Cheers,
> gregor
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkwMfd8ACgkQpdwBkPlyvgMSzwCZAZzok1gz4eHDkvaWkgV62rnF
R3wAn0WWnMjyC3O8Qla/QPTNkAFLIdz4
=Z4rN
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
