[
https://issues.apache.org/jira/browse/MJDEPS-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MJDEPS-15.
--------------------------------
Assignee: Robert Scholte
Resolution: Not A Problem
> The --multi-release option should only be specified when analyzing
> multi-release jars.
> --------------------------------------------------------------------------------------
>
> Key: MJDEPS-15
> URL: https://issues.apache.org/jira/browse/MJDEPS-15
> Project: Maven JDeps Plugin
> Issue Type: Bug
> Reporter: Aaron Whiteside
> Assignee: Robert Scholte
> Priority: Major
>
> In a normal project there is usually a mix of multi-release and
> non-multi-release dependencies.
> The maven-jdeps-plugin should support this and not force the user to manually
> determine what dependencies are multi-release or non-multi-release and
> exclude/include them. (we want a complete picture of all our dependencies
> dynamically, if we had to manually inspect each one we might as well not use
> jdeps at all)
> The plugin should take the <multiRelease> option and check each dependency to
> see if it truly is a multi-release JAR before passing the value of
> <multiRelease> on to jdeps using --multi-release argument.
> When running on Java 9 and higher,
> [https://docs.oracle.com/javase/9/docs/api/java/util/jar/JarFile.html#isMultiRelease--]
> Can be used.
> Prior to java 9, <multiRelease>/--multi-release isn't supported, and should
> be ignored.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
