[jira] Commented: (MDEP-143) incomplete literal/length tree when analyzing

["Dan Tran (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MDEP-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204522#action_204522 ] 

Dan Tran commented on MDEP-143:
-------------------------------

To fix this we need to wrap the original IOException with another IOException with additional info about the bad jar, however java 4 IOException does not have constructor IOException ( String cause, Throwable e ) ( and java 5 does )

so this is a tough fix, unless we are willing to throw another Exception type instead of IOException and still make Java 4 compatible at 

public interface ClassAnalyzer
{
    // fields -----------------------------------------------------------------

    String ROLE = ClassAnalyzer.class.getName();

    // public methods ---------------------------------------------------------

    Set analyze( URL url )
        throws IOException;
}





> incomplete literal/length tree when analyzing
> ---------------------------------------------
>
>                 Key: MDEP-143
>                 URL: http://jira.codehaus.org/browse/MDEP-143
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: analyze
>    Affects Versions: 2.0
>            Reporter: Baptiste MATHUS
>            Assignee: Brian Fox
>            Priority: Blocker
>             Fix For: 2.2
>
>         Attachments: analyze-crash.txt
>
>
> Starting analyze from a project directory, it crashes with this message : "incomplete literal/length tree". 
> It seems like some zip is corrupted, I guess this is a jar that may have this problem, but I can't figure which one it is.
> I guess maven-dependency-plugin should at least try to catch this exception to log which jar it was trying to analyze. This would help identify the corrupted jar in the local maven repository and try to correct/update it.
> Thanks a lot.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira