[
https://issues.apache.org/jira/browse/NUTCH-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Jelsma updated NUTCH-1394:
-
Summary: backport NUTCH-1232 Remove site field from index-basic (was:
backport NUTCH-1232
[
https://issues.apache.org/jira/browse/NUTCH-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema updated NUTCH-1392:
Attachment: NUTCH-1392.patch
-force and -resume arguments being ignored in ParserJob
Maybe just 1392? I went ahead and made a patch that should fix this. Feel
free to commit or ignore prior to RC2.
On Thu, Jun 14, 2012 at 1:44 AM, Lewis John Mcgibbney
lewis.mcgibb...@gmail.com wrote:
Hi Sebastian,
On Wed, Jun 13, 2012 at 11:30 PM, Sebastian Nagel
wastl.na...@googlemail.com
Lewis John McGibbney created NUTCH-1395:
---
Summary: Show batchId when skipping within ParserJob
Key: NUTCH-1395
URL: https://issues.apache.org/jira/browse/NUTCH-1395
Project: Nutch
[
https://issues.apache.org/jira/browse/NUTCH-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294994#comment-13294994
]
Lewis John McGibbney commented on NUTCH-1392:
-
Thanks Ferdy for the lightening
[
https://issues.apache.org/jira/browse/NUTCH-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney resolved NUTCH-1392.
-
Resolution: Fixed
Fix Version/s: (was: 2.1)
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 lewis.mcgibb...@gmail.com
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
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
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
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
lists.digitalpeb...@gmail.com wrote:
I disagree. You'd expect a binary release to work out of the box - which
yep, remember that you can't build from the bin package so inevitably
someone will wonder why only such or such backend is available etc...
another option is to NOT have a binary release at all, in which case it is
acceptable I think not to include the deps in ivy. Maybe we should at least
add
This is what is currently done and what I was essentially proposing.
I really don't know about the size of the bin artifact if we enable all
gora-* dependencies before packaging it for distribution... thanks to input
from yourselves we recently sorted out some size issues with 1.5, it would
be
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
14 matches
Mail list logo
