You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/03/16 22:40:20 UTC
[jira] [Closed] (MINDEXER-74) JarFileContentsIndexCreator may stop
scanning under some circumstances
[ https://issues.apache.org/jira/browse/MINDEXER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MINDEXER-74.
----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.
> JarFileContentsIndexCreator may stop scanning under some circumstances
> ----------------------------------------------------------------------
>
> Key: MINDEXER-74
> URL: https://issues.apache.org/jira/browse/MINDEXER-74
> Project: Maven Indexer
> Issue Type: Bug
> Reporter: Cservenak, Tamas
> Priority: Major
>
> JarFileContentsIndexCreator, if throws some RuntimeException, will:
> * abort scanning
> * not provide enough context information
> Example:
> https://issues.sonatype.org/browse/NEXUS-5814
> Probably caused by some unicode entry in inspected JAR file:
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4244499
> Proposal:
> JarFileContentsIndexCreator should in these case provide more meaningful log entry (what file, what entry maybe), be more resistant to problems like these and should not stop scanning, but Scanner should continue (and probably skip this JAR file but logging this fact).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)