Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

2018-04-06 Thread gregor herrmann 
Control: tag -1 + pending

On Fri, 06 Apr 2018 11:13:02 +0200, Emmanuel Bourg wrote:

> > Should we reassign this bug to liblog4j2-java (+ affects jabref)? I
> > suppose the problem doesn't exclusively hit jabref?
> I've uploaded liblog4j2-java/2.10.0-2 that should work with Java 8.
> Could you give it a try?

That's excellent news, thank you!

Let me try ...

During build I see some scary output:

Malformed class file [module-info.class] in jar 
[/usr/share/maven-repo/org/apache/logging/log4j/log4j-api/debian/log4j-api-debian.jar]
 found on classpath, which means that this class will cause a compile error if 
referenced in a source file. Gradle 5.0 will no longer allow malformed classes 
on compile classpath.
at 
org.gradle.api.internal.changedetection.state.JvmClassHasher.visit(JvmClassHasher.java:154)
at 
org.gradle.api.internal.changedetection.state.JvmClassHasher.hashJarFile(JvmClassHasher.java:122)
at 
org.gradle.api.internal.changedetection.state.DefaultCompileClasspathSnapshotter.normaliseFileElement(DefaultCompileClasspathSnapshotter.java:75)
at 
org.gradle.api.internal.changedetection.state.AbstractFileCollectionSnapshotter$FileCollectionVisitorImpl.visitCollection(AbstractFileCollectionSnapshotter.java:144)
at 
org.gradle.api.internal.file.AbstractFileCollection.visitRootElements(AbstractFileCollection.java:234)
at 
org.gradle.api.internal.file.CompositeFileCollection.visitRootElements(CompositeFileCollection.java:185)
at 
org.gradle.api.internal.changedetection.state.AbstractFileCollectionSnapshotter.snapshot(AbstractFileCollectionSnapshotter.java:71)
at 
org.gradle.api.internal.changedetection.rules.AbstractNamedFileSnapshotTaskStateChanges.buildSnapshots(AbstractNamedFileSnapshotTaskStateChanges.java:87)
at 
org.gradle.api.internal.changedetection.rules.AbstractNamedFileSnapshotTaskStateChanges.(AbstractNamedFileSnapshotTaskStateChanges.java:54)
at 
org.gradle.api.internal.changedetection.rules.InputFilesTaskStateChanges.(InputFilesTaskStateChanges.java:28)
at 
org.gradle.api.internal.changedetection.rules.TaskUpToDateState.(TaskUpToDateState.java:55)
at 
org.gradle.api.internal.changedetection.changes.DefaultTaskArtifactStateRepository$TaskArtifactStateImpl.getStates(DefaultTaskArtifactStateRepository.java:164)
at 
org.gradle.api.internal.changedetection.changes.DefaultTaskArtifactStateRepository$TaskArtifactStateImpl.isUpToDate(DefaultTaskArtifactStateRepository.java:79)
at 
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:51)
at 
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at 
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:46)
at 
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:51)
at 
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at 
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.execute(DefaultTaskGraphExecuter.java:236)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.execute(DefaultTaskGraphExecuter.java:228)
at org.gradle.internal.Transformers$4.transform(Transformers.java:169)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:61)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:228)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:215)
at 
org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:77)
at 
org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:58)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at 
org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:46)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at

Processed: Re: Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

2018-04-06 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 + pending
Bug #893251 [jabref] jabref: doesn't start with liblog4j2-java 2.10.0-1
Bug #894106 [jabref] jabref: fails to start with java-8-openjdk-amd64
Added tag(s) pending.
Added tag(s) pending.

-- 
893251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893251
894106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

2018-04-06 Thread Emmanuel Bourg 
On Tue, 20 Mar 2018 23:32:26 +0100 gregor herrmann wrote:

> > That said, so far I'm not able to build a liblog4j2-java from the
> > 2.10.0-1 source package that will play nicely with jabref, but I'll keep
> > looking at that and other options (aside from suggesting that we start
> > recommending a stretch chroot for jabref...)
> 
> Thanks. And I'm optimistic that you'll succeed in the end :)
> 
> Should we reassign this bug to liblog4j2-java (+ affects jabref)? I
> suppose the problem doesn't exclusively hit jabref?

I've uploaded liblog4j2-java/2.10.0-2 that should work with Java 8.
Could you give it a try?

Emmanuel Bourg

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

2018-03-20 Thread gregor herrmann 
On Mon, 19 Mar 2018 22:40:47 -0700, tony mancill wrote:

> > Maybe that's caused by the recent update of liblog4j2-java 2.8.2-2 -> 
> > 2.10.0-1
> > Indeed, downgrading liblog4j2-java to 2.8.2-2 helps.
> > Not sure if this is a jabref problem or a liblog4j2-java issue; let's
> > hope the java experts can shed some light on this bug.
> Ouch indeed!  I'm pretty certain that this is an issue with how
> liblog4j2-java is being built for Debian.  There is some discussion of
> the issue here [1].  Basically, we need to take precautions when
> building libraries with JDK 9 that are expected to run with JDK 8
> runtimes.

Thanks for looking into this issue and for digging up this reference.
 
> That said, so far I'm not able to build a liblog4j2-java from the
> 2.10.0-1 source package that will play nicely with jabref, but I'll keep
> looking at that and other options (aside from suggesting that we start
> recommending a stretch chroot for jabref...)

Thanks. And I'm optimistic that you'll succeed in the end :)

Should we reassign this bug to liblog4j2-java (+ affects jabref)? I
suppose the problem doesn't exclusively hit jabref?
 
> [1] https://github.com/plasma-umass/doppio/issues/497


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Rebekka Bakken & Wolfgang Muthspiel: Nowhere


signature.asc
Description: Digital Signature
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

2018-03-19 Thread tony mancill 
On Sun, Mar 18, 2018 at 04:28:26PM +0100, gregor herrmann wrote:
> > > You can run
> > > JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
> > Something is wrong here. Did openjdk-8 changed a bit?
> 
> Hm ...
>  
> > $ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
> > Exception in thread "main" java.lang.NoSuchMethodError:
> > java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer; at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:292)
> > at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:303)
> > at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.closeOutputStream(OutputStreamManager.java:308)
> > at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.releaseSub(OutputStreamManager.java:137)
> > at
> > org.apache.logging.log4j.core.appender.AbstractManager.stop(AbstractManager.java:86)
> > at
> > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:142)
> > at
> > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:136)
> > at
> > org.apache.logging.log4j.core.config.AbstractConfiguration.stop(AbstractConfiguration.java:359)
> > at
> > org.apache.logging.log4j.core.AbstractLifeCycle.stop(AbstractLifeCycle.java:136)
> > at
> > org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:550)
> > at
> > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617)
> > at
> > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
> > at
> > org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
> > at
> > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:153)
> > at
> > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
> > at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
> > at
> > org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122)
> > at
> > org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
> > at
> > org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46)
> > at
> > org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
> > at
> > org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
> > at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655) at
> > net.sf.jabref.JabRefMain.(JabRefMain.java:37)
> 
> Ouch, I have to confirm that I get the same errors.
> 
> Maybe that's caused by the recent update of liblog4j2-java 2.8.2-2 -> 2.10.0-1
> 
> Indeed, downgrading liblog4j2-java to 2.8.2-2 helps.
> 
> Not sure if this is a jabref problem or a liblog4j2-java issue; let's
> hope the java experts can shed some light on this bug.

Ouch indeed!  I'm pretty certain that this is an issue with how
liblog4j2-java is being built for Debian.  There is some discussion of
the issue here [1].  Basically, we need to take precautions when
building libraries with JDK 9 that are expected to run with JDK 8
runtimes.

That said, so far I'm not able to build a liblog4j2-java from the
2.10.0-1 source package that will play nicely with jabref, but I'll keep
looking at that and other options (aside from suggesting that we start
recommending a stretch chroot for jabref...)

Cheers,
tony

[1] https://github.com/plasma-umass/doppio/issues/497


signature.asc
Description: PGP signature
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

2018-03-19 Thread c.buhtz 
Dear Gregor,

thank you very much for your fast reply.

> True, this is already reported as #890905/#893138.
> I ('m trying to) merge those two bugs.

Sorry, for reporting again. I noticed that bugs. But as a
Java-foreigner it wasn't clear for me if they address the same issue.

> You can run
> JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref

Something is wrong here. Did openjdk-8 changed a bit?

$ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
Exception in thread "main" java.lang.NoSuchMethodError:
java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer; at
org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:292)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:303)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.closeOutputStream(OutputStreamManager.java:308)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.releaseSub(OutputStreamManager.java:137)
at
org.apache.logging.log4j.core.appender.AbstractManager.stop(AbstractManager.java:86)
at
org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:142)
at
org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:136)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.stop(AbstractConfiguration.java:359)
at
org.apache.logging.log4j.core.AbstractLifeCycle.stop(AbstractLifeCycle.java:136)
at
org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:550)
at
org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617)
at
org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
at
org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:153)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
at
org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122)
at
org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
at
org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46)
at
org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
at
org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655) at
net.sf.jabref.JabRefMain.(JabRefMain.java:37)



signature.asc
Description: Digital Signature
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

2018-03-18 Thread gregor herrmann 
Control: clone 890905 -1
Control: retitle -1 jabref: doesn't start with liblog4j2-java 2.10.0-1
Control: tag -1 - patch pending

On Sun, 18 Mar 2018 13:48:56 +0100, c.bu...@posteo.jp wrote:

> Dear Gregor,
> thank you very much for your fast reply.

You're welcome.
 
> > True, this is already reported as #890905/#893138.
> > I ('m trying to) merge those two bugs.
> Sorry, for reporting again. I noticed that bugs. But as a
> Java-foreigner it wasn't clear for me if they address the same issue.

No worries.
 
> > You can run
> > JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
> Something is wrong here. Did openjdk-8 changed a bit?

Hm ...
 
> $ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
> Exception in thread "main" java.lang.NoSuchMethodError:
> java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer; at
> org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:292)
> at
> org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:303)
> at
> org.apache.logging.log4j.core.appender.OutputStreamManager.closeOutputStream(OutputStreamManager.java:308)
> at
> org.apache.logging.log4j.core.appender.OutputStreamManager.releaseSub(OutputStreamManager.java:137)
> at
> org.apache.logging.log4j.core.appender.AbstractManager.stop(AbstractManager.java:86)
> at
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:142)
> at
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:136)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.stop(AbstractConfiguration.java:359)
> at
> org.apache.logging.log4j.core.AbstractLifeCycle.stop(AbstractLifeCycle.java:136)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:550)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
> at
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:153)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
> at
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122)
> at
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
> at
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46)
> at
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
> at
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655) at
> net.sf.jabref.JabRefMain.(JabRefMain.java:37)

Ouch, I have to confirm that I get the same errors.

Maybe that's caused by the recent update of liblog4j2-java 2.8.2-2 -> 2.10.0-1

Indeed, downgrading liblog4j2-java to 2.8.2-2 helps.

Not sure if this is a jabref problem or a liblog4j2-java issue; let's
hope the java experts can shed some light on this bug.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Cat Stevens: On The Road To Find Out


signature.asc
Description: Digital Signature
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Processed (with 1 error): Re: Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

2018-03-18 Thread Debian Bug Tracking System 
Processing control commands:

> clone 890905 -1
Bug #890905 [jabref] jabref: doesn't build/run with default-jdk/-jre
Bug #893251 [jabref] jabref 3.8 is started with OpenJDK 9 instead of 8
Failed to clone 890905: Bug is marked as being merged with others. Use an 
existing clone.

> retitle -1 jabref: doesn't start with liblog4j2-java 2.10.0-1
Bug #893251 [jabref] jabref 3.8 is started with OpenJDK 9 instead of 8
Bug #890905 [jabref] jabref: doesn't build/run with default-jdk/-jre
Changed Bug title to 'jabref: doesn't start with liblog4j2-java 2.10.0-1' from 
'jabref 3.8 is started with OpenJDK 9 instead of 8'.
Changed Bug title to 'jabref: doesn't start with liblog4j2-java 2.10.0-1' from 
'jabref: doesn't build/run with default-jdk/-jre'.
> tag -1 - patch pending
Bug #893251 [jabref] jabref: doesn't start with liblog4j2-java 2.10.0-1
Bug #890905 [jabref] jabref: doesn't start with liblog4j2-java 2.10.0-1
Removed tag(s) patch and pending.
Removed tag(s) pending and patch.

-- 
890905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890905
893251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

2018-03-17 Thread gregor herrmann 
Control: forcemerge 890905 -1

On Sat, 17 Mar 2018 15:32:16 +0100, Christian Buhtz wrote:

> JabRef is currently not working. 

True, this is already reported as #890905/#893138.
I ('m trying to) merge those two bugs.

> The script in /usr/bin/jabref requires
> "java8". But this need is ignored and version 9 is used. Because of that there
> are some errors.

It's not ignored, the problem is that openjdk-9 also provides the
java8 interface ... Cf. /usr/lib/java-wrappers/jvm-list.sh
 
> I don'T know how to make the installed JabRef run again with "java8".

You can run
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Processed: Re: Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

2018-03-17 Thread Debian Bug Tracking System 
Processing control commands:

> forcemerge 890905 -1
Bug #890905 [jabref] jabref: doesn't build/run with default-jdk/-jre
Bug #893251 [jabref] jabref 3.8 is started with OpenJDK 9 instead of 8
Set Bug forwarded-to-address to 'https://github.com/JabRef/jabref/issues/2594'.
Severity set to 'serious' from 'important'
Added tag(s) upstream, patch, and pending.
Merged 890905 893251

-- 
890905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890905
893251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

2018-03-17 Thread Christian Buhtz 
Package: jabref
Version: 3.8.2+ds-2
Severity: important

Dear Maintainer,

JabRef is currently not working. The script in /usr/bin/jabref requires
"java8". But this need is ignored and version 9 is used. Because of that there
are some errors.

I don'T know how to make the installed JabRef run again with "java8".

$ DEBUG_WRAPPER=1 jabref --debug
[debug] /usr/bin/jabref: Picking up the JVM designated by the alternatives
system:
[debug] /usr/bin/jabref:   JAVA_HOME = '/usr/lib/jvm/java-9-openjdk-amd64'
[debug] /usr/bin/jabref: Found JAVA_HOME = '/usr/lib/jvm/java-9-openjdk-amd64'
[debug] /usr/bin/jabref: Found JAVA_CMD = '/usr/lib/jvm/java-9-openjdk-
amd64/bin/java'
/usr/lib/jvm/java-9-openjdk-amd64/bin/java
[warning] /usr/bin/jabref: /usr/lib/jvm/java-9-openjdk-amd64/bin/java
[debug] /usr/bin/jabref: Environment variable CLASSPATH is ''
[debug] /usr/bin/jabref: Runnning /usr/lib/jvm/java-9-openjdk-amd64/bin/java
-classpath
/usr/share/java/jabref.jar:/usr/share/java/bcprov.jar:/usr/share/java/antlr3-runtime.jar:/usr/share/java/antlr4-runtime.jar:/usr/share/java/com.android.json.jar:/usr/share/java/commons-
cli.jar:/usr/share/java/commons-codec.jar:/usr/share/java/commons-
lang3.jar:/usr/share/java/commons-
logging.jar:/usr/share/java/fontbox.jar:/usr/share/java/glazedlists.jar:/usr/share/java/guava.jar:/usr/share/java/httpasyncclient.jar:/usr/share/java/httpclient.jar:/usr/share/java/httpcore.jar:/usr/share/java/httpcore-
nio.jar:/usr/share/java/httpmime.jar:/usr/share/java/java-string-
similarity.jar:/usr/share/java/jempbox.jar:/usr/share/java/jgoodies-
common.jar:/usr/share/java/jgoodies-forms.jar:/usr/share/java/jgoodies-
looks.jar:/usr/share/java/jhlabs-
filters.jar:/usr/share/java/jsoup.jar:/usr/share/java/juh.jar:/usr/share/java/jurt.jar:/usr/share/java/log4j-api.jar:/usr/share/java/log4j-core.jar:/usr/share/java/log4j-jcl.jar:/usr/share/java/microba.jar:/usr/share/java/mysql-
connector-
java.jar:/usr/share/java/pdfbox.jar:/usr/share/java/postgresql.jar:/usr/share/java/ridl.jar:/usr/share/java/spin.jar:/usr/share/java/swingx.jar:/usr/share/java/swing-
layout.jar:/usr/share/java/unirest-java.jar:/usr/share/java/unoil.jar
net.sf.jabref.JabRefMain --debug

15:27:50.292 [AWT-EventQueue-0] ERROR net.sf.jabref.FallbackExceptionHandler -
Uncaught exception Occurred in Thread[AWT-EventQueue-0,6,main]
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
at
net.sf.jabref.logic.importer.ImportFormatReader.resetImportFormats(ImportFormatReader.java:56)
~[JabRef-3.8.2.jar:?]
at net.sf.jabref.JabRefMain.start(JabRefMain.java:78)
~[JabRef-3.8.2.jar:?]
at net.sf.jabref.JabRefMain.lambda$main$0(JabRefMain.java:40)
~[JabRef-3.8.2.jar:?]
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
~[?:?]
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:764) ~[?:?]
at java.awt.EventQueue.access$500(EventQueue.java:97) ~[?:?]
at java.awt.EventQueue$3.run(EventQueue.java:717) ~[?:?]
at java.awt.EventQueue$3.run(EventQueue.java:711) ~[?:?]
at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
at
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:89)
~[?:?]
at java.awt.EventQueue.dispatchEvent(EventQueue.java:734) ~[?:?]
at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:199)
[?:?]
at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
[?:?]
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
[?:?]
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) [?:?]
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) [?:?]
at java.awt.EventDispatchThread.run(EventDispatchThread.java:90) [?:?]
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException
at
jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
~[?:?]
at
jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:496) ~[?:?]
... 17 more


$ DEBUG_WRAPPER=1 JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref --debug
[debug] /usr/bin/jabref: Using provided JAVA_HOME =
'/usr/lib/jvm/java-8-openjdk-amd64/'
[debug] /usr/bin/jabref: Found JAVA_HOME = '/usr/lib/jvm/java-8-openjdk-amd64/'
[debug] /usr/bin/jabref: Found JAVA_CMD = '/usr/lib/jvm/java-8-openjdk-
amd64//bin/java'
/usr/lib/jvm/java-8-openjdk-amd64//bin/java
[warning] /usr/bin/jabref: /usr/lib/jvm/java-8-openjdk-amd64//bin/java
[debug] /usr/bin/jabref: Environment variable CLASSPATH is ''
[debug] /usr/bin/jabref: Runnning /usr/lib/jvm/java-8-openjdk-amd64//bin/java
-classpath