Before you do, could you check that NutchGora passes ant test successfully. I just tried and got an error related to the parse-tika tests. Am about to open a JIRA to update to the latest version of Tika for NutchGora which should fix the problem and put it at the same level as trunk
J On 15 June 2012 10:01, Lewis John Mcgibbney <[email protected]>wrote:ly > I'll push this in an hour or so guys. > > Thanks for the input. > > Lewis > > > On Fri, Jun 15, 2012 at 9:39 AM, Julien Nioche < > [email protected]> wrote: > >> +1 >> >> >> On 15 June 2012 09:00, Ferdy Galema <[email protected]> wrote: >> >>> Agree with only releasing src. >>> >>> >>> On Thu, Jun 14, 2012 at 11:32 PM, Mattmann, Chris A (388J) < >>> [email protected]> wrote: >>> >>>> Or just not ship a bin release at all. Src is the only thing we >>>> really VOTE on legally though bin is provided for convenience purposes. >>>> Will type more on this later... >>>> >>>> Sent from my iPhone >>>> >>>> On Jun 14, 2012, at 2:18 PM, "Lewis John Mcgibbney" < >>>> [email protected]> wrote: >>>> >>>> Hi Julien, >>>> >>>> Do you suggest with the binary release that we simply open up all >>>> gora-* deps and ship it with every jar available? >>>> >>>> Lewis >>>> >>>> On Thu, Jun 14, 2012 at 9:39 PM, Julien Nioche < >>>> [email protected]> wrote: >>>> >>>>> I disagree. You'd expect a binary release to work out of the box - >>>>> which is not the case. Plus we'd have to spend more time explaining the >>>>> workaround, answering the same questions over and over on the ML etc... >>>>> Fixing this should not be a big deal (i.e. add the gore-x modules for the >>>>> backends to the ivy deps file). >>>>> >>>>> Julien >>>>> >>>>> >>>>> On 14 June 2012 20:27, Mattmann, Chris A (388J) < >>>>> [email protected]> wrote: >>>>> >>>>>> Hey Guys, >>>>>> >>>>>> I think the annoyance is probably something folks can live with as >>>>>> they have been >>>>>> waiting for an "official" release of 2.x for years :) >>>>>> >>>>>> My +1 to roll RC #2 with or without a solution to this and mark it as >>>>>> a TODO. "release >>>>>> eary", "release often" :) >>>>>> >>>>>> Cheers, >>>>>> Chris >>>>>> >>>>>> On Jun 14, 2012, at 10:04 AM, Lewis John Mcgibbney wrote: >>>>>> >>>>>> > Aye this is no good at all. Depending on which backend you wish to >>>>>> use with Gora, you will need to go and manually fetch the correct .jar's >>>>>> from maven central. >>>>>> > >>>>>> > Does anyone else have either solution or a workaround before I push >>>>>> RC2 with just src dists? >>>>>> > >>>>>> > Thanks >>>>>> > >>>>>> > Lewis >>>>>> > >>>>>> > On Thu, Jun 14, 2012 at 4:52 PM, Sebastian Nagel < >>>>>> [email protected]> wrote: >>>>>> > > We only supply src distributions... >>>>>> > > Does this principle apply to Nutch 2 as well? >>>>>> > Maybe, yes. >>>>>> > The situation with the current binary package is uncomfortable: >>>>>> > I had to copy/link gora-hbase and hbase jars into lib/ to get nutch >>>>>> running. >>>>>> > >>>>>> > 2012/6/13 Lewis John Mcgibbney <[email protected]> >>>>>> > Hi Guys, >>>>>> > >>>>>> > Whilst updating the Nutch2Tutorial I got thinking that within Gora >>>>>> we don't supply binary distributions of the code, this is because when >>>>>> using Gora a user may wish/require to recompile the code to accomodate >>>>>> config changes etc. We only supply src distributions... >>>>>> > >>>>>> > Does this principle apply to Nutch 2 as well? I mean, what if your >>>>>> using the gora-sql dependency, then you wish to switch to HBase and >>>>>> recompile, is this possible within the binary distribution? >>>>>> > >>>>>> > Best >>>>>> > >>>>>> > Lewis >>>>>> > >>>>>> > >>>>>> > On Wed, Jun 13, 2012 at 3:38 PM, Julien Nioche < >>>>>> [email protected]> wrote: >>>>>> > Ferdy >>>>>> > >>>>>> > The Nutch job jar is not present in the binary archive. This means >>>>>> distributed running of jobs is not supported. I'm not sure if this is a >>>>>> problem (since users can always build one themselves), merely pointing it >>>>>> out. The recently released 1.5 also lacks this job jar, so at least no >>>>>> difference there. >>>>>> > >>>>>> > The binary distrib corresponds to runtime/local and as such should >>>>>> NOT have the job file there. This is now the norm since 1.5 >>>>>> > >>>>>> > Will try and do some testing of the RC >>>>>> > >>>>>> > Thanks >>>>>> > >>>>>> > Julien >>>>>> > >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > >>>>>> > Open Source Solutions for Text Engineering >>>>>> > >>>>>> > http://digitalpebble.blogspot.com/ >>>>>> > http://www.digitalpebble.com >>>>>> > http://twitter.com/digitalpebble >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > Lewis >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > Lewis >>>>>> > >>>>>> >>>>>> >>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>>> Chris Mattmann, Ph.D. >>>>>> Senior Computer Scientist >>>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >>>>>> Office: 171-266B, Mailstop: 171-246 >>>>>> Email: [email protected] >>>>>> WWW: http://sunset.usc.edu/~mattmann/ >>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>>> Adjunct Assistant Professor, Computer Science Department >>>>>> University of Southern California, Los Angeles, CA 90089 USA >>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> * >>>>> * >>>>> Open Source Solutions for Text Engineering >>>>> >>>>> http://digitalpebble.blogspot.com/ >>>>> http://www.digitalpebble.com >>>>> http://twitter.com/digitalpebble >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Lewis* >>>> >>>> >>> >> >> >> -- >> * >> *Open Source Solutions for Text Engineering >> >> http://digitalpebble.blogspot.com/ >> http://www.digitalpebble.com >> http://twitter.com/digitalpebble >> >> > > > -- > *Lewis* > > -- * *Open Source Solutions for Text Engineering http://digitalpebble.blogspot.com/ http://www.digitalpebble.com http://twitter.com/digitalpebble
