I just tried "mvn clean && mvn install" using 1.7.0_04 and it worked OK -- so maybe it's not your JDK. In any case, if you can get it to work by setting MAVEN_OPTS I wouldn't consider it a show-stopper.
> On Feb 3, 2015, at 2:50 PM, Jacques Nadeau <[email protected]> wrote: > > Hmm.. Still getting it even with clean and install run separately. Maybe > because I use an old Java on my verification machine (on purpose :) > > #java -version > java version "1.7.0_09" > Java(TM) SE Runtime Environment (build 1.7.0_09-b05) > Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode) > > Let me try something more recent. > > On Tue, Feb 3, 2015 at 12:33 PM, Julian Hyde <[email protected]> wrote: > >> I've not seen that. And I'm running on a MacBook Air with a mere 4GB >> memory, and I have not set MAVEN_OPTS. >> >> However, the recommended build command is "mvn clean && mvn install". >> See https://issues.apache.org/jira/browse/CALCITE-553 for details. >> >> Julian >> >> On Tue, Feb 3, 2015 at 12:27 PM, Jacques Nadeau <[email protected]> >> wrote: >>> Running mvn clean install on this release artifact, I got out of memory >>> exception. Running again to see if transient. Any others seeing this? >>> >>> On Tue, Feb 3, 2015 at 11:10 AM, James Taylor <[email protected]> >>> wrote: >>> >>>> +1. Ran the same tests as before and everything worked well. >>>> >>>> Thanks, >>>> James >>>> >>>> On Mon, Feb 2, 2015 at 11:05 AM, Julian Hyde <[email protected]> >> wrote: >>>>> Yes, CALCITE-582 is fixed. It says so in the commit log, the release >>>> notes and the RC3 vote email. >>>>> >>>>> Re Jacques’ comments: I have not marked it fixed because I have not >>>> merged it to master yet. When incorporating Vladimir’s patch I had to >> make >>>> some other changes to make ScannableTableTest.testSimple pass. >>>>> >>>>> I have not had chance to look at CALCITE-580 yet. I do not think it is >>>> fixed, and I do not consider it a show-stopper for the release. >>>>> >>>>> Julian >>>>> >>>>> Chin Wei Low is running into a different issue, probably >>>>> On Feb 1, 2015, at 7:05 PM, Jacques Nadeau <[email protected]> >> wrote: >>>>> >>>>>> I'm actually a bit confused on this. The branch-1.0 shows that >>>> CALCITE-582 >>>>>> was merged but I don't see it marked resolved nor a +1. It also >> looks >>>> like >>>>>> Vladimir was the author but he doesn't like the fix. >>>>>> >>>>>> On Sun, Feb 1, 2015 at 5:33 PM, Chin Wei Low <[email protected]> >>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Did issue 582 fixed? >>>>>>> >>>>>>> Testing with query like this: select a from abc >>>>>>> But, it throw the exception. >>>>>>> Exception in thread "main" java.lang.ClassCastException: >>>>>>> [Ljava.lang.Object; incompatible with java.lang.Integer >>>>>>> at >>>>>>> >>>>>>> >>>> >> org.apache.calcite.avatica.util.AbstractCursor$IntAccessor.getInt(AbstractCursor.java:460) >>>>>>> at >>>>>>> >>>>>>> >>>> >> org.apache.calcite.avatica.AvaticaResultSet.getInt(AvaticaResultSet.java:311) >>>>>>> >>>>>>> On Mon, Feb 2, 2015 at 12:37 AM, Vladimir Sitnikov < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>>> I needed to fix the bug and get a release out with the minimum >>>>>>>> of disruption >>>>>>>> >>>>>>>> I see, however I raised the question since this area clearly is >>>>>>>> related to public API. >>>>>>>> I do not like "just fix the bug" approach without agreed APIs. >>>>>>>> >>>>>>>>> CALCITE-558. Please get involved >>>>>>>> >>>>>>>> Well, I try to block/prevent one more non-required convention to >>>> appear. >>>>>>>> >>>>>>>> Vladimir >>>>>>>> >>>>>>> >>>>> >>>> >>
