Seems like we're all in agreement then: https://issues.apache.org/jira/browse/BIGTOP-1358
Thanks, Roman. On Tue, Jul 1, 2014 at 10:39 AM, Mark Grover <m...@apache.org> wrote: > +1 given the problems described. > > > On Mon, Jun 30, 2014 at 10:13 PM, jay vyas <jayunit100.apa...@gmail.com> > wrote: > >> +1 for jdk 7 ! >> >> >> On Mon, Jun 30, 2014 at 10:34 PM, Konstantin Boudnik <c...@apache.org> >> wrote: >> >> > Yup, +1 >> > >> > On Sun, Jun 29, 2014 at 05:19PM, Roman Shaposhnik wrote: >> > > On Thu, Jun 26, 2014 at 7:03 PM, Andrew Purtell <apurt...@apache.org> >> > wrote: >> > > > With a bit of hacking on the build we could cross-compile to avoid >> the >> > type >> > > > related build failures that are creeping in as projects don't try >> > compiling >> > > > with JDK 6 any longer. >> > > > >> > > > $ javac -target 1.6 -bootclasspath /path/to/jdk/1.6/lib/rt.jar >> > > > >> > > > Nasty to require a JDK 6 and 7 for building, though. >> > > >> > > At this point, I'd suggest biting the bullet and declaring 0.8.0 >> > > JDK7+ only. Even for build. Three of the dozen or so projects >> > > already refuse to be built by anything but: >> > > * Hue 3.6 (can be hacked to stay with JDK6, but who will do it?) >> > > * Solr 4.9.0 (ditto) >> > > * Giraph 1.1.0 (not sure whether JDK7 specific functionality >> remains) >> > > >> > > So, unless somebody volunteers to solve all three of the above, >> > > I think 0.8.0 is about to move to JDK7. >> > > >> > > Scream within a week or forever...you know. >> > > >> > > Thanks, >> > > Roman. >> > >> >> >> >> -- >> jay vyas >>
