You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2017/09/13 18:44:00 UTC
[jira] [Created] (MJMOD-2) Classpath / Modulepath using the
dependencies of the current project. / Modulename using package name.
Karl Heinz Marbaise created MJMOD-2:
---------------------------------------
Summary: Classpath / Modulepath using the dependencies of the current project. / Modulename using package name.
Key: MJMOD-2
URL: https://issues.apache.org/jira/browse/MJMOD-2
Project: Maven JMod Plugin
Issue Type: Improvement
Affects Versions: 3.0.0-alpha-1
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
Priority: Blocker
Fix For: 3.0.0-alpha-1
Using for classpath / modulepath the current dependencies of the pom.
Using the packagename of the current module and define that as modulename.
Current best practice is to include the packagename as namespace.
If the module-info.class is there, it is also possible to extract this value with plexus-java.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)