maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MJAR-62) Build-Jdk in Manifest.mf does not reflect which compiler version actually compiled the classes in the jar
Date Thu, 14 Jan 2016 12:11:39 GMT

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

Michael Osipov commented on MJAR-62:
------------------------------------

Maven version [3.3.1|https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12330193]
has improved toolchains support. I have a look at your questions later.

> 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ø
>         Attachments: example-app.zip
>
>
> 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)

Mime
View raw message