[
https://issues.apache.org/jira/browse/NUTCH-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900335#action_12900335
]
Enis Soztutar commented on NUTCH-891:
-------------------------------------
Of course the best way that Nutch uses Gora is that Gora publishes it's
artifacts to Maven and Nutch uses ivy to fetch the jars. But Gora is still in
heavy development and we need some more time to make a first release.
Until then I think we can use the last commit sha1 in git for the revision
number in git. We use this convention when uploading jars to guthub. Would that
make sense?
> 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.
