[
https://issues.apache.org/jira/browse/LUCENE-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143906#comment-15143906
]
Steve Rowe commented on LUCENE-7024:
------------------------------------
The script crawls {{pom.xml.template}} files from the release branch of the
source repo (as a source of truth about what Maven artifacts should be
produced), and crawls all of the maven artifacts, POMs included, from the RC
URL, which is either an http(s):// URL (now served by the ASF Subversion
server), or is local (a file:// URL).
The Maven artifact crawling process should continue to work as-is.
But the ASF Git server's HTML viewer renders pages with a different URL format
and using different page layouts than the ASF Subversion server, so new
scraping code is needed in order to support that. I'll work on it, but I'm
afraid it'll likely take me a day or two to finish. Hopefully that won't
substantially delay your target 5.5.0 RC1 timeframe, [~mikemccand].
> smokeTestRelease.py's maven checker needs to switch from svn to git
> -------------------------------------------------------------------
>
> Key: LUCENE-7024
> URL: https://issues.apache.org/jira/browse/LUCENE-7024
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
>
> The {{checkMaven}} function in the smoke tester seems to be loading known
> branches from SVN to locate the branch currently being released and then
> crawling for {{pom.xml.template}} files from the svn server. We need to
> switch this to crawling git instead, but I'm not too familiar with what's
> happening here ...
> Maybe [~steve_rowe] can help?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
