Mailing-List: contact mahout-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mahout-dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of robin.anil@gmail.com
 designates 209.85.222.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=moODaJR/pr+/binCkAWZAj2yhhX8MIUxH55+ha/rKnVYn7eoMjtEWfTSTgVdSeoehu
         xpBXgXyBwgtXuRMlCTfmolxjOpd99V9f7LQBU/6q3lgTkHbgAdM+aD9Djop4mxV3pSnG
         bDBnyP/nUoysS6knqDPhS8irUAeaXhthDo44Y=
MIME-Version: 1.0
In-Reply-To: <8f8e14c41002141522t3e23488ame64d1f182d66be76@mail.gmail.com>
References: <E13AB68C-8BC0-43A8-B60B-F10DF0B06CA9@apache.org>
	<e2e029611002141407me44e363w4a78a661ea99f08f@mail.gmail.com>
	<954CD425-24DD-469A-90CE-F2870B539632@apache.org>
 <e2e029611002141431x6a3fd9bdk25ecc44935b7626e@mail.gmail.com>
	<2CF49E96-76D4-409C-864F-D0A472177877@apache.org>
 <8f8e14c41002141500uab182bbxd30c1c2f9e35bdd2@mail.gmail.com>
	<e2e029611002141503q5e861582k9ffc3651d2e2678f@mail.gmail.com>
	<8f8e14c41002141522t3e23488ame64d1f182d66be76@mail.gmail.com>
From: Robin Anil <robin.anil@gmail.com>
Date: Mon, 15 Feb 2010 10:03:55 +0530
Message-ID: <7d7600c51002142033x2269db29i72c04b74e69c1ff0@mail.gmail.com>
Subject: Re: Taste demo not working
To: mahout-dev@lucene.apache.org
Content-Type: multipart/alternative; boundary=000e0cd1ad4a2ce7e2047f9c2152

--000e0cd1ad4a2ce7e2047f9c2152
Content-Type: text/plain; charset=UTF-8

Many places the classes are instantiated at runtime from a
string. "org.apache.*.*.*.StandardAnalyzer".
 Thats the case when maven fails. Jets3 patch was doing the exact same
thing. In mahout's case we can enforce static checking by making sure the
package is referenced directly in some test.


On Mon, Feb 15, 2010 at 4:52 AM, Drew Farris <drew.farris@gmail.com> wrote:

> On Sun, Feb 14, 2010 at 6:03 PM, Sean Owen <srowen@gmail.com> wrote:
> > Could be a dumb question, but aren't these sorts of dependencies
> > necessarily things that particular users of Mahout/Hadoop depend on,
> > not Mahout? even at runtime? Kind of like depending on a particular
> > SLF4J binding to a logger.
>
> It depends, mvn will warn that jets3t is unused, but the code in
> MAHOUT-249 depends on it because it advertises the ability to write to
> S3 in its command-line options. Do we want to add the caveat that if
> you want to use s3 that you (as a user) have to provide the jar?
> That's the one example I'm aware of, are there others, I don't know.
>
> One could say that because there are utilities/examples that don't run
> using the hadoop driver but do use the Hadoop FS abstraction that we
> must include all of the jars for filesystems supported by that
> abstraction, but I'm not certain that I agree with that statement or
> not.
>
> I believe the Hadoop FS is probably the only case where we'd need to
> consider this but I'm not 100% certain. The logger binding is a
> somewhat similar class of problem.
>
> Drew
>

--000e0cd1ad4a2ce7e2047f9c2152--