Uploaded image for project: 'Maven Shared Components'
  1. Maven Shared Components
  2. MSHARED-128

Exceptions thrown by org.apache.maven.shared.jar.JarAnalyzer constructor should include pathname of the offending file

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • None
    • None
    • maven-shared-jar
    • None
    • Patch

    Description

      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.

      Attachments

        Issue Links

        relates to

        Improvement - An improvement or enhancement to an existing feature or task. MSHARED-87 ZipException throw by SDK's JarFile constructor may lack file name

        • Trivial - Cosmetic problem like misspelt words or misaligned text.
        • Closed

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            olamy Olivier Lamy
            rkrzewsk Rafal Krzewski
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment