You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2017/08/04 15:14:00 UTC

[jira] [Created] (MDEP-578) Add message in case module name cannot be extracted from jar.

Robert Scholte created MDEP-578:
-----------------------------------

             Summary: 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
             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
(v6.4.14#64029)