Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Thu, 17 Sep 2015 11:15:45 +0000 (UTC)
From: "Peter Janssen (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.12803896.1162790805000.364805.1442488545951@Atlassian.JIRA>
In-Reply-To: <JIRA.12803896.1162790805000@Atlassian.JIRA>
References: <JIRA.12803896.1162790805000@Atlassian.JIRA>
 <JIRA.12803896.1162790805661@arcas>
Subject: [jira] [Commented] (MJAR-62) Build-Jdk in Manifest.mf does not
 reflect which compiler version actually compiled the classes in the jar
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/MJAR-62?page=3Dcom.atlassian.ji=
ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1480275=
7#comment-14802757 ]=20

Peter Janssen commented on MJAR-62:
-----------------------------------

I agree with Stefan that this is not expected behaviour. I supplied an exam=
ple project (requiring a JDK17 profile in the settings.xml). Can we reconsi=
der 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=C3=B8
>
> Manifest.mf does not reflect the version of the compiler that built the j=
ar, but defaults to the version that maven runs under:  Build-Jdk: ${java.v=
ersion}.
> 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)