mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen" <>
Subject Re: [jira] Updated: (MAHOUT-94) Make the Taste Demo more automated.
Date Sun, 30 Nov 2008 14:51:30 GMT
Does Jetty need that defaultweb.xml file? all the necessary
configuration should be set in the generated web.xml file already, and
I suppose it'd be nicer to not configure, say, connectors and session
ID logic since they aren't needed. But if Jetty wants it, it wants it.

Also looks like the expected location of ratings.dat was changed?
Unless I am forgetting something the files are still expected to be
next to the code, where they were before. Not a big deal where it is,
just needs to be consistent of course. The build files don't expect it
in this new root-directory location right now for instance.

On Sun, Nov 30, 2008 at 3:08 AM, Grant Ingersoll (JIRA) <> wrote:
>     [
> Grant Ingersoll updated MAHOUT-94:
> ----------------------------------
>    Attachment: MAHOUT-94.patch
> Here's some updates
>> Make the Taste Demo more automated.
>> ------------------------------------
>>                 Key: MAHOUT-94
>>                 URL:
>>             Project: Mahout
>>          Issue Type: Improvement
>>            Reporter: Grant Ingersoll
>>            Assignee: Grant Ingersoll
>>            Priority: Minor
>>         Attachments: axis.tar, jetty.tar, MAHOUT-94.patch, MAHOUT-94.patch
>> Would be really cool if the Taste Demo (
was easier to get up and going.  For instance, we could have an Ant task that automatically
gets the data and puts it into the work directory just like we do for Reuters, Wikipedia and
Twenty News.  Then, we could also ship Jetty w/ the examples, such that one just needs to
do {code}java -jar start.jar{code} to fire up the WAR and have it running (Solr does this)
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.

View raw message