Maven Shared Components

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

Details

  • Testcase included:
    yes
  • Patch Submitted:
    Yes
  • Number of attachments :
    1

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.

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 - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Benjamin Bentmann made changes -
Field Original Value New Value
Key MNG-4336 MSHARED-128
Complexity Intermediate
Project Maven 2 [ 10500 ] Maven Shared Components [ 11761 ]
Benjamin Bentmann made changes -
Component/s maven-shared-jar [ 13279 ]
Olivier Lamy made changes -
Link This issue relates to MSHARED-87 [ MSHARED-87 ]
Olivier Lamy made changes -
Assignee Olivier Lamy [ olamy ]
Fix Version/s maven-shared-jar-1.1 [ 15654 ]
Olivier Lamy made changes -
Resolution Duplicate [ 3 ]
Status Open [ 1 ] Closed [ 6 ]

People

  • Assignee:
    Olivier Lamy
    Reporter:
    Rafal Krzewski
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: