I noticed this very old bug and wondered if it is still relevant.
Currently there is a jarwrapper package that uses binfmt-support to
allow jar-files to be executed.
=20
Almost. It's probably more use to most people than my javawrapper
implementation is, I agree.
=20
When I wrote javawrapper, it was in the early days of Java and it was
still common enough to just build a pile of .class files rather than a
.jar file. I wrote javawrapper because I was fed up with concocting th=
e
correct syntax to get the Java interpreter to start with a given .class=
file. This still seems as though it could be useful in some situations=
=2E
=20
CCing the javatools maintainers; would it be possible to merge some of
the functionality of
http://www.chiark.greenend.org.uk/~cjwatson/code/javawrapper/javawrappe=
r-1.0.tar.gz
into jarwrapper?
=20
Thanks,
=20
Hi again
Sorry for the late reply.
It is possible add this feature to jarwrapper, but I am not sure that it
make sense these days. Personally I hardly ever run a class directly;
either my IDE start the program for me or I bundle it into a jar first.
On a related note, the Debian Java Policy requires that all class
files are bundled into jar files, so it will not add any value for Java
packaging.
I do not mind supporting this if our users actually want this feature.
~Niels
signature.asc
Description: OpenPGP digital signature
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please
use
debian-j...@lists.debian.org for discussions and questions.
