[
https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816237#comment-16816237
]
Steve Rowe edited comment on LUCENE-2562 at 4/12/19 1:06 PM:
-------------------------------------------------------------
[~thetaphi]: I didn't think of running the smoke tester; I'm not sure
whether/how Maven artifact validation checks artifact correspondence, I'll run
it locally on the branch now that Tomoko has updated it.
[~Tomoko Uchida]: I saw that same problem, as did Kevin Risden [over on
SOLR-9515|https://jira.apache.org/jira/browse/SOLR-9515?focusedCommentId=16762835&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16762835].
AFAICT this happens when you have a local maven repo that you haven't used the
Lucene/Solr Maven build with, but which is populated by the Lucene/Solr Ant
build via the Maven Ant Tasks plugin. Earlier in the log I see:
{noformat}
[artifact:dependencies] Downloading:
com/healthmarketscience/openhms-parent/1.1.8/openhms-parent-1.1.8.pom from
repository taglets at http://maven.geotoolkit.org/
[artifact:dependencies] Transferring 0K from taglets
[artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Checksum failed on
download: local = 'c53d5de1975ce58462f226d7ed126e02d8f1f58b'; remote = '<html>
[artifact:dependencies] <head><title>301' - RETRYING
{noformat}
So (for me anyway) what happened was that a Maven repository we don't specify
(probably specified in the jackcess POM hierarchy) returned an HTML page and a
301 HTTP code (permanently relocated), which is improperly interpreted by Maven
Ant Tasks as the appropriate artifact and saved as if it were the jackcess
parent POM. I worked around this by deleting the local repo's bad file, then
installing the correct POM manually:
{noformat}
rm
~/.m2/repository/com/healthmarketscience/openhms-parent/1.1.8/openhms-parent-1.1.8.pom
curl -O
https://repo1.maven.org/maven2/com/healthmarketscience/openhms-parent/1.1.8/openhms-parent-1.1.8.pom
mvn install:install-file -Dfile=openhms-parent-1.1.8.pom
-DgroupId=com.healthmarketscience -DartifactId=openhms-parent -Dversion=1.1.8
-Dpackaging=pom
{noformat}
Maybe there's a better way? (E.g. running the Maven build in this context?)
The above fixed the problem for me. (Maven Ant Tasks have been EOL'd for a few
years, so there will be no fix for this problem in that project.)
was (Author: steve_rowe):
[~thetaphi]: I didn't think of running the smoke tester; I'm not sure
whether/how Maven artifact validation looks at , I'll run it locally on the
branch now that Tomoko has updated it.
[~Tomoko Uchida]: I saw that same problem, as did Kevin Risden [over on
SOLR-9515|https://jira.apache.org/jira/browse/SOLR-9515?focusedCommentId=16762835&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16762835].
AFAICT this happens when you have a local maven repo that you haven't used the
Lucene/Solr Maven build with, but which is populated by the Lucene/Solr Ant
build via the Maven Ant Tasks plugin. Earlier in the log I see:
{noformat}
[artifact:dependencies] Downloading:
com/healthmarketscience/openhms-parent/1.1.8/openhms-parent-1.1.8.pom from
repository taglets at http://maven.geotoolkit.org/
[artifact:dependencies] Transferring 0K from taglets
[artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Checksum failed on
download: local = 'c53d5de1975ce58462f226d7ed126e02d8f1f58b'; remote = '<html>
[artifact:dependencies] <head><title>301' - RETRYING
{noformat}
So (for me anyway) what happened was that a Maven repository we don't specify
(probably specified in the jackcess POM hierarchy) returned an HTML page and a
301 HTTP code (permanently relocated), which is improperly interpreted by Maven
Ant Tasks as the appropriate artifact and saved as if it were the jackcess
parent POM. I worked around this by deleting the local repo's bad file, then
installing the correct POM manually:
{noformat}
rm
~/.m2/repository/com/healthmarketscience/openhms-parent/1.1.8/openhms-parent-1.1.8.pom
curl -O
https://repo1.maven.org/maven2/com/healthmarketscience/openhms-parent/1.1.8/openhms-parent-1.1.8.pom
mvn install:install-file -Dfile=openhms-parent-1.1.8.pom
-DgroupId=com.healthmarketscience -DartifactId=openhms-parent -Dversion=1.1.8
-Dpackaging=pom
{noformat}
Maybe there's a better way? (E.g. running the Maven build in this context?)
The above fixed the problem for me. (Maven Ant Tasks have been EOL'd for a few
years, so there will be no fix for this problem in that project.)
> Make Luke a Lucene/Solr Module
> ------------------------------
>
> Key: LUCENE-2562
> URL: https://issues.apache.org/jira/browse/LUCENE-2562
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Mark Miller
> Assignee: Tomoko Uchida
> Priority: Major
> Labels: gsoc2014
> Fix For: 8.1, master (9.0)
>
> Attachments: LUCENE-2562-Ivy.patch, LUCENE-2562-Ivy.patch,
> LUCENE-2562-Ivy.patch, LUCENE-2562-ivy.patch, LUCENE-2562.patch,
> LUCENE-2562.patch, LUCENE-2562.patch, Luke-ALE-1.png, Luke-ALE-2.png,
> Luke-ALE-3.png, Luke-ALE-4.png, Luke-ALE-5.png, luke-javafx1.png,
> luke-javafx2.png, luke-javafx3.png, luke1.jpg, luke2.jpg, luke3.jpg,
> lukeALE-documents.png, screenshot-1.png, スクリーンショット 2018-11-05 9.19.47.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> see
> "RE: Luke - in need of maintainer":
> http://markmail.org/message/m4gsto7giltvrpuf
> "Web-based Luke": http://markmail.org/message/4xwps7p7ifltme5q
> I think it would be great if there was a version of Luke that always worked
> with trunk - and it would also be great if it was easier to match Luke jars
> with Lucene versions.
> While I'd like to get GWT Luke into the mix as well, I think the easiest
> starting point is to straight port Luke to another UI toolkit before
> abstracting out DTO objects that both GWT Luke and Pivot Luke could share.
> I've started slowly converting Luke's use of thinlet to Apache Pivot. I
> haven't/don't have a lot of time for this at the moment, but I've plugged
> away here and there over the past work or two. There is still a *lot* to do.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
