You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2018/12/09 11:42:00 UTC
[jira] [Closed] (SUREFIRE-1608) dump error paths with the same root
cause in Boot Manifest-JAR only once without stacktrace
[ https://issues.apache.org/jira/browse/SUREFIRE-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tibor Digana closed SUREFIRE-1608.
----------------------------------
> dump error paths with the same root cause in Boot Manifest-JAR only once without stacktrace
> -------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1608
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1608
> Project: Maven Surefire
> Issue Type: Improvement
> Components: process forking
> Affects Versions: 3.0.0-M2
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M3
>
>
> Currently JDK 1.8.0u181 and higher requires relative paths in URI in MAIFEST of JAR.
> If user has local repo on different disk, absolute path is used and dump with a warning is reported in {{target/surefire-reports}}. This includes report with a stacktrace for every such jar file in local repo which may slow down the startup. Reporting only one case with same root cause is enough. We have included a hit:
> {{Hint: <argLine>-Djdk.net.URLClassPath.disableClassPathURLCheck=true</argLine>}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)