You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Doğacan Güney (JIRA)" <ji...@apache.org> on 2010/08/19 14:21:16 UTC

[jira] Commented: (NUTCH-891) Nutch build should not depend on unversioned local deps

    [ https://issues.apache.org/jira/browse/NUTCH-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900267#action_12900267 ] 

Doğacan Güney commented on NUTCH-891:
-------------------------------------

Can't we put Gora jars somewhere? I would like to put jars up somewhere, revision them with commit id (so they will look like gora-core-78ab312.jar), and make nutch depend on a gora version with a commit id... Would this be difficult to do with ivy?

> 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.