这个常春藤的变化模式/快照配置有什么问题? [英] What's wrong with this Ivy changingPattern / SNAPSHOT configuration?

问题描述

更新快照依赖项时，我无法让 Ivy 更新缓存.解析器(具有以下设置:

I can't get Ivy to update cache when snapshot dependencies are updated. The resolver (to has the following settings:

<url name="xxx" m2compatible="false" 
     checkmodified="true" changingMatcher="regexp" 
     changingPattern=".*-SNAPSHOT.*">

一个示例工件文件名(在 Artifactory 中)是:

An example artifact filename (in Artifactory) is:

my-jar-1.999-SNAPSHOT.jar

解析的详细 Ant 日志包括:

A detailed Ant log of resolve includes:

[NOT REQUIRED] com.myorg#my-module;1.999-SNAPSHOT!my-jar.jar

工件上没有 POM.

解析器位于链式解析器下方；他们都设置了所有相关的属性.我已阅读 https://issues.apache.org/jira/browse/IVY-938 和 https://issues.apache.org/jira/browse/IVY-1221，包括所有评论，以及 AFAICT(可能是错误的！)没有任何解决方法是相关的.

The resolver is underneath a chain resolver; they both have all the relevant attributes set. I have read https://issues.apache.org/jira/browse/IVY-938 and https://issues.apache.org/jira/browse/IVY-1221, including all the comments, and AFAICT (perhaps incorrectly!) none of the workarounds are relevant.

我应该放弃快照而只使用带有integration.latest"动态版本依赖项的显式版本吗?我担心当我们为多个主要版本进行集成构建时，这可能最终会失败.到那时，我们需要将主要版本拆分到单独的存储库中，或者将主要版本号放在工件名称中，或者使用同样笨重的东西，只是为了使integration.latest"起作用.

Should I give up on snapshots and just use explicit versions with "integration.latest" dynamically versioned dependencies? I fear this may end up failing when we have integration builds happening for multiple major versions. At that point we'll need to split the major versions out into separate repositories, or put the major build number in the artifact name, or something equally clunky, just to make "integration.latest" work.

推荐答案

经过几天的挣扎...

问题在于

checkmodified="true" changingMatcher="regexp"

要在 上工作，它必须在层次结构行中的每个解析器 - 所有父 解析器和 、、或底部的 解析器.

to work on a <resolver>, it has to be on every resolver in the hierarchy line - all parent <chain> resolvers and the <url>, <local>, or <ibiblio> resolver at the bottom.

这篇关于这个常春藤的变化模式/快照配置有什么问题?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！