You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter Janssen (JIRA)" <ji...@apache.org> on 2015/09/17 13:15:45 UTC
[jira] [Commented] (MJAR-62) Build-Jdk in Manifest.mf does not
reflect which compiler version actually compiled the classes in the jar
[ https://issues.apache.org/jira/browse/MJAR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802757#comment-14802757 ]
Peter Janssen commented on MJAR-62:
-----------------------------------
I agree with Stefan that this is not expected behaviour. I supplied an example project (requiring a JDK17 profile in the settings.xml). Can we reconsider the close?
> Build-Jdk in Manifest.mf does not reflect which compiler version actually compiled the classes in the jar
> ---------------------------------------------------------------------------------------------------------
>
> Key: MJAR-62
> URL: https://issues.apache.org/jira/browse/MJAR-62
> Project: Maven JAR Plugin
> Issue Type: Bug
> Reporter: Stefan Magnus Landrø
>
> Manifest.mf does not reflect the version of the compiler that built the jar, but defaults to the version that maven runs under: Build-Jdk: ${java.version}.
> I believe this makes users uncertain of which compiler was actually used to build the classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)