Maven 2.x JAR Plugin

Build-Jdk in Manifest.mf does not reflect which compiler version actually compiled the classes in the jar

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Olivier Lamy added a comment -

Agree in case of forked compilation.
But currently it's impossible for the jar plugin to know if the javac was forked with using an other JAVA_HOME.
http://docs.codehaus.org/display/MAVEN/Toolchains will probably help.

Show
Olivier Lamy added a comment - Agree in case of forked compilation. But currently it's impossible for the jar plugin to know if the javac was forked with using an other JAVA_HOME. http://docs.codehaus.org/display/MAVEN/Toolchains will probably help.
Hide
Permalink
Frederic added a comment -

Is it possible for the jar plugin to support the toolchain features?
The manifest information (Build-Jdk) would then be correct.

Show
Frederic added a comment - Is it possible for the jar plugin to support the toolchain features? The manifest information (Build-Jdk) would then be correct.

People

  • Assignee:
    Unassigned
    Reporter:
    Stefan Magnus Landrø
Vote (4)
Watch (5)

Dates

  • Created:
    Updated: