Hi all,
I'm very excited about using recommendation system in my web apps and am new
to Mahout.
I tried installing it and everything seemed to install smoothly until I ran
this command: mvn jetty:run-war
Jetty was started up, but when I tried to access http://mydomain.com:8080/
this is what I get:
[
https://issues.apache.org/jira/browse/MAHOUT-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Scholten updated MAHOUT-508:
--
Attachment: MAHOUT-508.patch
> ARFF Driver configuration for mahout script missing
> --
[
https://issues.apache.org/jira/browse/MAHOUT-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Scholten updated MAHOUT-508:
--
Affects Version/s: 0.4
Status: Patch Available (was: Reopened)
> ARFF Driver co
[
https://issues.apache.org/jira/browse/MAHOUT-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Scholten reopened MAHOUT-508:
---
I noticed the property file is now located under mahout/conf so I created a
patch that moved to
[
https://issues.apache.org/jira/browse/MAHOUT-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Scholten updated MAHOUT-540:
--
Status: Patch Available (was: Open)
> Integration test for the DocumentProcessor
> ---
[
https://issues.apache.org/jira/browse/MAHOUT-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Scholten updated MAHOUT-540:
--
Attachment: DocumentProcessorTest.patch
> Integration test for the DocumentProcessor
>
Integration test for the DocumentProcessor
--
Key: MAHOUT-540
URL: https://issues.apache.org/jira/browse/MAHOUT-540
Project: Mahout
Issue Type: Improvement
Components: Clustering
Affects
I didn't get a strong sense from the Hadoop community that 0.21 is all that
well baked. To quote the website:
"This release contains many improvements, new features, bug fixes and
optimizations. It has not undergone testing at scale and should not be
considered stable or suitable for production
Yes, that's the right thing to do.
On Fri, Nov 5, 2010 at 8:50 AM, Drew Farris wrote:
> It might be as easy as changing the maven version in Hudson from
> 2.0.11 to 2.2.1 -- I'll give it a try
>
> On Fri, Nov 5, 2010 at 5:52 AM, Sean Owen wrote:
>> [INFO] Error resolving version for
>> 'org.apac
It might be as easy as changing the maven version in Hudson from
2.0.11 to 2.2.1 -- I'll give it a try
On Fri, Nov 5, 2010 at 5:52 AM, Sean Owen wrote:
> [INFO] Error resolving version for
> 'org.apache.maven.plugins:maven-assembly-plugin': Plugin requires Maven
> version 2.0.11
>
> I've seen thi
[INFO] Error resolving version for
'org.apache.maven.plugins:maven-assembly-plugin': Plugin requires Maven
version 2.0.11
I've seen this one a few times now, is there an easy fix, like just letting
it pick its version?
11 matches
Mail list logo