Hi Dan:
I have to set the Mac OS X port aside for a moment -- customer issues come first today :).
I'm having some problems with the way the javax.usb.properties file is packaged in the Linux RPM files, and I think it needs to be changed. The problem with it is that it's written into the /opt tree, and is referenced via a CLASSPATH entry to its enclosing directory.
This is all well and good -- so long as users aren't starting a javax.usb dependant application (like the jSyncManager) using java's "-jar" parameter. The "-jar" parameter unfortunately completely bypasses and invalidates whatever is in the CLASSPATH environment variable.
The javax.usb JARs themselves are found due to the copy placed in the jre/lib/ext directory, but unfortunately this doesn't work for property files. Of course, trying to instantiate javax.usb results in an exception stating that the property file can't be found.
I've come up with a temporary work-around here by simply using the JAR tool to add the property file to the Linux RI JAR far. Is there any reason why this isn't the default? As you can't use the Linux RI without this file, IMO adding it with the proper Linux settings to the Linux RI JAR file makes some sense (although at the same time, this does make it somewhat more onerous upon the user if that have to edit any of the default parameters in that file).
I'm thinking that it might be useful to have a "default" version of the properties file in the Linux RI JAR under a different name, which can be loaded if the user-modifiable properties file (javax.usb.properties) can't be loaded for some reason. The current setup prevents applications using the API from being launchable JARs, unless each application re-bundles javax.usb itself.
Thoughts? Ideas? There has to be a better way to handle this file -- while not really your fault, it seems unfortunate to have to tell people they can't launch an application via the -jar parameter because of a property file :).
As an aside, with the latest javax.usb for Linux implementation, I'm getting an "Unable to log: JavaxUsb class has no log method." error message when running on FC3 with Sun JDK v1.5.0. Any thoughts as to why?
Brad BARCLAY, Lead Developer & Project Administrator, The jSyncManager Project.
=-=-=-=-=-=-=-=-=-= From the Mac OS X Desktop of Brad BARCLAY E-Mail: [EMAIL PROTECTED] Web: http://www.jsyncmanager.org
smime.p7s
Description: S/MIME cryptographic signature
