[
https://issues.apache.org/jira/browse/MDEP-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329560#comment-16329560
]
Hudson commented on MDEP-578:
-----------------------------
Build succeeded in Jenkins: Maven TLP » maven-dependency-plugin » master #2
See
https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/master/2/
> Add message in case module name cannot be extracted from jar.
> -------------------------------------------------------------
>
> Key: MDEP-578
> URL: https://issues.apache.org/jira/browse/MDEP-578
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: resolve
> Affects Versions: 3.0.1
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.0.2
>
>
> The following jars are just some examples where Java 9 cannot give an
> automatic module name:
> || jar || root cause ||
> | geronimo-servlet_2.4_spec-1.1.1.jar | geronimo.servlet.2.4.spec: Invalid
> module name: '2' is not a Java identifier |
> | jdom-1.0.jar | JDOMAbout$Author.class found in top-level directory (unnamed
> package not allowed in module) |
> | geronimo-jta_1.1_spec-1.1.jar | geronimo.jta.1.1.spec: Invalid module name:
> '1' is not a Java identifier |
> Who would have expected that reason for jdom? A message would help a lot
> (even though in the end it means you can still not refer to it)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
