I was suffering with this problem too, but I solved it by adding the Jetty
dependency into Mahout examples by doing the following steps:
1. Copy the Jetty dependency into mahout examples pom.xml
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1.26</version>
</plugin>
2. Copy integration's webapp folder into mahout examples
$ mkdir -p mahout/examples/src/main/webapp/WEB-INF
$ cp mahout/integration/src/main/webapp/WEB-INF/web.xml
mahout/examples/src/main/webapp/WEB-INF/web.xml
3. Run Jetty inside the example submodule
$ cd mahout/examples
$ mvn:jetty
4. Access it in a browser by using the following URL:
http://<your_ip>:8080/mahout-examples/RecommenderServlet?userID=1<http://10.224.195.42:8080/mahout-examples/RecommenderServlet?userID=1>
I suspect that this problem is happening because forgot to move the webapp
folder to the examples dir and add the Jetty dependency when the GroupLens
example moved to the examples submodule. A JIRA ticket could be opened to
address that.
On 07/24/2013 12:23 AM, Jason Lee wrote:
@*Sean* & @Manuel, Thanks for your replies.
I solved this problem by adding a lower version of mahout-examples to
dependencies of mahout-integration, since maven is identify a unique
project by its groupId, artifactId and version, so we can avoid Maven
Circular Dependency by specify a different version of A to dependency of B
since B is dependency of A.
For example, Now i am run mahout 0.9-SNAPSHOT, there already has a
dependency in *mahout-examples/pom.xml* like this:
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>mahout-integration</artifactId>
</dependency>
The version of this dependency is 0.9-SNAPSHOT implicitly. So, if i just
add below code into *mahout-integration/pom.xml*:
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>mahout-examples</artifactId>
</dependency>
The Maven Circular Dependency problem will arise. But if we specify a
different version of mahout-examples as mahout-integration's
dependency(lower that 0.9, for example, 0.8), that will be fine:
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>mahout-examples</artifactId>
<version>0.8</version>
</dependency>
Regards.
- Jason
On Fri, Jul 19, 2013 at 11:13 PM, Manuel Blechschmidt <
[email protected]<mailto:[email protected]>> wrote:
Hi Jason,
if it is just about to get something up and running as fast as possible I
would recommend my github project:
It uses a glassfish 3.1.2 server but it is bundled. So you should get it
running with the following 3 commands:
git clone git://github.com/ManuelB/facebook-recommender-demo.git
cd facebook-recommender-demo
mvn install
mvn embedded-glassfish:run
https://github.com/ManuelB/facebook-recommender-demo
/Manuel
Am 19.07.2013 um 15:56 schrieb Sean Owen:
I think this is just old, and now you need to run from examples/. I
admit I don't know if this Jetty-based demo is still working or in the
project though. If so it should just be deleted.
On Fri, Jul 19, 2013 at 4:21 AM, Jason Lee
<[email protected]><mailto:[email protected]> wrote:
Hi, guys,
I was trying to following the doc
below:
https://cwiki.apache.org/confluence/display/MAHOUT/Recommender+Documentation
When I run jetty:run under *mahout-integration*, I am getting a
ClassNotFoundException:
org.apache.mahout.cf.taste.example.grouplens.GroupLensRecommender.
I noticed that GroupLensRecommender is belong to *mahout-examples*, so
i attempt add mahout-examples to dependencies of mahout-integration;
But, unfortunately, there already has a reversed dependency between
mahout-examples & mahout-integration, and Circular Dependency is not
allowed in maven, so i failed.
Btw, i am running mahout 0.8.
--
Manuel Blechschmidt
M.Sc. IT Systems Engineering
Dortustr. 57
14467 Potsdam
Mobil: 0173/6322621
Twitter: http://twitter.com/Manuel_B
--
Atenciosamente
Helder Martins
Arquitetura do Portal e Sistemas de Backend
+55 (51) 3284-4475
Terra
________________________________
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
podem conter informação privilegiada ou confidencial e são de uso exclusivo da
pessoa ou entidade de destino. Se não for destinatário desta mensagem, fica
notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização
pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem
por engano, pedimos que nos o comunique imediatamente por esta mesma via e, em
seguida, apague-a.
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede
contener información privilegiada o confidencial y es para uso exclusivo de la
persona o entidad de destino. Si no es usted él destinatario indicado, queda
notificado de que la lectura, utilización, divulgación y/o copia sin
autorización puede estar prohibida en virtud de la legislación vigente. Si ha
recibido este mensaje por error, le pedimos que nos lo comunique inmediatamente
por esta misma vía y proceda a su exclusión.
The information contained in this transmissión is privileged and confidential
information intended only for the use of the individual or entity named above.
If the reader of this message is not the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this communication
is strictly prohibited. If you have received this transmission in error, do not
read it. Please immediately reply to the sender that you have received this
communication in error and then delete it.
