[
https://issues.apache.org/jira/browse/NUTCH-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900290#action_12900290
]
Chris A. Mattmann commented on NUTCH-891:
-----------------------------------------
bq. Sure, that would solve the problem for now - I'll bother the Gora devs, and
you can create the patch, ok? Ultimately we should go with the other solution
(publish to Maven), but it requires more involvement from Gora devs.
I like it! lol. Sure, I'll try and create a patch to make it do that.
Installing Gora forced me to figure out how to use git the other day, so why
not figure out how to patch Gora! ^_^
bq. Neither am I, no egos here - I just find the current situation after the
fix to be intractable, especially when doing bugfixing and testing - because
even if APIs stay the same, hidden bugs may not be the same across revisions...
I hear ya. OK let me think on this -- we definitely need a solution here. In
the meanwhile I'll try and figure out how to patch Gora ant to make it version
the jar on the Ivy install in a more meaningful way.
> Nutch build should not depend on unversioned local deps
> -------------------------------------------------------
>
> Key: NUTCH-891
> URL: https://issues.apache.org/jira/browse/NUTCH-891
> Project: Nutch
> Issue Type: Bug
> Reporter: Andrzej Bialecki
>
> The fix in NUTCH-873 introduces an unknown variable to the build process.
> Since local ivy artifacts are unversioned, different people that install Gora
> jars at different points in time will use the same artifact id but in fact
> the artifacts (jars) will differ because they will come from different
> revisions of Gora sources. Therefore Nutch builds based on the same svn rev.
> won't be repeatable across different environments.
> As much as it pains the ivy purists ;) until Gora publishes versioned
> artifacts I'd like to revert the fix in NUTCH-873 and add again Gora jars
> built from a known external rev. We can add a README that contains commit id
> from Gora.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
