[ https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670325#comment-16670325 ]
Thorsten Glaser commented on SUREFIRE-1588: ------------------------------------------- Erm, can’t you please release a 2.x with the fix, as this is really important {color:#FF0000}RIGHT NOW{color}? We can upgrade to an incompatible 3.x later, but we’ll not use a -Mxxx milestone snapshot in production, and who knows what other incompatibilities 3.x will have. (As for making it Java 7+ that’s no problem, we got even the slowest and most conservative of customers to upgrade to Java 7 years ago, and almost all to Java 8 even, years ago even.) > Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8 > ----------------------------------------------------------------------- > > Key: SUREFIRE-1588 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1588 > Project: Maven Surefire > Issue Type: Bug > Affects Versions: 2.22.1 > Reporter: Cservenak, Tamas > Priority: Major > > See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of > Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces > Manifest class path entries to be relative, as defined in [2]. > Hence, surefire booter and rest of Maven classpath, that uses absolute URLs > are simply discarded. > Example error: > {noformat} > # Created at 2018-10-30T21:34:43.339 > Error: Could not find or load main class > org.apache.maven.surefire.booter.ForkedBooter{noformat} > using the new property > {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that > all the entries from the surefire JAR are simply ignored. > > [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925] > [2] > https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath > [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac] -- This message was sent by Atlassian JIRA (v7.6.3#76005)