Hi Tony,
Le 06/11/2018 à 21:12, tony mancill a écrit :
> XJC="java -cp
> /usr/share/java/xml-resolver.jar:/usr/share/java/jaxb-api.jar:/usr/share/java/jaxb-core.jar:/usr/share/java/jaxb-impl.jar:/usr/share/java/jaxb-jxc.jar:/usr/share/java/jaxb-xjc.jar
> -jar /usr/share/java/jaxb-xjc.jar"
>
>
On Thu, Nov 01, 2018 at 02:22:26PM +0100, Emmanuel Bourg wrote:
> On 01/11/2018 01:54, tony mancill wrote:
>
> > I am definitely open to (and appreciative of) your suggestions.
>
> Hi Tony, even if the jaxb package doesn't yet provide the xjc executable
> (#905357), you can invoke it with:
>
>
On 01/11/2018 01:54, tony mancill wrote:
> I am definitely open to (and appreciative of) your suggestions.
Hi Tony, even if the jaxb package doesn't yet provide the xjc executable
(#905357), you can invoke it with:
java -jar /usr/share/java/jaxb-xjc.jar
Emmanuel Bourg
On Tue, Oct 30, 2018 at 12:31:29PM +0100, Markus Koschany wrote:
> Am 30.10.18 um 01:15 schrieb Emmanuel Bourg:
> > Le 30/10/2018 à 00:41, gregor herrmann a écrit :
> >
> >> I guess we need to make sure that we build with openjdk-8.
> >> (You know this better than me but I seem to remember that th
Am 30.10.18 um 01:15 schrieb Emmanuel Bourg:
> Le 30/10/2018 à 00:41, gregor herrmann a écrit :
>
>> I guess we need to make sure that we build with openjdk-8.
>> (You know this better than me but I seem to remember that the plan
>> was to keep openjdk-8 in buster for building packages?)
>
> No p
Le 30/10/2018 à 00:41, gregor herrmann a écrit :
> I guess we need to make sure that we build with openjdk-8.
> (You know this better than me but I seem to remember that the plan
> was to keep openjdk-8 in buster for building packages?)
No please don't built with openjdk-8 if there is a workaroun
On Mon, 29 Oct 2018 16:33:54 -0700, tony mancill wrote:
> On Mon, Oct 29, 2018 at 11:44:36PM +0100, Emmanuel Bourg wrote:
> > jabref should no longer use the java.se.ee module, it was a temporary
> > module in Java 9 & 10 now removed in Java 11. jabref should add jaxb to
> > its classpath instead.
On Mon, Oct 29, 2018 at 11:44:36PM +0100, Emmanuel Bourg wrote:
> Le 29/10/2018 à 13:54, gregor herrmann a écrit :
>
> > Now that openjdk 11 is the default, jabref won't start without some
> > help:
> >
> > % jabref
> > Error occurred during initialization of boot layer
> > java.lang.module.FindE
Le 29/10/2018 à 13:54, gregor herrmann a écrit :
> Now that openjdk 11 is the default, jabref won't start without some
> help:
>
> % jabref
> Error occurred during initialization of boot layer
> java.lang.module.FindException: Module java.se.ee not found
jabref should no longer use the java.se.e
Control: tag -1 + ftbfs
On Mon, 29 Oct 2018 13:54:26 +0100, gregor herrmann wrote:
> Package: jabref
> Version: 3.8.2+ds-7
> Severity: important
>
> Now that openjdk 11 is the default, jabref won't start without some
> help:
>
> % jabref
> Error occurred during initialization of boot layer
> ja
Package: jabref
Version: 3.8.2+ds-7
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Now that openjdk 11 is the default, jabref won't start without some
help:
% jabref
Error occurred during initialization of boot layer
java.lang.module.FindException: Module java.se.ee not foun
11 matches
Mail list logo
