maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tamás Cservenák (JIRA) <>
Subject [jira] Updated: (MINDEXER-15) Indexer "blindly" opens JARs for inspection, causing logspam
Date Wed, 30 Mar 2011 08:03:31 GMT


Tamás Cservenák updated MINDEXER-15:

    Fix Version/s: 4.1.0

> Indexer "blindly" opens JARs for inspection, causing logspam
> ------------------------------------------------------------
>                 Key: MINDEXER-15
>                 URL:
>             Project: Maven Indexer
>          Issue Type: Improvement
>    Affects Versions: 3.1.0, 4.0.0
>            Reporter: Tamás Cservenák
>             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
> This problem was not a bug, did not cause invalid index or missing data, it was just
"log spamming".

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message