Package: jsvc
Version: 1.0.15-6
Severity: minor
Tags: upstream
Before 1.0.15, jsvc did not change working directory in any way, so the way to
set the cwd for an application was just to cd to the proper directory before
calling jsvc.
Starting with 1.0.15, the -cwd option was added, which is indeed a useful
addition.
However, 1.0.15 now *always* changes directory, with / as the default. This
means that -cwd now basically has to be used if a specific cwd is needed. Of
course, -cwd is an invalid option with versions before 1.0.15, so now it's
impossible to make an init script that works with both older and newer jsvc
setups.
It's not clear to me why leaving the cwd as is if -cwd isn't used wasn't kept.
As an extra annoyance, -version doesn't work without also setting seemingly
unrelated options, so adding code to set -cwd based on jsvc version is harder
than it should be.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages jsvc depends on:
ii libc6 2.19-12
ii libcommons-daemon-java 1.0.15-5.1
Versions of packages jsvc recommends:
ii default-jre-headless [java2-runtime-headless]2:1.7-52
ii openjdk-7-jre-headless [java2-runtime-headless] 7u71-2.5.3-1
jsvc suggests no packages.
-- no debconf information
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers.
Please use
debian-j...@lists.debian.org for discussions and questions.
