Am 03.12.2017 um 13:29 schrieb Adrian Bunk:
> Package: libjaxb-java
> Version: 2.3.0-3
> Severity: serious
> Control: affects -1 src:eclipselink

Hi,

Thanks for reporting. I had a look at this but I can't find the mistake
in libjaxb-java. The difference between 2.3.0-2 and 2.3.0-3 is that we
use absolute classpaths now and this works for Netbeans for example. [1]
I can't see that I made a typo somewhere. So my guess is something
curious is going on with eclipselink's build system. When I add the
necessary dependencies to debian/classpath-debian it works again but it
really should not make any difference in this case whether the classpath
for usr/share/java/jaxb-xjc.jar uses relative or absolute paths.

It would be nice if someone else had a look at this because I might have
overlooked something but it doesn't look like a bug in libjaxb-java.

Markus

[1]
https://anonscm.debian.org/cgit/pkg-java/jaxb.git/commit/?id=0c76b6c3fd1430f4fdc07d13af1a42a593a2319d

Attachment: signature.asc
Description: OpenPGP digital signature

__
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.

Reply via email to