I am -1 for a change with out a bit more details.
I think having two options (source+doc and source+doc+dependent jars)
would make everybody happy.
Having the source in the second option only adds a small amount to the
size, compared to (a typical set of) dependent jars.
[snip]
Also, I have some question about the second option due largely to my
maven
inexperience. Is there an easy way to tell maven that jars *might( be
present locally and that it doesn't need to download them? It would
seem
really a bad idea to have to change the pom for different
distributions.
This is how Maven operates by default. You have a local cache
(typically ~/.m2) that's used for all versioned jars.
Snapshot jars require checks against the source repo, but that's not a
common case.
And the build still works (with warnings) if your network is down, as
long as you have some version of the snapshot jar available.
-- Ken
To argue against my own point, is it the sense of the group that the
source-only need is satisfied by svn access?
On Wed, Dec 9, 2009 at 11:53 AM, Patterson, Josh
<[email protected]>wrote:
I think this is probably a good idea from a base "simplest use case"
viewpoint;
If I come along and just want to try out something in Mahout as
quickly
as possible, I could download the jars and give something a quick
try.
If it works out for me, then that draws me further into thinking out
looking at the actual source code and possibly contributing later
down
the road. Datamining, Hadoop, et al are complex enough for the
average
user --- why not provide an option that caters to the casual crowd
and
lowers that barrier to entry just a little?
Its trivial to offer the jars and the rest of us can continue to use
Maven/Ant to build as we like.
Josh
-----Original Message-----
From: Jake Mannix [mailto:[email protected]]
Sent: Wednesday, December 09, 2009 2:23 PM
To: [email protected]
Subject: Re: download mahout-0.2 release
So another thought on this: should we just provide jars as part of a
distribution
via a simple link on lucene.apache.org/mahout?
So that people don't need to build from source?
I mean, if we want to include artifacts, why not just put them on the
site
for download?
-jake
On Wed, Dec 9, 2009 at 10:33 AM, Drew Farris <[email protected]>
wrote:
+1 here too -- I opened
https://issues.apache.org/jira/browse/MAHOUT-215to
track it.
On Wed, Dec 9, 2009 at 11:55 AM, F.Ozgur Catak
<[email protected]
wrote:
+1 :)
On Wed, Dec 9, 2009 at 6:48 PM, Jake Mannix <[email protected]>
wrote:
On Wed, Dec 9, 2009 at 7:58 AM, Isabel Drost <[email protected]>
wrote:
On Tue Sean Owen <[email protected]> wrote:
Yeah I think we should just include the .jars next time for
convenience.
+1
+1 from me as well.
-jake
--
Ted Dunning, CTO
DeepDyve
--------------------------------------------
Ken Krugler
+1 530-210-6378
http://bixolabs.com
e l a s t i c w e b m i n i n g
