Bug#679616: Latest LTS is now 1.466.1

2012-08-23 Thread YOSHINO Yoshihito
Hi, Version 1.466.1 is released as LTS on 2012/07/23: http://jenkins-ci.org/changelog-stable Please consider packaging this (or newer stable?) version. Regards, -- YOSHINO Yoshihito __ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin

Bug#517035: tomcat6: Default HTTP connector port should not be 8080

2009-02-25 Thread YOSHINO Yoshihito
Subject: tomcat6: Default HTTP connector port should not be 8080 Source: tomcat6 Version: 6.0.18-2 Severity: important WWW caching service uses port 8080, so tomcat6 should use another port as a default. -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstab

Bug#517035: tomcat6: Default HTTP connector port should not be 8080

2009-03-03 Thread YOSHINO Yoshihito
tomcat5.5 to coexist. # So do I in regard to the shutdown control port. Port 8005 is used by both tomcat6 and tomcat5.5 as default... -- YOSHINO Yoshihito ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.al

Bug#858876: libjna-jni: causes NoClassDefFoundError

2017-03-27 Thread YOSHINO Yoshihito
tch.so -> libjnidispatch.system.so fixes this error. Regards, -- YOSHINO Yoshihito -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable') Architecture: i386 (x86_64) Foreign Archite

Bug#858876: libjna-jni: causes NoClassDefFoundError

2017-03-28 Thread YOSHINO Yoshihito
Hi Emmanuel, On Tue, Mar 28, 2017 at 4:47 PM, Emmanuel Bourg wrote: > Thank you for the report. The symlink was in the same directory? What > JRE did you use? Yes, in the same directory. I use openjdk-8-jre:i386. Regards, -- YOSHINO Yoshihito __ This is the maintainer address of De

Bug#858876: libjna-jni: causes NoClassDefFoundError

2017-04-17 Thread YOSHINO Yoshihito
Package: libjna-jni Followup-For: Bug #858876 Control: reopen -1 Dear Maintainer, Sorry for the delay. I have upgraded this package, while this error still persists. Exactly the same error message appears in the netbeans log. Creating the symlink works around this error. Regards, -- YOSHINO