Hi Michael, Please see this: http://blog.athico.com/2011/01/jdk15-future-for-drools-and-jbpm.html
The conclusion on IRC, IIRC, was that we're to target 1.5 until ~the end of the year and then move to 1.6. Cheers, Mike On 16 February 2011 11:00, Michael Neale <michael.ne...@gmail.com> wrote: > why 1.5 ? > > ---- > twitter.com/michaelneale > michaelneale.blogspot.com > www.michaelneale.net > > On Wednesday, 16 February 2011 at 8:55 PM, Michael Anstis wrote: > > Hi, > > Since we are destined to retain JDK1.5 compatibility for the time being and > the likelihood that we're making new workspaces (or what not) as the GIT > split-up progresses this is probably a good time to mention that, those of > us running with a JDK1.6, should ensure compatibility is set to 1.5. > > There's been a number of classes checked into GIT (for Guvnor) following > the split-up that had been written against a JDK1.6 with JDK1.6 > compatibility which fail to compile for those of us running either JDK1.5 or > JDK1.6 with JDK1.5 compatibility. > > I'm among the guilty so this isn't a finger pointing exercise, just a > reminder as it's too easy to forget. > > Cheers, > > Mike > _______________________________________________ > rules-dev mailing list > rules-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-dev > > > > _______________________________________________ > rules-dev mailing list > rules-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-dev > >
_______________________________________________ rules-dev mailing list rules-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev
