You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Schnell (Jira)" <ji...@apache.org> on 2020/01/03 11:58:00 UTC

[jira] [Comment Edited] (MJDEPS-15) The --multi-release option should only be specified when analyzing multi-release jars.

    [ https://issues.apache.org/jira/browse/MJDEPS-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007434#comment-17007434 ] 

Michael Schnell edited comment on MJDEPS-15 at 1/3/20 11:57 AM:
----------------------------------------------------------------

+1 Would be nice to have this feature

Unfortunately *jdeps* itself does not support mixed jars as stated in [https://bugs.openjdk.java.net/browse/JDK-8207162].

So the only way to go would be to call jdeps at least twice, once with "--multi-release" for all multi release jars and once without the argument for the rest.


was (Author: michael-schnell):
+1 Would be nice to have this feature

Unfortunately *jdeps* itself does not support mixed jars as stated in [JDK-8207162|[https://bugs.openjdk.java.net/browse/JDK-8207162]].

So the only way to go would be to call jdeps at least twice, once with "--multi-release" for all multi release jars and once without the argument for the rest.

> 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
>            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)