Bug 656 – Fiji's Javac cannot report its version anymore

Bug 656 - Fiji's Javac cannot report its version anymore


Summary:	Fiji's Javac cannot report its version anymore

Status:	RESOLVED FIXED

Product:	Fiji
Classification:	Unclassified
Component:	Other
Version:	unspecified
Hardware:	All All

Importance:	P5 trivial
Assigned To:	ImageJ Bugs Mailing List

URL:

Depends on:
Blocks:

Reported:	2013-08-29 11:07 CDT by Curtis Rueden
Modified:	2013-09-04 15:45 CDT
CC List:	1 user (show)

See Also:

Description Curtis Rueden 2013-08-29 11:07:56 CDT

Since Fiji's custom version of Javac was Mavenized, it no longer embeds the version properly in its JAR manifest. You can see this by running:

$ java -jar jars/javac.jar -version
javac compiler message file broken: key=compiler.misc.version.resource.missing arguments=1.7.0_21, {1}, {2}, {3}, {4}, {5}, {6}, {7}

Of course, Fiji's version is customized from multiple different versions of Javac anyway (for details, see the commit history at: https://github.com/fiji/fiji/commits/master/src-plugins/javac). But: A) it would still be nice if that functionality worked as expected; and B) this misconfiguration might suggest other potential related misconfigurations of the JAR file resources.

Still, MiniMaven builds all of Fiji successfully, so I've marked this bug as trivial. Just filing so we don't forget...

Comment 1 Johannes Schindelin 2013-09-04 15:35:00 CDT

I fixed this in

https://github.com/fiji/fiji/commit/add9fcef1d19f191e2aca482f03ccf7ddf8dbac4

and deployed it as 1.6.0.24-ubuntu-fiji1 to reflect that we used Ubuntu's sources of 1.6.0u24 and patched one change of OpenJDK7's javac in to avoid having to ask the ImgLib2 developers to use less convoluted generic constructs ;-)

Comment 2 Curtis Rueden 2013-09-04 15:45:55 CDT

Awesome!

I am repeatedly flabbergasted by how disorganized and unfriendly Java is as a so-called "open source" project. But I am very grateful for your diligence in addressing such a ridiculous situation.