Hi,
>
> Should we have a branch that builds with JDK 6 alone?
I think this is just minor issue, which could be easily fixed with
existing JDK 1.5 API.
IMHO we can wait until 1.5 will EOL and then move trunk to be
compliant with JDK 1.6 and create branch for 1.5. But again, only if
we will have good reasons for that.
What do you think?
WBR,
Alexey.
>
>
> -Kedar
>
> On Thu, Jan 15, 2009 at 9:54 AM, Jeanfrancois Arcand <Jeanfrancois.Arcand_at_sun.com
> > wrote:
> Salut,
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Compilation failure
>
> /files/hudson/workspace/Grizzly-1.x-trunk/trunk/modules/utils/src/
> main/java/com/sun/grizzly/util/LinkedTransferQueue.java:[303,27]
> park() in java.util.concurrent.locks.LockSupport cannot be applied
> to (com.sun.grizzly.util.LinkedTransferQueue<E>)
>
> /files/hudson/workspace/Grizzly-1.x-trunk/trunk/modules/utils/src/
> main/java/com/sun/grizzly/util/LinkedTransferQueue.java:[308,27]
> parkNanos(long) in java.util.concurrent.locks.LockSupport cannot be
> applied to (com.sun.grizzly.util.LinkedTransferQueue<E>,long)
>
>
> [INFO]
> ------------------------------------------------------------------------
>
> Make sure it always build with JDK 5 (I know this is painful). The
> build works fine with JDK 6.
>
> A+
>
> -- Jeanfrancois
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
>