You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Tran (JIRA)" <ji...@codehaus.org> on 2010/01/04 09:05:55 UTC

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

     [ http://jira.codehaus.org/browse/MDEP-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Tran updated MDEP-143:
--------------------------

    Attachment: MDEP-143.diff

I think it is worth to rethrow another ZipException for the shake of better error visibility. I attached the patch for review purpose since it is not a clean fix, until we start using java 5 where we would not lose the original stack trace

> 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, MDEP-143.diff
>
>
> 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