In the light of a wholesale migration of maven and maven plugins to Java 6 as
a minimum supported version, this totally makes sense. Please note that the
patch sets source/target to 1.6 not 1.6+ (which is not a value option anyway
imho).
On the second point, project Jigsaw is going to cause a lot of havoc for
plugins that invoke Java tools, and I am not sure if people at Oracle are going
to do anything to make maven folks' lives easier, because people at Oracle are
still living in Stone Age with flint tools like Ant being prevalent. I think we
may need to start developing some framework for invoking Java9 tools as soon as
the API and the JDK structure fully crystallise.
--
Sergei Ivanov
>
>Wednesday, 18 February 2015 08:30 +0000 from Jörg Schaible
><joerg.schai...@swisspost.com>:
>Hi Tiago,
>just because Java 9 requires minimum source/target to be 1.6 for building,
>it does not mean that it cannot run java classes targeting older JDKs. The
>plugin should support also the minimal JDK version of the minimal supported
>Maven version. There's no need to build and release this plugin with Java 9.
>Cheers,
>Jörg
>Tiago Stürmer Daitx wrote:
>> JDK9 source and target version must be set to 1.6+ [1] and the file
>> tools.jar has been removed due to the Jigsaw project [2].
>>
>> The patch (attached and bellow) fix this, enabling jspc to be build
>> using JDK9 and removing the jspc-maven-plugin assert for tools.jar
>> when it is run using JDK9.
>>
>> Regards,
>> Tiago Daitx
>>
>> [1]
>> [ http://mail.openjdk.java.net/pipermail/hotspot-dev/2014-July/014595.html
>> [2] http://mreinhold.org/blog/jigsaw-modular-images
>---------------------------------------------------------------------
>To unsubscribe from this list, please visit:
> http://xircles.codehaus.org/manage_email
