Sorry for the late reply.
+1 on going to 1.7 as a minimum. Just a question on an associated pom
entry. Should our root pom now be changed to reflect this?
Right now we have this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<compilerId>javac</compilerId>
<source>1.6</source>
<target>1.6</target>
<debug>true</debug>
<!--
<verbose>true</verbose>
<forceJavacCompilerUse>true</forceJavacCompilerUse>
<fork>true</fork>
-->
</configuration>
<dependencies>
<dependency>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-compiler-javac</artifactId>
<version>2.3</version>
</dependency>
</dependencies>
</plugin>
On 4/11/15, 11:56 AM, "larry mccay" <[email protected]> wrote:
>All -
>
>After committing the changes for KNOX-509 - KnoxSSO - we have a minimum
>jdk
>requirement of 1.7.
>
>The apache jenkins job failed due to the dependency from the nimbus jwt
>library on 1.7.
>
>I changed the jenkins configuration and rebuilt and it is stable again.
>
>Apparently Hadoop common is running with 1.7 since I added the nimbus
>library as a dependency there as well and there has been no related
>failures.
>
>I think it is time that we drop 1.6 support - especially given that it is
>EOL'd by Oracle since 2013.
>
>So, I propose that our minimum JRE version be 1.7 in 0.6.0, that we MUST
>be
>able to build with 1.7 and also run on JRE 1.8.
>
>We will need to address our building with JDK 1.8 (and tests) in a follow
>up release.
>
>Thoughts?
>
>thanks,
>
>--larry
