> Problems were not finished: Josm didn't compile, because it now relies
> on classes such as sun.net.www.protocol.http.Handler and
> sun.net.www.protocol.http.HttpURLConnection, which are present in
> official Sun compiler, but not in GCJ, which we are using.
Can we convince the josm developer(s) to avoid thus SUN specific API?
> So, the question is: should we move to Sun's javac, or do you know
> some workaround for this? I've just updated josm-plugins (which
> can't be build right now, because it depends on too recent josm) and
> josm (which fails to build for the reason I just underlined) to SVN.
I believe we should stick with the free compilers, and ask debian-java
for clues on a workaround and the josm developers to avoid using SUN
specific APIs. This might change when the new Java version make it to
unstable (is the SUN API part of that version?), but until then, we
should try our best to keep josm part of Debian/main.
Pkg-grass-devel mailing list