[
https://issues.apache.org/jira/browse/NUTCH-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated NUTCH-891:
--------------------------------
Attachment: gora-49_v1.patch
Nice patch, but I think changing the artifact name causes some problems in the
other parts of the build (namely test and publish). I am attaching another
patch for Gora which adds jar-snapshot and test-jar-snapshot targets to the top
level build.
Nutch can use :
$ ant test-jar-snapshot
and copy the resulting jars at will. Is this acceptable ?
BTW, gora uses github's issue tracker, you can also comment there.
http://github.com/enis/gora/issues/issue/49
> 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-49_v1.patch, 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.
