[
https://issues.apache.org/jira/browse/NUTCH-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166875#comment-17166875
]
Lewis John McGibbney commented on NUTCH-2669:
---------------------------------------------
Hi [~snagel] I did the following and was able to build without error
{code}
rm -r ~/.ivy2
rm -r ~/.ant
{code}
* upgrade
[ivy.version|https://github.com/apache/nutch/blob/master/default.properties#L66]
to 2.5.0
* upgrade
[ivy.install.version|https://github.com/apache/nutch/blob/master/src/plugin/any23/build-ivy.xml#L20]
to 2.5.0 in the following plugins
{code}
./src/plugin/exchange-jexl/build-ivy.xml
./src/plugin/index-geoip/build-ivy.xml
./src/plugin/indexer-elastic/build-ivy.xml
./src/plugin/parse-tika/build-ivy.xml
./src/plugin/protocol-selenium/build-ivy.xml
./src/plugin/any23/build-ivy.xml
./src/plugin/indexer-rabbit/build-ivy.xml
./src/plugin/lib-htmlunit/build-ivy.xml
./src/plugin/protocol-interactiveselenium/build-ivy.xml
./src/plugin/scoring-similarity/build-ivy.xml
./src/plugin/lib-selenium/build-ivy.xml
./src/plugin/parsefilter-naivebayes/build-ivy.xml
./src/plugin/indexer-solr/build-ivy.xml
./src/plugin/indexer-kafka/build-ivy.xml
./src/plugin/lib-rabbitmq/build-ivy.xml
./src/plugin/publish-rabbitmq/build-ivy.xml
{code}
I wonder if we can remove _ivy.install.version_ or if we can reuse _ivy.version
_ from earlier... hmmm.
Do you have time to cleaer local cache's and to try this approach as well? Do
you want me to produce a pull request for same which would make it easdier for
you?
> Reliable solution for javax.ws packaging.type
> ---------------------------------------------
>
> Key: NUTCH-2669
> URL: https://issues.apache.org/jira/browse/NUTCH-2669
> Project: Nutch
> Issue Type: Bug
> Components: build
> Affects Versions: 2.4, 1.16
> Reporter: Sebastian Nagel
> Assignee: Sebastian Nagel
> Priority: Blocker
> Fix For: 1.18
>
>
> The upgrade of Tika to v1.19.1 (NUTCH-2651, NUTCH-2665, NUTCH-2667) raises an
> ant/ivy issue during build when resolving/fetching dependencies:
> {noformat}
> [ivy:resolve] [FAILED ]
> javax.ws.rs#javax.ws.rs-api;2.1!javax.ws.rs-api.${packaging.type}: (0ms)
> [ivy:resolve] ==== local: tried
> [ivy:resolve]
> /home/jenkins/.ivy2/local/javax.ws.rs/javax.ws.rs-api/2.1/${packaging.type}s/javax.ws.rs-api.${packaging.type}
> [ivy:resolve] ==== maven2: tried
> [ivy:resolve]
> http://repo1.maven.org/maven2/javax/ws/rs/javax.ws.rs-api/2.1/javax.ws.rs-api-2.1.${packaging.type}
> [ivy:resolve] ==== apache-snapshot: tried
> [ivy:resolve]
> https://repository.apache.org/content/repositories/snapshots/javax/ws/rs/javax.ws.rs-api/2.1/javax.ws.rs-api-2.1.${packaging.type}
> [ivy:resolve] ==== sonatype: tried
> [ivy:resolve]
> http://oss.sonatype.org/content/repositories/releases/javax/ws/rs/javax.ws.rs-api/2.1/javax.ws.rs-api-2.1.${packaging.type}
> [ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve] :: FAILED DOWNLOADS ::
> [ivy:resolve] :: ^ see resolution messages for details ^ ::
> [ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve] ::
> javax.ws.rs#javax.ws.rs-api;2.1!javax.ws.rs-api.${packaging.type}
> [ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve] :::: ERRORS
> ...
> BUILD FAILED
> {noformat}
> More information about this issue is linked on
> [jax-rs#576|https://github.com/jax-rs/api/pull/576].
> A work-around is to define a property {{packaging.type}} and set it to
> {{jar}}. This can be done
> - in command-line {{ant -Dpackaging.type=jar ...}}
> - in default.properties
> - in ivysettings.xml
> The last work-around is active in current master/1.x. However, there are
> still Jenkins builds failing while few succeed:
> ||#build||status jax-rs||machine||work-around||
> |3578|success|H28|ivysettings.xml|
> |3577|failed|H28|ivysettings.xml|
> |3576|failed|H33|ivysettings.xml|
> |3575|success|ubuntu-4|ivysettings.xml|
> |3574|failed|ubuntu-4|-Dpackaging.type=jar + default.properties|
> |3571|failed|?|-Dpackaging.type=jar + default.properties|
> |3568|failed|?|-Dpackaging.type=jar + default.properties|
> Builds which failed for other reasons are left away. The only pattern I see
> is that only the second build on every of the Jenkins machines succeeds. A
> possible reason could be that the build environments on the machines persist
> state (the Nutch build directory, local ivy cache, etc.). If this is the
> case, it may take some time until all Jenkins machines will succeed.
> The ivysettings.xml work-around was the first which succeeded on a Jenkins
> build but it may be the case that all three work-arounds apply.
> The issue is supposed to be resolved (without work-arounds) by IVY-1577.
> However, it looks like it isn't:
> - get rc2 of ivy 2.5.0 (the URL may change):
> {noformat}
> % wget -O ivy/ivy-2.5.0-rc2-test.jar \
>
> https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/artifact/org.apache.ivy_2.5.0.cr2_20181023065327.jar
> {noformat}
> - edit default properties and set {{ivy.version=2.5.0-rc2-test}}
> - remove work-around in ivysettings.xml (or default.properties)
> - run {{ant clean runtime}} and check for failure resp. whether javax.ws lib
> is in place: {{ls build/lib/javax.ws.rs-api*.jar}}
> This solution fails for
> [ivy-2.5.0-rc1.jar|http://repo2.maven.org/maven2/org/apache/ivy/ivy/2.5.0-rc1/ivy-2.5.0-rc1.jar]
> and the mentioned rc2 jar as of 2018-10-23. But maybe the procedure is
> wrong, I'll contact the ant/ivy team to solve this.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
