[
https://issues.apache.org/jira/browse/MINDEXER-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965235#comment-17965235
]
Olivier Lamy commented on MINDEXER-15:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-indexer#436|https://github.com/apache/maven-indexer/issues/436].
> Indexer "blindly" opens JARs for inspection, causing logspam
> ------------------------------------------------------------
>
> Key: MINDEXER-15
> URL: https://issues.apache.org/jira/browse/MINDEXER-15
> Project: Maven Indexer (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 3.1.0, 4.0.0
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 4.1.0
>
>
> Indexer "blindly" opens JARs for inspection, causing logspam.
> Depending on "incoming" file, context produces tries to find the
> "counterpart" of it (POM->JAR or JAR->POM). This is done mainly by File path
> mangling, but no existence check occurs.
> Later, MinimalIndexCreator "blindly" tries to open up the (usually) JAR file
> using ZipFile, thus masking real cause (exception message says "Error opening
> Zip file", even if the file is not present).
> Simply, the file should tried to be opened only if present. Usually -- think
> deploy -- the first file is POM to be deployed, and later will come the JAR,
> resulting in good index content.
> This problem was not a bug, did not cause invalid index or missing data, it
> was just "log spamming".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
