You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by Pat Ferrel <pa...@occamsmachete.com> on 2015/03/27 17:08:53 UTC
build error
Latest source for Spark 1.1.0 and Hadoop 1.2.1
Build complains about the move to <maven.compiler.target>1.7</maven.compiler.target> I think this was upped from 1.6 but not sure if that’s what the error is about.
I’m on Java 6 no this machine if that matters.
Actual error:
[INFO] Mahout Build Tools ................................ SUCCESS [3.512s]
[INFO] Apache Mahout ..................................... SUCCESS [0.603s]
[INFO] Mahout Math ....................................... FAILURE [6.453s]
[INFO] Mahout MapReduce Legacy ........................... SKIPPED
[INFO] Mahout Integration ................................ SKIPPED
[INFO] Mahout Examples ................................... SKIPPED
[INFO] Mahout Release Package ............................ SKIPPED
[INFO] Mahout Math Scala bindings ........................ SKIPPED
[INFO] Mahout Spark bindings ............................. SKIPPED
[INFO] Mahout Spark bindings shell ....................... SKIPPED
[INFO] Mahout H2O backend ................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11.609s
[INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
[INFO] Final Memory: 24M/310M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project mahout-math: Fatal error compiling: invalid target release: 1.7 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
Re: build error
Posted by Pat Ferrel <pa...@occamsmachete.com>.
Why is java 7 required? Support I get but required, do we have some reason for that?
On Mar 27, 2015, at 9:15 AM, Suneel Marthi <su...@gmail.com> wrote:
This is the Java version, gotta use Java 7
On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>
> Build complains about the move to
> <maven.compiler.target>1.7</maven.compiler.target> I think this was upped
> from 1.6 but not sure if that’s what the error is about.
>
> I’m on Java 6 no this machine if that matters.
>
> Actual error:
>
> [INFO] Mahout Build Tools ................................ SUCCESS [3.512s]
> [INFO] Apache Mahout ..................................... SUCCESS [0.603s]
> [INFO] Mahout Math ....................................... FAILURE [6.453s]
> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> [INFO] Mahout Integration ................................ SKIPPED
> [INFO] Mahout Examples ................................... SKIPPED
> [INFO] Mahout Release Package ............................ SKIPPED
> [INFO] Mahout Math Scala bindings ........................ SKIPPED
> [INFO] Mahout Spark bindings ............................. SKIPPED
> [INFO] Mahout Spark bindings shell ....................... SKIPPED
> [INFO] Mahout H2O backend ................................ SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 11.609s
> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> [INFO] Final Memory: 24M/310M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> (default-compile) on project mahout-math: Fatal error compiling: invalid
> target release: 1.7 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
>
>
Re: build error
Posted by Suneel Marthi <su...@gmail.com>.
I am not in "commit" mode now, if someone else can pick this up and commit
it go for it.
On Fri, Mar 27, 2015 at 1:16 PM, Suneel Marthi <su...@gmail.com>
wrote:
> Its not about removing Guava, but trying to minimize Guava usage with the
> upgrade to Java 7. Sure u can still use BiMaps but there are other things
> like the guava Closeables that Stevo mentioned should be replaced with
> equivalent Java 7 constructs.
>
> Switching isDir() to isDirectory() was my fault, will revert that back.
>
> On Fri, Mar 27, 2015 at 1:11 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
>> BTW guava is in scala cooccurrence so not sure it’s going to be removed
>> completely. It’s also used in Hadoop and Spark. Why are we trying to remove
>> it when it seems to be the defacto standard? Cooccurrence uses a unique to
>> Guava class (HashBiMap) so to remove it is not trivial. I’ve seen scala
>> versions but why fragment into implementing out own generic collections. Is
>> there a HashBiMap in Java 7, I haven’t heard.
>>
>> Anyway I don’t think forcing an upgrade to Java 7 is all that big a deal.
>> Go ahead and remove guava is you want but be aware that one part is still
>> being used.
>>
>> I’m more concerned with dropping support for hadoop 1.2.1 without
>> compelling reasons.
>>
>> On Mar 27, 2015, at 9:57 AM, Suneel Marthi <su...@gmail.com>
>> wrote:
>>
>> Agree with Stevo. there's another round of code cleanup we need to go thru
>> to eliminate guava collection calls and replace with straight Java 7
>> calls.
>> We agreed as part of the last hangout that Java 7 would be the minimal
>> Java
>> that we support going forward.
>>
>> On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com> wrote:
>>
>> > Question is what is minimal Java that we should require Mahout users to
>> > use. It was raised to 1.7 via MAHOUT-1652
>> > <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to
>> use
>> > Java 1.7 APIs, finally. E.g. after level was raised I was recently able
>> to
>> > eliminate some usage of Guava for closing Closable's with using
>> > try-with-resources Java 7 construct. We should minimize dependencies,
>> there
>> > are IMO too many. Depending more and more on standard libraries of Java
>> and
>> > Scala helps in that direction. Hopefully we do not wait much longer
>> before
>> > the level is raised even further to 1.8, so we have even less 3rd party
>> > dependencies.
>> >
>> > On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com>
>> wrote:
>> >
>> >> It should, Hadoop supports it long term and lots of people stuck there
>> >> with projects that haven’t been upgraded (Mahout comes to mind).
>> >>
>> >> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
>> >>
>> >> Have to check but I doubt that build supports hadoop 1.x any more.
>> >>
>> >> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <
>> suneel.marthi@gmail.com>
>> >> wrote:
>> >>
>> >>> This is the Java version, gotta use Java 7
>> >>>
>> >>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
>> >>> wrote:
>> >>>
>> >>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>> >>>>
>> >>>> Build complains about the move to
>> >>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
>> >> upped
>> >>>> from 1.6 but not sure if that’s what the error is about.
>> >>>>
>> >>>> I’m on Java 6 no this machine if that matters.
>> >>>>
>> >>>> Actual error:
>> >>>>
>> >>>> [INFO] Mahout Build Tools ................................ SUCCESS
>> >>> [3.512s]
>> >>>> [INFO] Apache Mahout ..................................... SUCCESS
>> >>> [0.603s]
>> >>>> [INFO] Mahout Math ....................................... FAILURE
>> >>> [6.453s]
>> >>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
>> >>>> [INFO] Mahout Integration ................................ SKIPPED
>> >>>> [INFO] Mahout Examples ................................... SKIPPED
>> >>>> [INFO] Mahout Release Package ............................ SKIPPED
>> >>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
>> >>>> [INFO] Mahout Spark bindings ............................. SKIPPED
>> >>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
>> >>>> [INFO] Mahout H2O backend ................................ SKIPPED
>> >>>> [INFO]
>> >>>>
>> > ------------------------------------------------------------------------
>> >>>> [INFO] BUILD FAILURE
>> >>>> [INFO]
>> >>>>
>> > ------------------------------------------------------------------------
>> >>>> [INFO] Total time: 11.609s
>> >>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
>> >>>> [INFO] Final Memory: 24M/310M
>> >>>> [INFO]
>> >>>>
>> > ------------------------------------------------------------------------
>> >>>> [ERROR] Failed to execute goal
>> >>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>> >>>> (default-compile) on project mahout-math: Fatal error compiling:
>> > invalid
>> >>>> target release: 1.7 -> [Help 1]
>> >>>> [ERROR]
>> >>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> > the
>> >>>> -e switch.
>> >>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>> logging.
>> >>>> [ERROR]
>> >>>>
>> >>>>
>> >>>
>> >>
>> >>
>> >
>>
>>
>
Re: build error
Posted by Pat Ferrel <pa...@occamsmachete.com>.
No doubt but couldn’t spend the time today, sorry.
On Mar 27, 2015, at 12:12 PM, Suneel Marthi <su...@gmail.com> wrote:
Hmm... Its not a straight global replace all isDirectory() with isDir().
Gotta differentiate between java.io.File.isDirectory() vs
org.apache.hadoop.fs.FileSystem.isDirectory()
Its the later that needs to be changed, changing the former is not gonna be
recognized.
On Fri, Mar 27, 2015 at 3:03 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> isDir isn’t recognized and the import isn’t found so looks like a pom
> changes and import additions
>
> On Mar 27, 2015, at 12:01 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> Reverting isDirectory() to isDir() should do it? What else is the issue?
>
> On Fri, Mar 27, 2015 at 3:00 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
>> wow, too many uses to track down and too many commits to back out.
>>
>> Looks like Suneel and Stevo have been working on this? To support Hadoop
>> 1.2.1 several things need to be backed out. I don’t have the time to work
>> through them right now. I changed all the IsDirectory but isDir isn’t
>> recognized and some other issues are coming up.
>>
>> I’m going to have to move back before all those commits to get a client
>> project going.
>>
>>
>> On Mar 27, 2015, at 10:35 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>>
>> OK, if it’s just isDirectory I may do it and get a test on a 1.2.1
> cluster
>> to boot.
>>
>> On Mar 27, 2015, at 10:24 AM, Suneel Marthi <su...@gmail.com>
>> wrote:
>>
>> +1 with Java 7
>>
>> will stick with Hadoop 1.2.1 support. Amen!
>>
>> On Fri, Mar 27, 2015 at 1:19 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
>>
>>> ok, don’t see a major problem with forcing Java 7.
>>>
>>> So are we agreeing to support Hadoop 1.2.1? That would be a big thing to
>>> drop even though I agree we must support 2.x and would come down in it’s
>>> favor if forced to choose.
>>>
>>>
>>> On Mar 27, 2015, at 10:16 AM, Suneel Marthi <su...@gmail.com>
>>> wrote:
>>>
>>> Its not about removing Guava, but trying to minimize Guava usage with
> the
>>> upgrade to Java 7. Sure u can still use BiMaps but there are other
> things
>>> like the guava Closeables that Stevo mentioned should be replaced with
>>> equivalent Java 7 constructs.
>>>
>>> Switching isDir() to isDirectory() was my fault, will revert that back.
>>>
>>> On Fri, Mar 27, 2015 at 1:11 PM, Pat Ferrel <pa...@occamsmachete.com>
>> wrote:
>>>
>>>> BTW guava is in scala cooccurrence so not sure it’s going to be removed
>>>> completely. It’s also used in Hadoop and Spark. Why are we trying to
>>> remove
>>>> it when it seems to be the defacto standard? Cooccurrence uses a unique
>>> to
>>>> Guava class (HashBiMap) so to remove it is not trivial. I’ve seen scala
>>>> versions but why fragment into implementing out own generic
> collections.
>>> Is
>>>> there a HashBiMap in Java 7, I haven’t heard.
>>>>
>>>> Anyway I don’t think forcing an upgrade to Java 7 is all that big a
>> deal.
>>>> Go ahead and remove guava is you want but be aware that one part is
>> still
>>>> being used.
>>>>
>>>> I’m more concerned with dropping support for hadoop 1.2.1 without
>>>> compelling reasons.
>>>>
>>>> On Mar 27, 2015, at 9:57 AM, Suneel Marthi <su...@gmail.com>
>>>> wrote:
>>>>
>>>> Agree with Stevo. there's another round of code cleanup we need to go
>>> thru
>>>> to eliminate guava collection calls and replace with straight Java 7
>>> calls.
>>>> We agreed as part of the last hangout that Java 7 would be the minimal
>>> Java
>>>> that we support going forward.
>>>>
>>>> On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com>
>>> wrote:
>>>>
>>>>> Question is what is minimal Java that we should require Mahout users
> to
>>>>> use. It was raised to 1.7 via MAHOUT-1652
>>>>> <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to
>>>> use
>>>>> Java 1.7 APIs, finally. E.g. after level was raised I was recently
> able
>>>> to
>>>>> eliminate some usage of Guava for closing Closable's with using
>>>>> try-with-resources Java 7 construct. We should minimize dependencies,
>>>> there
>>>>> are IMO too many. Depending more and more on standard libraries of
> Java
>>>> and
>>>>> Scala helps in that direction. Hopefully we do not wait much longer
>>>> before
>>>>> the level is raised even further to 1.8, so we have even less 3rd
> party
>>>>> dependencies.
>>>>>
>>>>> On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com>
>>>> wrote:
>>>>>
>>>>>> It should, Hadoop supports it long term and lots of people stuck
> there
>>>>>> with projects that haven’t been upgraded (Mahout comes to mind).
>>>>>>
>>>>>> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
>>>>>>
>>>>>> Have to check but I doubt that build supports hadoop 1.x any more.
>>>>>>
>>>>>> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <
>>> suneel.marthi@gmail.com
>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>> This is the Java version, gotta use Java 7
>>>>>>>
>>>>>>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pat@occamsmachete.com
>>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>>>>>>>>
>>>>>>>> Build complains about the move to
>>>>>>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
>>>>>> upped
>>>>>>>> from 1.6 but not sure if that’s what the error is about.
>>>>>>>>
>>>>>>>> I’m on Java 6 no this machine if that matters.
>>>>>>>>
>>>>>>>> Actual error:
>>>>>>>>
>>>>>>>> [INFO] Mahout Build Tools ................................ SUCCESS
>>>>>>> [3.512s]
>>>>>>>> [INFO] Apache Mahout ..................................... SUCCESS
>>>>>>> [0.603s]
>>>>>>>> [INFO] Mahout Math ....................................... FAILURE
>>>>>>> [6.453s]
>>>>>>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
>>>>>>>> [INFO] Mahout Integration ................................ SKIPPED
>>>>>>>> [INFO] Mahout Examples ................................... SKIPPED
>>>>>>>> [INFO] Mahout Release Package ............................ SKIPPED
>>>>>>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
>>>>>>>> [INFO] Mahout Spark bindings ............................. SKIPPED
>>>>>>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
>>>>>>>> [INFO] Mahout H2O backend ................................ SKIPPED
>>>>>>>> [INFO]
>>>>>>>>
>>>>>
>> ------------------------------------------------------------------------
>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>> [INFO]
>>>>>>>>
>>>>>
>> ------------------------------------------------------------------------
>>>>>>>> [INFO] Total time: 11.609s
>>>>>>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
>>>>>>>> [INFO] Final Memory: 24M/310M
>>>>>>>> [INFO]
>>>>>>>>
>>>>>
>> ------------------------------------------------------------------------
>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>> (default-compile) on project mahout-math: Fatal error compiling:
>>>>> invalid
>>>>>>>> target release: 1.7 -> [Help 1]
>>>>>>>> [ERROR]
>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven
> with
>>>>> the
>>>>>>>> -e switch.
>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>> logging.
>>>>>>>> [ERROR]
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>
Re: build error
Posted by Suneel Marthi <su...@gmail.com>.
Hmm... Its not a straight global replace all isDirectory() with isDir().
Gotta differentiate between java.io.File.isDirectory() vs
org.apache.hadoop.fs.FileSystem.isDirectory()
Its the later that needs to be changed, changing the former is not gonna be
recognized.
On Fri, Mar 27, 2015 at 3:03 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> isDir isn’t recognized and the import isn’t found so looks like a pom
> changes and import additions
>
> On Mar 27, 2015, at 12:01 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> Reverting isDirectory() to isDir() should do it? What else is the issue?
>
> On Fri, Mar 27, 2015 at 3:00 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> > wow, too many uses to track down and too many commits to back out.
> >
> > Looks like Suneel and Stevo have been working on this? To support Hadoop
> > 1.2.1 several things need to be backed out. I don’t have the time to work
> > through them right now. I changed all the IsDirectory but isDir isn’t
> > recognized and some other issues are coming up.
> >
> > I’m going to have to move back before all those commits to get a client
> > project going.
> >
> >
> > On Mar 27, 2015, at 10:35 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> >
> > OK, if it’s just isDirectory I may do it and get a test on a 1.2.1
> cluster
> > to boot.
> >
> > On Mar 27, 2015, at 10:24 AM, Suneel Marthi <su...@gmail.com>
> > wrote:
> >
> > +1 with Java 7
> >
> > will stick with Hadoop 1.2.1 support. Amen!
> >
> > On Fri, Mar 27, 2015 at 1:19 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
> >
> >> ok, don’t see a major problem with forcing Java 7.
> >>
> >> So are we agreeing to support Hadoop 1.2.1? That would be a big thing to
> >> drop even though I agree we must support 2.x and would come down in it’s
> >> favor if forced to choose.
> >>
> >>
> >> On Mar 27, 2015, at 10:16 AM, Suneel Marthi <su...@gmail.com>
> >> wrote:
> >>
> >> Its not about removing Guava, but trying to minimize Guava usage with
> the
> >> upgrade to Java 7. Sure u can still use BiMaps but there are other
> things
> >> like the guava Closeables that Stevo mentioned should be replaced with
> >> equivalent Java 7 constructs.
> >>
> >> Switching isDir() to isDirectory() was my fault, will revert that back.
> >>
> >> On Fri, Mar 27, 2015 at 1:11 PM, Pat Ferrel <pa...@occamsmachete.com>
> > wrote:
> >>
> >>> BTW guava is in scala cooccurrence so not sure it’s going to be removed
> >>> completely. It’s also used in Hadoop and Spark. Why are we trying to
> >> remove
> >>> it when it seems to be the defacto standard? Cooccurrence uses a unique
> >> to
> >>> Guava class (HashBiMap) so to remove it is not trivial. I’ve seen scala
> >>> versions but why fragment into implementing out own generic
> collections.
> >> Is
> >>> there a HashBiMap in Java 7, I haven’t heard.
> >>>
> >>> Anyway I don’t think forcing an upgrade to Java 7 is all that big a
> > deal.
> >>> Go ahead and remove guava is you want but be aware that one part is
> > still
> >>> being used.
> >>>
> >>> I’m more concerned with dropping support for hadoop 1.2.1 without
> >>> compelling reasons.
> >>>
> >>> On Mar 27, 2015, at 9:57 AM, Suneel Marthi <su...@gmail.com>
> >>> wrote:
> >>>
> >>> Agree with Stevo. there's another round of code cleanup we need to go
> >> thru
> >>> to eliminate guava collection calls and replace with straight Java 7
> >> calls.
> >>> We agreed as part of the last hangout that Java 7 would be the minimal
> >> Java
> >>> that we support going forward.
> >>>
> >>> On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com>
> >> wrote:
> >>>
> >>>> Question is what is minimal Java that we should require Mahout users
> to
> >>>> use. It was raised to 1.7 via MAHOUT-1652
> >>>> <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to
> >>> use
> >>>> Java 1.7 APIs, finally. E.g. after level was raised I was recently
> able
> >>> to
> >>>> eliminate some usage of Guava for closing Closable's with using
> >>>> try-with-resources Java 7 construct. We should minimize dependencies,
> >>> there
> >>>> are IMO too many. Depending more and more on standard libraries of
> Java
> >>> and
> >>>> Scala helps in that direction. Hopefully we do not wait much longer
> >>> before
> >>>> the level is raised even further to 1.8, so we have even less 3rd
> party
> >>>> dependencies.
> >>>>
> >>>> On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com>
> >>> wrote:
> >>>>
> >>>>> It should, Hadoop supports it long term and lots of people stuck
> there
> >>>>> with projects that haven’t been upgraded (Mahout comes to mind).
> >>>>>
> >>>>> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
> >>>>>
> >>>>> Have to check but I doubt that build supports hadoop 1.x any more.
> >>>>>
> >>>>> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <
> >> suneel.marthi@gmail.com
> >>>>
> >>>>> wrote:
> >>>>>
> >>>>>> This is the Java version, gotta use Java 7
> >>>>>>
> >>>>>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pat@occamsmachete.com
> >
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
> >>>>>>>
> >>>>>>> Build complains about the move to
> >>>>>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
> >>>>> upped
> >>>>>>> from 1.6 but not sure if that’s what the error is about.
> >>>>>>>
> >>>>>>> I’m on Java 6 no this machine if that matters.
> >>>>>>>
> >>>>>>> Actual error:
> >>>>>>>
> >>>>>>> [INFO] Mahout Build Tools ................................ SUCCESS
> >>>>>> [3.512s]
> >>>>>>> [INFO] Apache Mahout ..................................... SUCCESS
> >>>>>> [0.603s]
> >>>>>>> [INFO] Mahout Math ....................................... FAILURE
> >>>>>> [6.453s]
> >>>>>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> >>>>>>> [INFO] Mahout Integration ................................ SKIPPED
> >>>>>>> [INFO] Mahout Examples ................................... SKIPPED
> >>>>>>> [INFO] Mahout Release Package ............................ SKIPPED
> >>>>>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
> >>>>>>> [INFO] Mahout Spark bindings ............................. SKIPPED
> >>>>>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
> >>>>>>> [INFO] Mahout H2O backend ................................ SKIPPED
> >>>>>>> [INFO]
> >>>>>>>
> >>>>
> > ------------------------------------------------------------------------
> >>>>>>> [INFO] BUILD FAILURE
> >>>>>>> [INFO]
> >>>>>>>
> >>>>
> > ------------------------------------------------------------------------
> >>>>>>> [INFO] Total time: 11.609s
> >>>>>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> >>>>>>> [INFO] Final Memory: 24M/310M
> >>>>>>> [INFO]
> >>>>>>>
> >>>>
> > ------------------------------------------------------------------------
> >>>>>>> [ERROR] Failed to execute goal
> >>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>>>> (default-compile) on project mahout-math: Fatal error compiling:
> >>>> invalid
> >>>>>>> target release: 1.7 -> [Help 1]
> >>>>>>> [ERROR]
> >>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven
> with
> >>>> the
> >>>>>>> -e switch.
> >>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
> >> logging.
> >>>>>>> [ERROR]
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
>
>
Re: build error
Posted by Pat Ferrel <pa...@occamsmachete.com>.
isDir isn’t recognized and the import isn’t found so looks like a pom changes and import additions
On Mar 27, 2015, at 12:01 PM, Suneel Marthi <su...@gmail.com> wrote:
Reverting isDirectory() to isDir() should do it? What else is the issue?
On Fri, Mar 27, 2015 at 3:00 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> wow, too many uses to track down and too many commits to back out.
>
> Looks like Suneel and Stevo have been working on this? To support Hadoop
> 1.2.1 several things need to be backed out. I don’t have the time to work
> through them right now. I changed all the IsDirectory but isDir isn’t
> recognized and some other issues are coming up.
>
> I’m going to have to move back before all those commits to get a client
> project going.
>
>
> On Mar 27, 2015, at 10:35 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> OK, if it’s just isDirectory I may do it and get a test on a 1.2.1 cluster
> to boot.
>
> On Mar 27, 2015, at 10:24 AM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> +1 with Java 7
>
> will stick with Hadoop 1.2.1 support. Amen!
>
> On Fri, Mar 27, 2015 at 1:19 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
>> ok, don’t see a major problem with forcing Java 7.
>>
>> So are we agreeing to support Hadoop 1.2.1? That would be a big thing to
>> drop even though I agree we must support 2.x and would come down in it’s
>> favor if forced to choose.
>>
>>
>> On Mar 27, 2015, at 10:16 AM, Suneel Marthi <su...@gmail.com>
>> wrote:
>>
>> Its not about removing Guava, but trying to minimize Guava usage with the
>> upgrade to Java 7. Sure u can still use BiMaps but there are other things
>> like the guava Closeables that Stevo mentioned should be replaced with
>> equivalent Java 7 constructs.
>>
>> Switching isDir() to isDirectory() was my fault, will revert that back.
>>
>> On Fri, Mar 27, 2015 at 1:11 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
>>
>>> BTW guava is in scala cooccurrence so not sure it’s going to be removed
>>> completely. It’s also used in Hadoop and Spark. Why are we trying to
>> remove
>>> it when it seems to be the defacto standard? Cooccurrence uses a unique
>> to
>>> Guava class (HashBiMap) so to remove it is not trivial. I’ve seen scala
>>> versions but why fragment into implementing out own generic collections.
>> Is
>>> there a HashBiMap in Java 7, I haven’t heard.
>>>
>>> Anyway I don’t think forcing an upgrade to Java 7 is all that big a
> deal.
>>> Go ahead and remove guava is you want but be aware that one part is
> still
>>> being used.
>>>
>>> I’m more concerned with dropping support for hadoop 1.2.1 without
>>> compelling reasons.
>>>
>>> On Mar 27, 2015, at 9:57 AM, Suneel Marthi <su...@gmail.com>
>>> wrote:
>>>
>>> Agree with Stevo. there's another round of code cleanup we need to go
>> thru
>>> to eliminate guava collection calls and replace with straight Java 7
>> calls.
>>> We agreed as part of the last hangout that Java 7 would be the minimal
>> Java
>>> that we support going forward.
>>>
>>> On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com>
>> wrote:
>>>
>>>> Question is what is minimal Java that we should require Mahout users to
>>>> use. It was raised to 1.7 via MAHOUT-1652
>>>> <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to
>>> use
>>>> Java 1.7 APIs, finally. E.g. after level was raised I was recently able
>>> to
>>>> eliminate some usage of Guava for closing Closable's with using
>>>> try-with-resources Java 7 construct. We should minimize dependencies,
>>> there
>>>> are IMO too many. Depending more and more on standard libraries of Java
>>> and
>>>> Scala helps in that direction. Hopefully we do not wait much longer
>>> before
>>>> the level is raised even further to 1.8, so we have even less 3rd party
>>>> dependencies.
>>>>
>>>> On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com>
>>> wrote:
>>>>
>>>>> It should, Hadoop supports it long term and lots of people stuck there
>>>>> with projects that haven’t been upgraded (Mahout comes to mind).
>>>>>
>>>>> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
>>>>>
>>>>> Have to check but I doubt that build supports hadoop 1.x any more.
>>>>>
>>>>> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <
>> suneel.marthi@gmail.com
>>>>
>>>>> wrote:
>>>>>
>>>>>> This is the Java version, gotta use Java 7
>>>>>>
>>>>>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>>>>>>>
>>>>>>> Build complains about the move to
>>>>>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
>>>>> upped
>>>>>>> from 1.6 but not sure if that’s what the error is about.
>>>>>>>
>>>>>>> I’m on Java 6 no this machine if that matters.
>>>>>>>
>>>>>>> Actual error:
>>>>>>>
>>>>>>> [INFO] Mahout Build Tools ................................ SUCCESS
>>>>>> [3.512s]
>>>>>>> [INFO] Apache Mahout ..................................... SUCCESS
>>>>>> [0.603s]
>>>>>>> [INFO] Mahout Math ....................................... FAILURE
>>>>>> [6.453s]
>>>>>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
>>>>>>> [INFO] Mahout Integration ................................ SKIPPED
>>>>>>> [INFO] Mahout Examples ................................... SKIPPED
>>>>>>> [INFO] Mahout Release Package ............................ SKIPPED
>>>>>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
>>>>>>> [INFO] Mahout Spark bindings ............................. SKIPPED
>>>>>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
>>>>>>> [INFO] Mahout H2O backend ................................ SKIPPED
>>>>>>> [INFO]
>>>>>>>
>>>>
> ------------------------------------------------------------------------
>>>>>>> [INFO] BUILD FAILURE
>>>>>>> [INFO]
>>>>>>>
>>>>
> ------------------------------------------------------------------------
>>>>>>> [INFO] Total time: 11.609s
>>>>>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
>>>>>>> [INFO] Final Memory: 24M/310M
>>>>>>> [INFO]
>>>>>>>
>>>>
> ------------------------------------------------------------------------
>>>>>>> [ERROR] Failed to execute goal
>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>> (default-compile) on project mahout-math: Fatal error compiling:
>>>> invalid
>>>>>>> target release: 1.7 -> [Help 1]
>>>>>>> [ERROR]
>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>>>> the
>>>>>>> -e switch.
>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>> logging.
>>>>>>> [ERROR]
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
Re: build error
Posted by Suneel Marthi <su...@gmail.com>.
Reverting isDirectory() to isDir() should do it? What else is the issue?
On Fri, Mar 27, 2015 at 3:00 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> wow, too many uses to track down and too many commits to back out.
>
> Looks like Suneel and Stevo have been working on this? To support Hadoop
> 1.2.1 several things need to be backed out. I don’t have the time to work
> through them right now. I changed all the IsDirectory but isDir isn’t
> recognized and some other issues are coming up.
>
> I’m going to have to move back before all those commits to get a client
> project going.
>
>
> On Mar 27, 2015, at 10:35 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> OK, if it’s just isDirectory I may do it and get a test on a 1.2.1 cluster
> to boot.
>
> On Mar 27, 2015, at 10:24 AM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> +1 with Java 7
>
> will stick with Hadoop 1.2.1 support. Amen!
>
> On Fri, Mar 27, 2015 at 1:19 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> > ok, don’t see a major problem with forcing Java 7.
> >
> > So are we agreeing to support Hadoop 1.2.1? That would be a big thing to
> > drop even though I agree we must support 2.x and would come down in it’s
> > favor if forced to choose.
> >
> >
> > On Mar 27, 2015, at 10:16 AM, Suneel Marthi <su...@gmail.com>
> > wrote:
> >
> > Its not about removing Guava, but trying to minimize Guava usage with the
> > upgrade to Java 7. Sure u can still use BiMaps but there are other things
> > like the guava Closeables that Stevo mentioned should be replaced with
> > equivalent Java 7 constructs.
> >
> > Switching isDir() to isDirectory() was my fault, will revert that back.
> >
> > On Fri, Mar 27, 2015 at 1:11 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
> >
> >> BTW guava is in scala cooccurrence so not sure it’s going to be removed
> >> completely. It’s also used in Hadoop and Spark. Why are we trying to
> > remove
> >> it when it seems to be the defacto standard? Cooccurrence uses a unique
> > to
> >> Guava class (HashBiMap) so to remove it is not trivial. I’ve seen scala
> >> versions but why fragment into implementing out own generic collections.
> > Is
> >> there a HashBiMap in Java 7, I haven’t heard.
> >>
> >> Anyway I don’t think forcing an upgrade to Java 7 is all that big a
> deal.
> >> Go ahead and remove guava is you want but be aware that one part is
> still
> >> being used.
> >>
> >> I’m more concerned with dropping support for hadoop 1.2.1 without
> >> compelling reasons.
> >>
> >> On Mar 27, 2015, at 9:57 AM, Suneel Marthi <su...@gmail.com>
> >> wrote:
> >>
> >> Agree with Stevo. there's another round of code cleanup we need to go
> > thru
> >> to eliminate guava collection calls and replace with straight Java 7
> > calls.
> >> We agreed as part of the last hangout that Java 7 would be the minimal
> > Java
> >> that we support going forward.
> >>
> >> On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com>
> > wrote:
> >>
> >>> Question is what is minimal Java that we should require Mahout users to
> >>> use. It was raised to 1.7 via MAHOUT-1652
> >>> <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to
> >> use
> >>> Java 1.7 APIs, finally. E.g. after level was raised I was recently able
> >> to
> >>> eliminate some usage of Guava for closing Closable's with using
> >>> try-with-resources Java 7 construct. We should minimize dependencies,
> >> there
> >>> are IMO too many. Depending more and more on standard libraries of Java
> >> and
> >>> Scala helps in that direction. Hopefully we do not wait much longer
> >> before
> >>> the level is raised even further to 1.8, so we have even less 3rd party
> >>> dependencies.
> >>>
> >>> On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com>
> >> wrote:
> >>>
> >>>> It should, Hadoop supports it long term and lots of people stuck there
> >>>> with projects that haven’t been upgraded (Mahout comes to mind).
> >>>>
> >>>> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
> >>>>
> >>>> Have to check but I doubt that build supports hadoop 1.x any more.
> >>>>
> >>>> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <
> > suneel.marthi@gmail.com
> >>>
> >>>> wrote:
> >>>>
> >>>>> This is the Java version, gotta use Java 7
> >>>>>
> >>>>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> >>>>> wrote:
> >>>>>
> >>>>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
> >>>>>>
> >>>>>> Build complains about the move to
> >>>>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
> >>>> upped
> >>>>>> from 1.6 but not sure if that’s what the error is about.
> >>>>>>
> >>>>>> I’m on Java 6 no this machine if that matters.
> >>>>>>
> >>>>>> Actual error:
> >>>>>>
> >>>>>> [INFO] Mahout Build Tools ................................ SUCCESS
> >>>>> [3.512s]
> >>>>>> [INFO] Apache Mahout ..................................... SUCCESS
> >>>>> [0.603s]
> >>>>>> [INFO] Mahout Math ....................................... FAILURE
> >>>>> [6.453s]
> >>>>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> >>>>>> [INFO] Mahout Integration ................................ SKIPPED
> >>>>>> [INFO] Mahout Examples ................................... SKIPPED
> >>>>>> [INFO] Mahout Release Package ............................ SKIPPED
> >>>>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
> >>>>>> [INFO] Mahout Spark bindings ............................. SKIPPED
> >>>>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
> >>>>>> [INFO] Mahout H2O backend ................................ SKIPPED
> >>>>>> [INFO]
> >>>>>>
> >>>
> ------------------------------------------------------------------------
> >>>>>> [INFO] BUILD FAILURE
> >>>>>> [INFO]
> >>>>>>
> >>>
> ------------------------------------------------------------------------
> >>>>>> [INFO] Total time: 11.609s
> >>>>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> >>>>>> [INFO] Final Memory: 24M/310M
> >>>>>> [INFO]
> >>>>>>
> >>>
> ------------------------------------------------------------------------
> >>>>>> [ERROR] Failed to execute goal
> >>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>>> (default-compile) on project mahout-math: Fatal error compiling:
> >>> invalid
> >>>>>> target release: 1.7 -> [Help 1]
> >>>>>> [ERROR]
> >>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
> >>> the
> >>>>>> -e switch.
> >>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
> > logging.
> >>>>>> [ERROR]
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>
> >>
> >
> >
>
>
>
Re: build error
Posted by Pat Ferrel <pa...@occamsmachete.com>.
wow, too many uses to track down and too many commits to back out.
Looks like Suneel and Stevo have been working on this? To support Hadoop 1.2.1 several things need to be backed out. I don’t have the time to work through them right now. I changed all the IsDirectory but isDir isn’t recognized and some other issues are coming up.
I’m going to have to move back before all those commits to get a client project going.
On Mar 27, 2015, at 10:35 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
OK, if it’s just isDirectory I may do it and get a test on a 1.2.1 cluster to boot.
On Mar 27, 2015, at 10:24 AM, Suneel Marthi <su...@gmail.com> wrote:
+1 with Java 7
will stick with Hadoop 1.2.1 support. Amen!
On Fri, Mar 27, 2015 at 1:19 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> ok, don’t see a major problem with forcing Java 7.
>
> So are we agreeing to support Hadoop 1.2.1? That would be a big thing to
> drop even though I agree we must support 2.x and would come down in it’s
> favor if forced to choose.
>
>
> On Mar 27, 2015, at 10:16 AM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> Its not about removing Guava, but trying to minimize Guava usage with the
> upgrade to Java 7. Sure u can still use BiMaps but there are other things
> like the guava Closeables that Stevo mentioned should be replaced with
> equivalent Java 7 constructs.
>
> Switching isDir() to isDirectory() was my fault, will revert that back.
>
> On Fri, Mar 27, 2015 at 1:11 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
>> BTW guava is in scala cooccurrence so not sure it’s going to be removed
>> completely. It’s also used in Hadoop and Spark. Why are we trying to
> remove
>> it when it seems to be the defacto standard? Cooccurrence uses a unique
> to
>> Guava class (HashBiMap) so to remove it is not trivial. I’ve seen scala
>> versions but why fragment into implementing out own generic collections.
> Is
>> there a HashBiMap in Java 7, I haven’t heard.
>>
>> Anyway I don’t think forcing an upgrade to Java 7 is all that big a deal.
>> Go ahead and remove guava is you want but be aware that one part is still
>> being used.
>>
>> I’m more concerned with dropping support for hadoop 1.2.1 without
>> compelling reasons.
>>
>> On Mar 27, 2015, at 9:57 AM, Suneel Marthi <su...@gmail.com>
>> wrote:
>>
>> Agree with Stevo. there's another round of code cleanup we need to go
> thru
>> to eliminate guava collection calls and replace with straight Java 7
> calls.
>> We agreed as part of the last hangout that Java 7 would be the minimal
> Java
>> that we support going forward.
>>
>> On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com>
> wrote:
>>
>>> Question is what is minimal Java that we should require Mahout users to
>>> use. It was raised to 1.7 via MAHOUT-1652
>>> <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to
>> use
>>> Java 1.7 APIs, finally. E.g. after level was raised I was recently able
>> to
>>> eliminate some usage of Guava for closing Closable's with using
>>> try-with-resources Java 7 construct. We should minimize dependencies,
>> there
>>> are IMO too many. Depending more and more on standard libraries of Java
>> and
>>> Scala helps in that direction. Hopefully we do not wait much longer
>> before
>>> the level is raised even further to 1.8, so we have even less 3rd party
>>> dependencies.
>>>
>>> On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com>
>> wrote:
>>>
>>>> It should, Hadoop supports it long term and lots of people stuck there
>>>> with projects that haven’t been upgraded (Mahout comes to mind).
>>>>
>>>> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
>>>>
>>>> Have to check but I doubt that build supports hadoop 1.x any more.
>>>>
>>>> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <
> suneel.marthi@gmail.com
>>>
>>>> wrote:
>>>>
>>>>> This is the Java version, gotta use Java 7
>>>>>
>>>>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
>>>>> wrote:
>>>>>
>>>>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>>>>>>
>>>>>> Build complains about the move to
>>>>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
>>>> upped
>>>>>> from 1.6 but not sure if that’s what the error is about.
>>>>>>
>>>>>> I’m on Java 6 no this machine if that matters.
>>>>>>
>>>>>> Actual error:
>>>>>>
>>>>>> [INFO] Mahout Build Tools ................................ SUCCESS
>>>>> [3.512s]
>>>>>> [INFO] Apache Mahout ..................................... SUCCESS
>>>>> [0.603s]
>>>>>> [INFO] Mahout Math ....................................... FAILURE
>>>>> [6.453s]
>>>>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
>>>>>> [INFO] Mahout Integration ................................ SKIPPED
>>>>>> [INFO] Mahout Examples ................................... SKIPPED
>>>>>> [INFO] Mahout Release Package ............................ SKIPPED
>>>>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
>>>>>> [INFO] Mahout Spark bindings ............................. SKIPPED
>>>>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
>>>>>> [INFO] Mahout H2O backend ................................ SKIPPED
>>>>>> [INFO]
>>>>>>
>>> ------------------------------------------------------------------------
>>>>>> [INFO] BUILD FAILURE
>>>>>> [INFO]
>>>>>>
>>> ------------------------------------------------------------------------
>>>>>> [INFO] Total time: 11.609s
>>>>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
>>>>>> [INFO] Final Memory: 24M/310M
>>>>>> [INFO]
>>>>>>
>>> ------------------------------------------------------------------------
>>>>>> [ERROR] Failed to execute goal
>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>> (default-compile) on project mahout-math: Fatal error compiling:
>>> invalid
>>>>>> target release: 1.7 -> [Help 1]
>>>>>> [ERROR]
>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>>> the
>>>>>> -e switch.
>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
>>>>>> [ERROR]
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
>
Re: build error
Posted by Pat Ferrel <pa...@occamsmachete.com>.
OK, if it’s just isDirectory I may do it and get a test on a 1.2.1 cluster to boot.
On Mar 27, 2015, at 10:24 AM, Suneel Marthi <su...@gmail.com> wrote:
+1 with Java 7
will stick with Hadoop 1.2.1 support. Amen!
On Fri, Mar 27, 2015 at 1:19 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> ok, don’t see a major problem with forcing Java 7.
>
> So are we agreeing to support Hadoop 1.2.1? That would be a big thing to
> drop even though I agree we must support 2.x and would come down in it’s
> favor if forced to choose.
>
>
> On Mar 27, 2015, at 10:16 AM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> Its not about removing Guava, but trying to minimize Guava usage with the
> upgrade to Java 7. Sure u can still use BiMaps but there are other things
> like the guava Closeables that Stevo mentioned should be replaced with
> equivalent Java 7 constructs.
>
> Switching isDir() to isDirectory() was my fault, will revert that back.
>
> On Fri, Mar 27, 2015 at 1:11 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
>> BTW guava is in scala cooccurrence so not sure it’s going to be removed
>> completely. It’s also used in Hadoop and Spark. Why are we trying to
> remove
>> it when it seems to be the defacto standard? Cooccurrence uses a unique
> to
>> Guava class (HashBiMap) so to remove it is not trivial. I’ve seen scala
>> versions but why fragment into implementing out own generic collections.
> Is
>> there a HashBiMap in Java 7, I haven’t heard.
>>
>> Anyway I don’t think forcing an upgrade to Java 7 is all that big a deal.
>> Go ahead and remove guava is you want but be aware that one part is still
>> being used.
>>
>> I’m more concerned with dropping support for hadoop 1.2.1 without
>> compelling reasons.
>>
>> On Mar 27, 2015, at 9:57 AM, Suneel Marthi <su...@gmail.com>
>> wrote:
>>
>> Agree with Stevo. there's another round of code cleanup we need to go
> thru
>> to eliminate guava collection calls and replace with straight Java 7
> calls.
>> We agreed as part of the last hangout that Java 7 would be the minimal
> Java
>> that we support going forward.
>>
>> On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com>
> wrote:
>>
>>> Question is what is minimal Java that we should require Mahout users to
>>> use. It was raised to 1.7 via MAHOUT-1652
>>> <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to
>> use
>>> Java 1.7 APIs, finally. E.g. after level was raised I was recently able
>> to
>>> eliminate some usage of Guava for closing Closable's with using
>>> try-with-resources Java 7 construct. We should minimize dependencies,
>> there
>>> are IMO too many. Depending more and more on standard libraries of Java
>> and
>>> Scala helps in that direction. Hopefully we do not wait much longer
>> before
>>> the level is raised even further to 1.8, so we have even less 3rd party
>>> dependencies.
>>>
>>> On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com>
>> wrote:
>>>
>>>> It should, Hadoop supports it long term and lots of people stuck there
>>>> with projects that haven’t been upgraded (Mahout comes to mind).
>>>>
>>>> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
>>>>
>>>> Have to check but I doubt that build supports hadoop 1.x any more.
>>>>
>>>> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <
> suneel.marthi@gmail.com
>>>
>>>> wrote:
>>>>
>>>>> This is the Java version, gotta use Java 7
>>>>>
>>>>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
>>>>> wrote:
>>>>>
>>>>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>>>>>>
>>>>>> Build complains about the move to
>>>>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
>>>> upped
>>>>>> from 1.6 but not sure if that’s what the error is about.
>>>>>>
>>>>>> I’m on Java 6 no this machine if that matters.
>>>>>>
>>>>>> Actual error:
>>>>>>
>>>>>> [INFO] Mahout Build Tools ................................ SUCCESS
>>>>> [3.512s]
>>>>>> [INFO] Apache Mahout ..................................... SUCCESS
>>>>> [0.603s]
>>>>>> [INFO] Mahout Math ....................................... FAILURE
>>>>> [6.453s]
>>>>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
>>>>>> [INFO] Mahout Integration ................................ SKIPPED
>>>>>> [INFO] Mahout Examples ................................... SKIPPED
>>>>>> [INFO] Mahout Release Package ............................ SKIPPED
>>>>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
>>>>>> [INFO] Mahout Spark bindings ............................. SKIPPED
>>>>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
>>>>>> [INFO] Mahout H2O backend ................................ SKIPPED
>>>>>> [INFO]
>>>>>>
>>> ------------------------------------------------------------------------
>>>>>> [INFO] BUILD FAILURE
>>>>>> [INFO]
>>>>>>
>>> ------------------------------------------------------------------------
>>>>>> [INFO] Total time: 11.609s
>>>>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
>>>>>> [INFO] Final Memory: 24M/310M
>>>>>> [INFO]
>>>>>>
>>> ------------------------------------------------------------------------
>>>>>> [ERROR] Failed to execute goal
>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>> (default-compile) on project mahout-math: Fatal error compiling:
>>> invalid
>>>>>> target release: 1.7 -> [Help 1]
>>>>>> [ERROR]
>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>>> the
>>>>>> -e switch.
>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
>>>>>> [ERROR]
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
>
Re: build error
Posted by Suneel Marthi <su...@gmail.com>.
+1 with Java 7
will stick with Hadoop 1.2.1 support. Amen!
On Fri, Mar 27, 2015 at 1:19 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> ok, don’t see a major problem with forcing Java 7.
>
> So are we agreeing to support Hadoop 1.2.1? That would be a big thing to
> drop even though I agree we must support 2.x and would come down in it’s
> favor if forced to choose.
>
>
> On Mar 27, 2015, at 10:16 AM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> Its not about removing Guava, but trying to minimize Guava usage with the
> upgrade to Java 7. Sure u can still use BiMaps but there are other things
> like the guava Closeables that Stevo mentioned should be replaced with
> equivalent Java 7 constructs.
>
> Switching isDir() to isDirectory() was my fault, will revert that back.
>
> On Fri, Mar 27, 2015 at 1:11 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> > BTW guava is in scala cooccurrence so not sure it’s going to be removed
> > completely. It’s also used in Hadoop and Spark. Why are we trying to
> remove
> > it when it seems to be the defacto standard? Cooccurrence uses a unique
> to
> > Guava class (HashBiMap) so to remove it is not trivial. I’ve seen scala
> > versions but why fragment into implementing out own generic collections.
> Is
> > there a HashBiMap in Java 7, I haven’t heard.
> >
> > Anyway I don’t think forcing an upgrade to Java 7 is all that big a deal.
> > Go ahead and remove guava is you want but be aware that one part is still
> > being used.
> >
> > I’m more concerned with dropping support for hadoop 1.2.1 without
> > compelling reasons.
> >
> > On Mar 27, 2015, at 9:57 AM, Suneel Marthi <su...@gmail.com>
> > wrote:
> >
> > Agree with Stevo. there's another round of code cleanup we need to go
> thru
> > to eliminate guava collection calls and replace with straight Java 7
> calls.
> > We agreed as part of the last hangout that Java 7 would be the minimal
> Java
> > that we support going forward.
> >
> > On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com>
> wrote:
> >
> >> Question is what is minimal Java that we should require Mahout users to
> >> use. It was raised to 1.7 via MAHOUT-1652
> >> <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to
> > use
> >> Java 1.7 APIs, finally. E.g. after level was raised I was recently able
> > to
> >> eliminate some usage of Guava for closing Closable's with using
> >> try-with-resources Java 7 construct. We should minimize dependencies,
> > there
> >> are IMO too many. Depending more and more on standard libraries of Java
> > and
> >> Scala helps in that direction. Hopefully we do not wait much longer
> > before
> >> the level is raised even further to 1.8, so we have even less 3rd party
> >> dependencies.
> >>
> >> On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com>
> > wrote:
> >>
> >>> It should, Hadoop supports it long term and lots of people stuck there
> >>> with projects that haven’t been upgraded (Mahout comes to mind).
> >>>
> >>> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
> >>>
> >>> Have to check but I doubt that build supports hadoop 1.x any more.
> >>>
> >>> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <
> suneel.marthi@gmail.com
> >>
> >>> wrote:
> >>>
> >>>> This is the Java version, gotta use Java 7
> >>>>
> >>>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> >>>> wrote:
> >>>>
> >>>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
> >>>>>
> >>>>> Build complains about the move to
> >>>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
> >>> upped
> >>>>> from 1.6 but not sure if that’s what the error is about.
> >>>>>
> >>>>> I’m on Java 6 no this machine if that matters.
> >>>>>
> >>>>> Actual error:
> >>>>>
> >>>>> [INFO] Mahout Build Tools ................................ SUCCESS
> >>>> [3.512s]
> >>>>> [INFO] Apache Mahout ..................................... SUCCESS
> >>>> [0.603s]
> >>>>> [INFO] Mahout Math ....................................... FAILURE
> >>>> [6.453s]
> >>>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> >>>>> [INFO] Mahout Integration ................................ SKIPPED
> >>>>> [INFO] Mahout Examples ................................... SKIPPED
> >>>>> [INFO] Mahout Release Package ............................ SKIPPED
> >>>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
> >>>>> [INFO] Mahout Spark bindings ............................. SKIPPED
> >>>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
> >>>>> [INFO] Mahout H2O backend ................................ SKIPPED
> >>>>> [INFO]
> >>>>>
> >> ------------------------------------------------------------------------
> >>>>> [INFO] BUILD FAILURE
> >>>>> [INFO]
> >>>>>
> >> ------------------------------------------------------------------------
> >>>>> [INFO] Total time: 11.609s
> >>>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> >>>>> [INFO] Final Memory: 24M/310M
> >>>>> [INFO]
> >>>>>
> >> ------------------------------------------------------------------------
> >>>>> [ERROR] Failed to execute goal
> >>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>> (default-compile) on project mahout-math: Fatal error compiling:
> >> invalid
> >>>>> target release: 1.7 -> [Help 1]
> >>>>> [ERROR]
> >>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
> >> the
> >>>>> -e switch.
> >>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
> >>>>> [ERROR]
> >>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>
> >
> >
>
>
Re: build error
Posted by Pat Ferrel <pa...@occamsmachete.com>.
ok, don’t see a major problem with forcing Java 7.
So are we agreeing to support Hadoop 1.2.1? That would be a big thing to drop even though I agree we must support 2.x and would come down in it’s favor if forced to choose.
On Mar 27, 2015, at 10:16 AM, Suneel Marthi <su...@gmail.com> wrote:
Its not about removing Guava, but trying to minimize Guava usage with the
upgrade to Java 7. Sure u can still use BiMaps but there are other things
like the guava Closeables that Stevo mentioned should be replaced with
equivalent Java 7 constructs.
Switching isDir() to isDirectory() was my fault, will revert that back.
On Fri, Mar 27, 2015 at 1:11 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> BTW guava is in scala cooccurrence so not sure it’s going to be removed
> completely. It’s also used in Hadoop and Spark. Why are we trying to remove
> it when it seems to be the defacto standard? Cooccurrence uses a unique to
> Guava class (HashBiMap) so to remove it is not trivial. I’ve seen scala
> versions but why fragment into implementing out own generic collections. Is
> there a HashBiMap in Java 7, I haven’t heard.
>
> Anyway I don’t think forcing an upgrade to Java 7 is all that big a deal.
> Go ahead and remove guava is you want but be aware that one part is still
> being used.
>
> I’m more concerned with dropping support for hadoop 1.2.1 without
> compelling reasons.
>
> On Mar 27, 2015, at 9:57 AM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> Agree with Stevo. there's another round of code cleanup we need to go thru
> to eliminate guava collection calls and replace with straight Java 7 calls.
> We agreed as part of the last hangout that Java 7 would be the minimal Java
> that we support going forward.
>
> On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com> wrote:
>
>> Question is what is minimal Java that we should require Mahout users to
>> use. It was raised to 1.7 via MAHOUT-1652
>> <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to
> use
>> Java 1.7 APIs, finally. E.g. after level was raised I was recently able
> to
>> eliminate some usage of Guava for closing Closable's with using
>> try-with-resources Java 7 construct. We should minimize dependencies,
> there
>> are IMO too many. Depending more and more on standard libraries of Java
> and
>> Scala helps in that direction. Hopefully we do not wait much longer
> before
>> the level is raised even further to 1.8, so we have even less 3rd party
>> dependencies.
>>
>> On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
>>
>>> It should, Hadoop supports it long term and lots of people stuck there
>>> with projects that haven’t been upgraded (Mahout comes to mind).
>>>
>>> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
>>>
>>> Have to check but I doubt that build supports hadoop 1.x any more.
>>>
>>> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <suneel.marthi@gmail.com
>>
>>> wrote:
>>>
>>>> This is the Java version, gotta use Java 7
>>>>
>>>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
>>>> wrote:
>>>>
>>>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>>>>>
>>>>> Build complains about the move to
>>>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
>>> upped
>>>>> from 1.6 but not sure if that’s what the error is about.
>>>>>
>>>>> I’m on Java 6 no this machine if that matters.
>>>>>
>>>>> Actual error:
>>>>>
>>>>> [INFO] Mahout Build Tools ................................ SUCCESS
>>>> [3.512s]
>>>>> [INFO] Apache Mahout ..................................... SUCCESS
>>>> [0.603s]
>>>>> [INFO] Mahout Math ....................................... FAILURE
>>>> [6.453s]
>>>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
>>>>> [INFO] Mahout Integration ................................ SKIPPED
>>>>> [INFO] Mahout Examples ................................... SKIPPED
>>>>> [INFO] Mahout Release Package ............................ SKIPPED
>>>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
>>>>> [INFO] Mahout Spark bindings ............................. SKIPPED
>>>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
>>>>> [INFO] Mahout H2O backend ................................ SKIPPED
>>>>> [INFO]
>>>>>
>> ------------------------------------------------------------------------
>>>>> [INFO] BUILD FAILURE
>>>>> [INFO]
>>>>>
>> ------------------------------------------------------------------------
>>>>> [INFO] Total time: 11.609s
>>>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
>>>>> [INFO] Final Memory: 24M/310M
>>>>> [INFO]
>>>>>
>> ------------------------------------------------------------------------
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>> (default-compile) on project mahout-math: Fatal error compiling:
>> invalid
>>>>> target release: 1.7 -> [Help 1]
>>>>> [ERROR]
>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the
>>>>> -e switch.
>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>>> [ERROR]
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>
Re: build error
Posted by Suneel Marthi <su...@gmail.com>.
Its not about removing Guava, but trying to minimize Guava usage with the
upgrade to Java 7. Sure u can still use BiMaps but there are other things
like the guava Closeables that Stevo mentioned should be replaced with
equivalent Java 7 constructs.
Switching isDir() to isDirectory() was my fault, will revert that back.
On Fri, Mar 27, 2015 at 1:11 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> BTW guava is in scala cooccurrence so not sure it’s going to be removed
> completely. It’s also used in Hadoop and Spark. Why are we trying to remove
> it when it seems to be the defacto standard? Cooccurrence uses a unique to
> Guava class (HashBiMap) so to remove it is not trivial. I’ve seen scala
> versions but why fragment into implementing out own generic collections. Is
> there a HashBiMap in Java 7, I haven’t heard.
>
> Anyway I don’t think forcing an upgrade to Java 7 is all that big a deal.
> Go ahead and remove guava is you want but be aware that one part is still
> being used.
>
> I’m more concerned with dropping support for hadoop 1.2.1 without
> compelling reasons.
>
> On Mar 27, 2015, at 9:57 AM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> Agree with Stevo. there's another round of code cleanup we need to go thru
> to eliminate guava collection calls and replace with straight Java 7 calls.
> We agreed as part of the last hangout that Java 7 would be the minimal Java
> that we support going forward.
>
> On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com> wrote:
>
> > Question is what is minimal Java that we should require Mahout users to
> > use. It was raised to 1.7 via MAHOUT-1652
> > <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to
> use
> > Java 1.7 APIs, finally. E.g. after level was raised I was recently able
> to
> > eliminate some usage of Guava for closing Closable's with using
> > try-with-resources Java 7 construct. We should minimize dependencies,
> there
> > are IMO too many. Depending more and more on standard libraries of Java
> and
> > Scala helps in that direction. Hopefully we do not wait much longer
> before
> > the level is raised even further to 1.8, so we have even less 3rd party
> > dependencies.
> >
> > On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
> >
> >> It should, Hadoop supports it long term and lots of people stuck there
> >> with projects that haven’t been upgraded (Mahout comes to mind).
> >>
> >> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
> >>
> >> Have to check but I doubt that build supports hadoop 1.x any more.
> >>
> >> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <suneel.marthi@gmail.com
> >
> >> wrote:
> >>
> >>> This is the Java version, gotta use Java 7
> >>>
> >>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> >>> wrote:
> >>>
> >>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
> >>>>
> >>>> Build complains about the move to
> >>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
> >> upped
> >>>> from 1.6 but not sure if that’s what the error is about.
> >>>>
> >>>> I’m on Java 6 no this machine if that matters.
> >>>>
> >>>> Actual error:
> >>>>
> >>>> [INFO] Mahout Build Tools ................................ SUCCESS
> >>> [3.512s]
> >>>> [INFO] Apache Mahout ..................................... SUCCESS
> >>> [0.603s]
> >>>> [INFO] Mahout Math ....................................... FAILURE
> >>> [6.453s]
> >>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> >>>> [INFO] Mahout Integration ................................ SKIPPED
> >>>> [INFO] Mahout Examples ................................... SKIPPED
> >>>> [INFO] Mahout Release Package ............................ SKIPPED
> >>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
> >>>> [INFO] Mahout Spark bindings ............................. SKIPPED
> >>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
> >>>> [INFO] Mahout H2O backend ................................ SKIPPED
> >>>> [INFO]
> >>>>
> > ------------------------------------------------------------------------
> >>>> [INFO] BUILD FAILURE
> >>>> [INFO]
> >>>>
> > ------------------------------------------------------------------------
> >>>> [INFO] Total time: 11.609s
> >>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> >>>> [INFO] Final Memory: 24M/310M
> >>>> [INFO]
> >>>>
> > ------------------------------------------------------------------------
> >>>> [ERROR] Failed to execute goal
> >>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>> (default-compile) on project mahout-math: Fatal error compiling:
> > invalid
> >>>> target release: 1.7 -> [Help 1]
> >>>> [ERROR]
> >>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
> > the
> >>>> -e switch.
> >>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >>>> [ERROR]
> >>>>
> >>>>
> >>>
> >>
> >>
> >
>
>
Re: build error
Posted by Pat Ferrel <pa...@occamsmachete.com>.
BTW guava is in scala cooccurrence so not sure it’s going to be removed completely. It’s also used in Hadoop and Spark. Why are we trying to remove it when it seems to be the defacto standard? Cooccurrence uses a unique to Guava class (HashBiMap) so to remove it is not trivial. I’ve seen scala versions but why fragment into implementing out own generic collections. Is there a HashBiMap in Java 7, I haven’t heard.
Anyway I don’t think forcing an upgrade to Java 7 is all that big a deal. Go ahead and remove guava is you want but be aware that one part is still being used.
I’m more concerned with dropping support for hadoop 1.2.1 without compelling reasons.
On Mar 27, 2015, at 9:57 AM, Suneel Marthi <su...@gmail.com> wrote:
Agree with Stevo. there's another round of code cleanup we need to go thru
to eliminate guava collection calls and replace with straight Java 7 calls.
We agreed as part of the last hangout that Java 7 would be the minimal Java
that we support going forward.
On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com> wrote:
> Question is what is minimal Java that we should require Mahout users to
> use. It was raised to 1.7 via MAHOUT-1652
> <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to use
> Java 1.7 APIs, finally. E.g. after level was raised I was recently able to
> eliminate some usage of Guava for closing Closable's with using
> try-with-resources Java 7 construct. We should minimize dependencies, there
> are IMO too many. Depending more and more on standard libraries of Java and
> Scala helps in that direction. Hopefully we do not wait much longer before
> the level is raised even further to 1.8, so we have even less 3rd party
> dependencies.
>
> On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
>> It should, Hadoop supports it long term and lots of people stuck there
>> with projects that haven’t been upgraded (Mahout comes to mind).
>>
>> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
>>
>> Have to check but I doubt that build supports hadoop 1.x any more.
>>
>> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <su...@gmail.com>
>> wrote:
>>
>>> This is the Java version, gotta use Java 7
>>>
>>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
>>> wrote:
>>>
>>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>>>>
>>>> Build complains about the move to
>>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
>> upped
>>>> from 1.6 but not sure if that’s what the error is about.
>>>>
>>>> I’m on Java 6 no this machine if that matters.
>>>>
>>>> Actual error:
>>>>
>>>> [INFO] Mahout Build Tools ................................ SUCCESS
>>> [3.512s]
>>>> [INFO] Apache Mahout ..................................... SUCCESS
>>> [0.603s]
>>>> [INFO] Mahout Math ....................................... FAILURE
>>> [6.453s]
>>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
>>>> [INFO] Mahout Integration ................................ SKIPPED
>>>> [INFO] Mahout Examples ................................... SKIPPED
>>>> [INFO] Mahout Release Package ............................ SKIPPED
>>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
>>>> [INFO] Mahout Spark bindings ............................. SKIPPED
>>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
>>>> [INFO] Mahout H2O backend ................................ SKIPPED
>>>> [INFO]
>>>>
> ------------------------------------------------------------------------
>>>> [INFO] BUILD FAILURE
>>>> [INFO]
>>>>
> ------------------------------------------------------------------------
>>>> [INFO] Total time: 11.609s
>>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
>>>> [INFO] Final Memory: 24M/310M
>>>> [INFO]
>>>>
> ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>> (default-compile) on project mahout-math: Fatal error compiling:
> invalid
>>>> target release: 1.7 -> [Help 1]
>>>> [ERROR]
>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
>>>> -e switch.
>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>> [ERROR]
>>>>
>>>>
>>>
>>
>>
>
Re: build error
Posted by Suneel Marthi <su...@gmail.com>.
Agree with Stevo. there's another round of code cleanup we need to go thru
to eliminate guava collection calls and replace with straight Java 7 calls.
We agreed as part of the last hangout that Java 7 would be the minimal Java
that we support going forward.
On Fri, Mar 27, 2015 at 12:51 PM, Stevo Slavić <ss...@gmail.com> wrote:
> Question is what is minimal Java that we should require Mahout users to
> use. It was raised to 1.7 via MAHOUT-1652
> <https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to use
> Java 1.7 APIs, finally. E.g. after level was raised I was recently able to
> eliminate some usage of Guava for closing Closable's with using
> try-with-resources Java 7 construct. We should minimize dependencies, there
> are IMO too many. Depending more and more on standard libraries of Java and
> Scala helps in that direction. Hopefully we do not wait much longer before
> the level is raised even further to 1.8, so we have even less 3rd party
> dependencies.
>
> On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> > It should, Hadoop supports it long term and lots of people stuck there
> > with projects that haven’t been upgraded (Mahout comes to mind).
> >
> > On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
> >
> > Have to check but I doubt that build supports hadoop 1.x any more.
> >
> > On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <su...@gmail.com>
> > wrote:
> >
> > > This is the Java version, gotta use Java 7
> > >
> > > On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> > > wrote:
> > >
> > >> Latest source for Spark 1.1.0 and Hadoop 1.2.1
> > >>
> > >> Build complains about the move to
> > >> <maven.compiler.target>1.7</maven.compiler.target> I think this was
> > upped
> > >> from 1.6 but not sure if that’s what the error is about.
> > >>
> > >> I’m on Java 6 no this machine if that matters.
> > >>
> > >> Actual error:
> > >>
> > >> [INFO] Mahout Build Tools ................................ SUCCESS
> > > [3.512s]
> > >> [INFO] Apache Mahout ..................................... SUCCESS
> > > [0.603s]
> > >> [INFO] Mahout Math ....................................... FAILURE
> > > [6.453s]
> > >> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> > >> [INFO] Mahout Integration ................................ SKIPPED
> > >> [INFO] Mahout Examples ................................... SKIPPED
> > >> [INFO] Mahout Release Package ............................ SKIPPED
> > >> [INFO] Mahout Math Scala bindings ........................ SKIPPED
> > >> [INFO] Mahout Spark bindings ............................. SKIPPED
> > >> [INFO] Mahout Spark bindings shell ....................... SKIPPED
> > >> [INFO] Mahout H2O backend ................................ SKIPPED
> > >> [INFO]
> > >>
> ------------------------------------------------------------------------
> > >> [INFO] BUILD FAILURE
> > >> [INFO]
> > >>
> ------------------------------------------------------------------------
> > >> [INFO] Total time: 11.609s
> > >> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> > >> [INFO] Final Memory: 24M/310M
> > >> [INFO]
> > >>
> ------------------------------------------------------------------------
> > >> [ERROR] Failed to execute goal
> > >> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> > >> (default-compile) on project mahout-math: Fatal error compiling:
> invalid
> > >> target release: 1.7 -> [Help 1]
> > >> [ERROR]
> > >> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> > >> -e switch.
> > >> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > >> [ERROR]
> > >>
> > >>
> > >
> >
> >
>
Re: build error
Posted by Stevo Slavić <ss...@gmail.com>.
Question is what is minimal Java that we should require Mahout users to
use. It was raised to 1.7 via MAHOUT-1652
<https://issues.apache.org/jira/browse/MAHOUT-1652>. It enables us to use
Java 1.7 APIs, finally. E.g. after level was raised I was recently able to
eliminate some usage of Guava for closing Closable's with using
try-with-resources Java 7 construct. We should minimize dependencies, there
are IMO too many. Depending more and more on standard libraries of Java and
Scala helps in that direction. Hopefully we do not wait much longer before
the level is raised even further to 1.8, so we have even less 3rd party
dependencies.
On Fri, Mar 27, 2015 at 5:31 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> It should, Hadoop supports it long term and lots of people stuck there
> with projects that haven’t been upgraded (Mahout comes to mind).
>
> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
>
> Have to check but I doubt that build supports hadoop 1.x any more.
>
> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> > This is the Java version, gotta use Java 7
> >
> > On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> > wrote:
> >
> >> Latest source for Spark 1.1.0 and Hadoop 1.2.1
> >>
> >> Build complains about the move to
> >> <maven.compiler.target>1.7</maven.compiler.target> I think this was
> upped
> >> from 1.6 but not sure if that’s what the error is about.
> >>
> >> I’m on Java 6 no this machine if that matters.
> >>
> >> Actual error:
> >>
> >> [INFO] Mahout Build Tools ................................ SUCCESS
> > [3.512s]
> >> [INFO] Apache Mahout ..................................... SUCCESS
> > [0.603s]
> >> [INFO] Mahout Math ....................................... FAILURE
> > [6.453s]
> >> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> >> [INFO] Mahout Integration ................................ SKIPPED
> >> [INFO] Mahout Examples ................................... SKIPPED
> >> [INFO] Mahout Release Package ............................ SKIPPED
> >> [INFO] Mahout Math Scala bindings ........................ SKIPPED
> >> [INFO] Mahout Spark bindings ............................. SKIPPED
> >> [INFO] Mahout Spark bindings shell ....................... SKIPPED
> >> [INFO] Mahout H2O backend ................................ SKIPPED
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] BUILD FAILURE
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Total time: 11.609s
> >> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> >> [INFO] Final Memory: 24M/310M
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [ERROR] Failed to execute goal
> >> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >> (default-compile) on project mahout-math: Fatal error compiling: invalid
> >> target release: 1.7 -> [Help 1]
> >> [ERROR]
> >> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> >> -e switch.
> >> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >> [ERROR]
> >>
> >>
> >
>
>
Re: Require Java 7 and Hadoop 2.x?
Posted by Ted Dunning <te...@gmail.com>.
There are subtle API incompatibilities.
Unfortunate. But true.
On Fri, Mar 27, 2015 at 10:16 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> As I said in the other thread forcing Java 7 is not as big a deal as
> forcing Hadoop 1.2.1. Is there some new part of 2.X that we need? Or some
> forced API incompatability?
>
>
> On Mar 27, 2015, at 9:58 AM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> TED??? please jump in.
>
> On Fri, Mar 27, 2015 at 12:54 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
>
> > Aren’t current Mahout 0.9 users on hadoop 1.2.1 by definition? Probably
> > most on Java 6 too.
> >
> > Unless there is some strong reason it seems like we should support both
> of
> > those for at least one release, shouldn’t we?
> >
> > I have a hadoop 1.2.1 cluster, which has a hadoop job that is not Hadoop
> 2
> > compatible so I’m stuck there for the time being. Compiling Mahout for
> this
> > now gives an error over the H2 API “isDirectory”, which I think used to
> be
> > “isDir” for H1. Has that API been deprecated in H2? Are we forced to
> chose
> > either/or?
> >
> >
> > On Mar 27, 2015, at 9:31 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> >
> > It should, Hadoop supports it long term and lots of people stuck there
> > with projects that haven’t been upgraded (Mahout comes to mind).
> >
> > On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
> >
> > Have to check but I doubt that build supports hadoop 1.x any more.
> >
> > On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <su...@gmail.com>
> > wrote:
> >
> >> This is the Java version, gotta use Java 7
> >>
> >> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> >> wrote:
> >>
> >>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
> >>>
> >>> Build complains about the move to
> >>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
> > upped
> >>> from 1.6 but not sure if that’s what the error is about.
> >>>
> >>> I’m on Java 6 no this machine if that matters.
> >>>
> >>> Actual error:
> >>>
> >>> [INFO] Mahout Build Tools ................................ SUCCESS
> >> [3.512s]
> >>> [INFO] Apache Mahout ..................................... SUCCESS
> >> [0.603s]
> >>> [INFO] Mahout Math ....................................... FAILURE
> >> [6.453s]
> >>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> >>> [INFO] Mahout Integration ................................ SKIPPED
> >>> [INFO] Mahout Examples ................................... SKIPPED
> >>> [INFO] Mahout Release Package ............................ SKIPPED
> >>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
> >>> [INFO] Mahout Spark bindings ............................. SKIPPED
> >>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
> >>> [INFO] Mahout H2O backend ................................ SKIPPED
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [INFO] BUILD FAILURE
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [INFO] Total time: 11.609s
> >>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> >>> [INFO] Final Memory: 24M/310M
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [ERROR] Failed to execute goal
> >>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>> (default-compile) on project mahout-math: Fatal error compiling:
> invalid
> >>> target release: 1.7 -> [Help 1]
> >>> [ERROR]
> >>> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> >>> -e switch.
> >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >>> [ERROR]
> >>>
> >>>
> >>
> >
> >
> >
>
>
Re: Require Java 7 and Hadoop 2.x?
Posted by Pat Ferrel <pa...@occamsmachete.com>.
As I said in the other thread forcing Java 7 is not as big a deal as forcing Hadoop 1.2.1. Is there some new part of 2.X that we need? Or some forced API incompatability?
On Mar 27, 2015, at 9:58 AM, Suneel Marthi <su...@gmail.com> wrote:
TED??? please jump in.
On Fri, Mar 27, 2015 at 12:54 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> Aren’t current Mahout 0.9 users on hadoop 1.2.1 by definition? Probably
> most on Java 6 too.
>
> Unless there is some strong reason it seems like we should support both of
> those for at least one release, shouldn’t we?
>
> I have a hadoop 1.2.1 cluster, which has a hadoop job that is not Hadoop 2
> compatible so I’m stuck there for the time being. Compiling Mahout for this
> now gives an error over the H2 API “isDirectory”, which I think used to be
> “isDir” for H1. Has that API been deprecated in H2? Are we forced to chose
> either/or?
>
>
> On Mar 27, 2015, at 9:31 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> It should, Hadoop supports it long term and lots of people stuck there
> with projects that haven’t been upgraded (Mahout comes to mind).
>
> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
>
> Have to check but I doubt that build supports hadoop 1.x any more.
>
> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
>> This is the Java version, gotta use Java 7
>>
>> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
>> wrote:
>>
>>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>>>
>>> Build complains about the move to
>>> <maven.compiler.target>1.7</maven.compiler.target> I think this was
> upped
>>> from 1.6 but not sure if that’s what the error is about.
>>>
>>> I’m on Java 6 no this machine if that matters.
>>>
>>> Actual error:
>>>
>>> [INFO] Mahout Build Tools ................................ SUCCESS
>> [3.512s]
>>> [INFO] Apache Mahout ..................................... SUCCESS
>> [0.603s]
>>> [INFO] Mahout Math ....................................... FAILURE
>> [6.453s]
>>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
>>> [INFO] Mahout Integration ................................ SKIPPED
>>> [INFO] Mahout Examples ................................... SKIPPED
>>> [INFO] Mahout Release Package ............................ SKIPPED
>>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
>>> [INFO] Mahout Spark bindings ............................. SKIPPED
>>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
>>> [INFO] Mahout H2O backend ................................ SKIPPED
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 11.609s
>>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
>>> [INFO] Final Memory: 24M/310M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>> (default-compile) on project mahout-math: Fatal error compiling: invalid
>>> target release: 1.7 -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>> -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>>
>>>
>>
>
>
>
Re: Require Java 7 and Hadoop 2.x?
Posted by Ted Dunning <te...@gmail.com>.
I haven't heard of many people still on Java 6. *(except in this thread,
of course). It shouldn't be a big deal forcing that.
Hadoop 2 is probably close enough that we should be able to jump forward
with our next release. I certainly know of a significant number of
non-upgraded installs, but adding a bit more pressure to upgrade would be a
good thing for the world at large, probably.
On Fri, Mar 27, 2015 at 9:58 AM, Suneel Marthi <su...@gmail.com>
wrote:
> TED??? please jump in.
>
> On Fri, Mar 27, 2015 at 12:54 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
>
> > Aren’t current Mahout 0.9 users on hadoop 1.2.1 by definition? Probably
> > most on Java 6 too.
> >
> > Unless there is some strong reason it seems like we should support both
> of
> > those for at least one release, shouldn’t we?
> >
> > I have a hadoop 1.2.1 cluster, which has a hadoop job that is not Hadoop
> 2
> > compatible so I’m stuck there for the time being. Compiling Mahout for
> this
> > now gives an error over the H2 API “isDirectory”, which I think used to
> be
> > “isDir” for H1. Has that API been deprecated in H2? Are we forced to
> chose
> > either/or?
> >
> >
> > On Mar 27, 2015, at 9:31 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> >
> > It should, Hadoop supports it long term and lots of people stuck there
> > with projects that haven’t been upgraded (Mahout comes to mind).
> >
> > On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
> >
> > Have to check but I doubt that build supports hadoop 1.x any more.
> >
> > On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <su...@gmail.com>
> > wrote:
> >
> > > This is the Java version, gotta use Java 7
> > >
> > > On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> > > wrote:
> > >
> > >> Latest source for Spark 1.1.0 and Hadoop 1.2.1
> > >>
> > >> Build complains about the move to
> > >> <maven.compiler.target>1.7</maven.compiler.target> I think this was
> > upped
> > >> from 1.6 but not sure if that’s what the error is about.
> > >>
> > >> I’m on Java 6 no this machine if that matters.
> > >>
> > >> Actual error:
> > >>
> > >> [INFO] Mahout Build Tools ................................ SUCCESS
> > > [3.512s]
> > >> [INFO] Apache Mahout ..................................... SUCCESS
> > > [0.603s]
> > >> [INFO] Mahout Math ....................................... FAILURE
> > > [6.453s]
> > >> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> > >> [INFO] Mahout Integration ................................ SKIPPED
> > >> [INFO] Mahout Examples ................................... SKIPPED
> > >> [INFO] Mahout Release Package ............................ SKIPPED
> > >> [INFO] Mahout Math Scala bindings ........................ SKIPPED
> > >> [INFO] Mahout Spark bindings ............................. SKIPPED
> > >> [INFO] Mahout Spark bindings shell ....................... SKIPPED
> > >> [INFO] Mahout H2O backend ................................ SKIPPED
> > >> [INFO]
> > >>
> ------------------------------------------------------------------------
> > >> [INFO] BUILD FAILURE
> > >> [INFO]
> > >>
> ------------------------------------------------------------------------
> > >> [INFO] Total time: 11.609s
> > >> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> > >> [INFO] Final Memory: 24M/310M
> > >> [INFO]
> > >>
> ------------------------------------------------------------------------
> > >> [ERROR] Failed to execute goal
> > >> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> > >> (default-compile) on project mahout-math: Fatal error compiling:
> invalid
> > >> target release: 1.7 -> [Help 1]
> > >> [ERROR]
> > >> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> > >> -e switch.
> > >> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > >> [ERROR]
> > >>
> > >>
> > >
> >
> >
> >
>
Re: Require Java 7 and Hadoop 2.x?
Posted by Suneel Marthi <su...@gmail.com>.
TED??? please jump in.
On Fri, Mar 27, 2015 at 12:54 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> Aren’t current Mahout 0.9 users on hadoop 1.2.1 by definition? Probably
> most on Java 6 too.
>
> Unless there is some strong reason it seems like we should support both of
> those for at least one release, shouldn’t we?
>
> I have a hadoop 1.2.1 cluster, which has a hadoop job that is not Hadoop 2
> compatible so I’m stuck there for the time being. Compiling Mahout for this
> now gives an error over the H2 API “isDirectory”, which I think used to be
> “isDir” for H1. Has that API been deprecated in H2? Are we forced to chose
> either/or?
>
>
> On Mar 27, 2015, at 9:31 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> It should, Hadoop supports it long term and lots of people stuck there
> with projects that haven’t been upgraded (Mahout comes to mind).
>
> On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
>
> Have to check but I doubt that build supports hadoop 1.x any more.
>
> On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> > This is the Java version, gotta use Java 7
> >
> > On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> > wrote:
> >
> >> Latest source for Spark 1.1.0 and Hadoop 1.2.1
> >>
> >> Build complains about the move to
> >> <maven.compiler.target>1.7</maven.compiler.target> I think this was
> upped
> >> from 1.6 but not sure if that’s what the error is about.
> >>
> >> I’m on Java 6 no this machine if that matters.
> >>
> >> Actual error:
> >>
> >> [INFO] Mahout Build Tools ................................ SUCCESS
> > [3.512s]
> >> [INFO] Apache Mahout ..................................... SUCCESS
> > [0.603s]
> >> [INFO] Mahout Math ....................................... FAILURE
> > [6.453s]
> >> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> >> [INFO] Mahout Integration ................................ SKIPPED
> >> [INFO] Mahout Examples ................................... SKIPPED
> >> [INFO] Mahout Release Package ............................ SKIPPED
> >> [INFO] Mahout Math Scala bindings ........................ SKIPPED
> >> [INFO] Mahout Spark bindings ............................. SKIPPED
> >> [INFO] Mahout Spark bindings shell ....................... SKIPPED
> >> [INFO] Mahout H2O backend ................................ SKIPPED
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] BUILD FAILURE
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Total time: 11.609s
> >> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> >> [INFO] Final Memory: 24M/310M
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [ERROR] Failed to execute goal
> >> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >> (default-compile) on project mahout-math: Fatal error compiling: invalid
> >> target release: 1.7 -> [Help 1]
> >> [ERROR]
> >> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> >> -e switch.
> >> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >> [ERROR]
> >>
> >>
> >
>
>
>
Re: Require Java 7 and Hadoop 2.x?
Posted by Pat Ferrel <pa...@occamsmachete.com>.
I’m all for adding any needed support for java 7 and making Hadoop 2 the default but do they also have to be required?
On Mar 27, 2015, at 9:54 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
Aren’t current Mahout 0.9 users on hadoop 1.2.1 by definition? Probably most on Java 6 too.
Unless there is some strong reason it seems like we should support both of those for at least one release, shouldn’t we?
I have a hadoop 1.2.1 cluster, which has a hadoop job that is not Hadoop 2 compatible so I’m stuck there for the time being. Compiling Mahout for this now gives an error over the H2 API “isDirectory”, which I think used to be “isDir” for H1. Has that API been deprecated in H2? Are we forced to chose either/or?
On Mar 27, 2015, at 9:31 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
It should, Hadoop supports it long term and lots of people stuck there with projects that haven’t been upgraded (Mahout comes to mind).
On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
Have to check but I doubt that build supports hadoop 1.x any more.
On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <su...@gmail.com>
wrote:
> This is the Java version, gotta use Java 7
>
> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
>
>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>>
>> Build complains about the move to
>> <maven.compiler.target>1.7</maven.compiler.target> I think this was upped
>> from 1.6 but not sure if that’s what the error is about.
>>
>> I’m on Java 6 no this machine if that matters.
>>
>> Actual error:
>>
>> [INFO] Mahout Build Tools ................................ SUCCESS
> [3.512s]
>> [INFO] Apache Mahout ..................................... SUCCESS
> [0.603s]
>> [INFO] Mahout Math ....................................... FAILURE
> [6.453s]
>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
>> [INFO] Mahout Integration ................................ SKIPPED
>> [INFO] Mahout Examples ................................... SKIPPED
>> [INFO] Mahout Release Package ............................ SKIPPED
>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
>> [INFO] Mahout Spark bindings ............................. SKIPPED
>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
>> [INFO] Mahout H2O backend ................................ SKIPPED
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 11.609s
>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
>> [INFO] Final Memory: 24M/310M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>> (default-compile) on project mahout-math: Fatal error compiling: invalid
>> target release: 1.7 -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>>
>>
>
Require Java 7 and Hadoop 2.x?
Posted by Pat Ferrel <pa...@occamsmachete.com>.
Aren’t current Mahout 0.9 users on hadoop 1.2.1 by definition? Probably most on Java 6 too.
Unless there is some strong reason it seems like we should support both of those for at least one release, shouldn’t we?
I have a hadoop 1.2.1 cluster, which has a hadoop job that is not Hadoop 2 compatible so I’m stuck there for the time being. Compiling Mahout for this now gives an error over the H2 API “isDirectory”, which I think used to be “isDir” for H1. Has that API been deprecated in H2? Are we forced to chose either/or?
On Mar 27, 2015, at 9:31 AM, Pat Ferrel <pa...@occamsmachete.com> wrote:
It should, Hadoop supports it long term and lots of people stuck there with projects that haven’t been upgraded (Mahout comes to mind).
On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
Have to check but I doubt that build supports hadoop 1.x any more.
On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <su...@gmail.com>
wrote:
> This is the Java version, gotta use Java 7
>
> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
>
>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>>
>> Build complains about the move to
>> <maven.compiler.target>1.7</maven.compiler.target> I think this was upped
>> from 1.6 but not sure if that’s what the error is about.
>>
>> I’m on Java 6 no this machine if that matters.
>>
>> Actual error:
>>
>> [INFO] Mahout Build Tools ................................ SUCCESS
> [3.512s]
>> [INFO] Apache Mahout ..................................... SUCCESS
> [0.603s]
>> [INFO] Mahout Math ....................................... FAILURE
> [6.453s]
>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
>> [INFO] Mahout Integration ................................ SKIPPED
>> [INFO] Mahout Examples ................................... SKIPPED
>> [INFO] Mahout Release Package ............................ SKIPPED
>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
>> [INFO] Mahout Spark bindings ............................. SKIPPED
>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
>> [INFO] Mahout H2O backend ................................ SKIPPED
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 11.609s
>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
>> [INFO] Final Memory: 24M/310M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>> (default-compile) on project mahout-math: Fatal error compiling: invalid
>> target release: 1.7 -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>>
>>
>
Re: build error
Posted by Pat Ferrel <pa...@occamsmachete.com>.
It should, Hadoop supports it long term and lots of people stuck there with projects that haven’t been upgraded (Mahout comes to mind).
On Mar 27, 2015, at 9:26 AM, Stevo Slavić <ss...@gmail.com> wrote:
Have to check but I doubt that build supports hadoop 1.x any more.
On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <su...@gmail.com>
wrote:
> This is the Java version, gotta use Java 7
>
> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
>
>> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>>
>> Build complains about the move to
>> <maven.compiler.target>1.7</maven.compiler.target> I think this was upped
>> from 1.6 but not sure if that’s what the error is about.
>>
>> I’m on Java 6 no this machine if that matters.
>>
>> Actual error:
>>
>> [INFO] Mahout Build Tools ................................ SUCCESS
> [3.512s]
>> [INFO] Apache Mahout ..................................... SUCCESS
> [0.603s]
>> [INFO] Mahout Math ....................................... FAILURE
> [6.453s]
>> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
>> [INFO] Mahout Integration ................................ SKIPPED
>> [INFO] Mahout Examples ................................... SKIPPED
>> [INFO] Mahout Release Package ............................ SKIPPED
>> [INFO] Mahout Math Scala bindings ........................ SKIPPED
>> [INFO] Mahout Spark bindings ............................. SKIPPED
>> [INFO] Mahout Spark bindings shell ....................... SKIPPED
>> [INFO] Mahout H2O backend ................................ SKIPPED
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 11.609s
>> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
>> [INFO] Final Memory: 24M/310M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>> (default-compile) on project mahout-math: Fatal error compiling: invalid
>> target release: 1.7 -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>>
>>
>
Re: build error
Posted by Stevo Slavić <ss...@gmail.com>.
Have to check but I doubt that build supports hadoop 1.x any more.
On Fri, Mar 27, 2015 at 5:15 PM, Suneel Marthi <su...@gmail.com>
wrote:
> This is the Java version, gotta use Java 7
>
> On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com>
> wrote:
>
> > Latest source for Spark 1.1.0 and Hadoop 1.2.1
> >
> > Build complains about the move to
> > <maven.compiler.target>1.7</maven.compiler.target> I think this was upped
> > from 1.6 but not sure if that’s what the error is about.
> >
> > I’m on Java 6 no this machine if that matters.
> >
> > Actual error:
> >
> > [INFO] Mahout Build Tools ................................ SUCCESS
> [3.512s]
> > [INFO] Apache Mahout ..................................... SUCCESS
> [0.603s]
> > [INFO] Mahout Math ....................................... FAILURE
> [6.453s]
> > [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> > [INFO] Mahout Integration ................................ SKIPPED
> > [INFO] Mahout Examples ................................... SKIPPED
> > [INFO] Mahout Release Package ............................ SKIPPED
> > [INFO] Mahout Math Scala bindings ........................ SKIPPED
> > [INFO] Mahout Spark bindings ............................. SKIPPED
> > [INFO] Mahout Spark bindings shell ....................... SKIPPED
> > [INFO] Mahout H2O backend ................................ SKIPPED
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 11.609s
> > [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> > [INFO] Final Memory: 24M/310M
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> > (default-compile) on project mahout-math: Fatal error compiling: invalid
> > target release: 1.7 -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> > -e switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> >
> >
>
Re: build error
Posted by Suneel Marthi <su...@gmail.com>.
This is the Java version, gotta use Java 7
On Fri, Mar 27, 2015 at 12:08 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> Latest source for Spark 1.1.0 and Hadoop 1.2.1
>
> Build complains about the move to
> <maven.compiler.target>1.7</maven.compiler.target> I think this was upped
> from 1.6 but not sure if that’s what the error is about.
>
> I’m on Java 6 no this machine if that matters.
>
> Actual error:
>
> [INFO] Mahout Build Tools ................................ SUCCESS [3.512s]
> [INFO] Apache Mahout ..................................... SUCCESS [0.603s]
> [INFO] Mahout Math ....................................... FAILURE [6.453s]
> [INFO] Mahout MapReduce Legacy ........................... SKIPPED
> [INFO] Mahout Integration ................................ SKIPPED
> [INFO] Mahout Examples ................................... SKIPPED
> [INFO] Mahout Release Package ............................ SKIPPED
> [INFO] Mahout Math Scala bindings ........................ SKIPPED
> [INFO] Mahout Spark bindings ............................. SKIPPED
> [INFO] Mahout Spark bindings shell ....................... SKIPPED
> [INFO] Mahout H2O backend ................................ SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 11.609s
> [INFO] Finished at: Fri Mar 27 08:55:35 PDT 2015
> [INFO] Final Memory: 24M/310M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> (default-compile) on project mahout-math: Fatal error compiling: invalid
> target release: 1.7 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
>
>