[jira] [Commented] (MJAR-62) Build-Jdk in Manifest.mf does not reflect which compiler version actually compiled the classes in the jar

["Nathan Revo (JIRA)" <ji...@apache.org>]

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

Nathan Revo commented on MJAR-62:
---------------------------------

I just spent 3 days trying to work around this problem.  Lots of frustration involved, and I want to know why Build-Jdk is defined inside maven-archiver.  

Also, why doesn't toolchains expose useful properties by default.  Version, home and architecture seem important to me.

Our solution is to create a custom plugin that will call the javac binary with the -version argument and extract the version.  This value will be set as a maven property, which should be usable inside the pom.  

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