[
https://issues.apache.org/jira/browse/NUTCH-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901724#action_12901724
]
Chris A. Mattmann commented on NUTCH-891:
-----------------------------------------
Hey Guys,
OK, i finally had time to do this. I went ahead and added a ${now} parameter to
the gora jar file names. I could have done like a sha1 appended to the jar
name, but kept running into a chicken and egg problem. The attached patch works
great and just uses the same ${now} format used in the Ivy build-common.xml
part. I don't know how to get this contributed to gora, so I'm attaching it
here -- feel free to pull down into Gora.
Cheers,
Chris
> 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
> Attachments: gora.build.patch
>
>
> 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.
