Re: Java 1.7

[sainik dasgupta <ds...@gmail.com>]

We have a similar requirement where we use the new java.nio.file package.
We are working with flume 1.3.1 version and java 7 .Flume works fine with
java7.

We enforce with java 7 plugin


<

plugin>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-enforcer-plugin</artifactId>

<executions>

*<execution>*
* *

<id>enforce-versions</id>

<goals>

<goal>enforce</goal>

</goals>

<configuration>

<rules>

<requireJavaVersion>

<version>1.7</version>

</requireJavaVersion>

</rules>

</configuration>

</execution>

</executions>

</plugin>


On Fri, Jul 19, 2013 at 10:33 AM, Phil Scala <Ph...@globalrelay.net>wrote:

> Hi everyone,
>
> I was poking around and working on creating a patch to the spool directory
> source and noticed the pom.xml is setting the java compiler/source version
> to 1.6.  So I was wondering is there a historical reason to stay on 1.6?
> The patch I am working on would rely on some Java 1.7 functionality (new
> class :: java.nio.file.Files).  I would love any feedback and even up the
> discussion up if needed on moving to java 1.7.  BTW, a local compilation
> against 1.7 was fine with no errors.
>
> Thanks
>   Phil
>
> Phil Scala
> Developer / Architect
> Global Relay
>
> phil.scala@globalrelay.net
>
> 866.484.6630  |  info@globalrelay.net  |  globalrelay.com
>
>
>
>