![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Amit Gupta <amit.gupta221@gmail.com> | |
| Wed, 10 Feb 2010 13:37:36 +0000 (14:37 +0100) | ||
| committer | Florian Forster <octo@huhu.verplant.org> | |
| Wed, 10 Feb 2010 13:48:33 +0000 (14:48 +0100) | ||
| commit | c983405b9f18cce28d6301124a5426e53adc63b2 | |
| tree | df643843586c25cae41144049dad2a55eb4a2fc0 | tree | snapshot |
| parent | 93c2cad7632046ca9fb23b23056e01db57f874ee | commit | diff |
Build system: Put Java class files into a .jar file.
Hi,
I was wondering why the java plugin api class files are published under
share/collectd/java. Ideally, a java-plugin.jar file containing all the class
files should get published rather than the individual class files.
Additionally, the jar files IMO should get published to the lib directory where
the so files are sitting rather than the share directory.
Same holds true for jmx class files as well (probably jmx.jar?).
I could work on this if everyone is okay with it.
Regards
Amit
Hi,
I was wondering why the java plugin api class files are published under
share/collectd/java. Ideally, a java-plugin.jar file containing all the class
files should get published rather than the individual class files.
Additionally, the jar files IMO should get published to the lib directory where
the so files are sitting rather than the share directory.
Same holds true for jmx class files as well (probably jmx.jar?).
I could work on this if everyone is okay with it.
Regards
Amit
| bindings/java/Makefile.am | diff | blob | history | |
| configure.in | diff | blob | history | |
| src/collectd.conf.in | diff | blob | history |