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 2015/12/26 00:48:49 UTC
[jira] [Updated] (MSHARED-128) Exceptions thrown by
org.apache.maven.shared.jar.JarAnalyzer constructor should include pathname
of the offending file
[ https://issues.apache.org/jira/browse/MSHARED-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MSHARED-128:
-----------------------------------
Fix Version/s: (was: maven-shared-jar-1.1)
> Exceptions thrown by org.apache.maven.shared.jar.JarAnalyzer constructor should include pathname of the offending file
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: MSHARED-128
> URL: https://issues.apache.org/jira/browse/MSHARED-128
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-shared-jar
> Reporter: Rafal Krzewski
> Assignee: Olivier Lamy (*$^¨%`£)
> Attachments: maven-shared-jar_exception_message.patch
>
>
> A corrupted jar file in the repository, or an attempt to use classes directory in place of a jar during a build is tricky do diagnose, because the exception message does not reveal which file could not been opened.
> The attached patch includes the pathname in the exception message.
> JarAnalyzerTest was enhanced accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)