On Sun, 17 Jun 2018 21:47:09 -0700, tony mancill wrote:
> For the time-being, I propose that we check the java version directly in
> the jabref wrapper script like so:
>
> JAVA_VERSION=$(run_java -version 2>&1 | grep ' version ' | awk '{print $3}')
> if ! ( echo "$JAVA_VERSION" | grep -q '1.8.0'
On Sat, Jun 02, 2018 at 07:06:56PM +0200, gregor herrmann wrote:
> On Sat, 02 Jun 2018 09:59:55 -0700, tony mancill wrote:
>
> > What I think we should do is try to detect if the jabref-wrapper is
> > being invoked with java8 and clear the options required for the java9
> > workaround.
> > If that
On Sat, 02 Jun 2018 09:59:55 -0700, tony mancill wrote:
> > Looking at the recent evolution of debian/control, I note that
> > there's no default-jre or openjdk-* in Depends any more.
> >
> > The recent changes were:
> > "default-jre (>= 2:1.8) | java8-runtime" → "openjdk-8-jre" → ""
> >
> > I g
On Tue, May 29, 2018 at 04:40:50PM +0200, gregor herrmann wrote:
> On Tue, 29 May 2018 14:41:14 +0200, Andreas Gocht wrote:
>
> > I recently tried to start JabRef using my default Java8 version. I got the
> > following error:
> >
> > Unrecognized option: --add-modules=java.se.ee
> > Error: Could
On Tue, 29 May 2018 14:41:14 +0200, Andreas Gocht wrote:
> I recently tried to start JabRef using my default Java8 version. I got the
> following error:
>
> Unrecognized option: --add-modules=java.se.ee
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred.
Package: jabref
Version: 3.8.2+ds-5
Severity: normal
Dear Maintainer,
I recently tried to start JabRef using my default Java8 version. I got the
following error:
Unrecognized option: --add-modules=java.se.ee
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred
6 matches
Mail list logo
