旧版存储库的常春藤依赖管理 [英] Ivy dependency management for legacy repository

问题描述

我们有一个没有ivy.xml和其他元数据文件的存储库.此后，它由另一个不使用ivy/maven的团队发布，但将继续频繁交付代码.

We have a repository which doesn't have ivy.xml and other metadata files. Since, its published by another team which doesn't use ivy/maven but will continue to deliver code frequently.

依赖所需的jar文件以平面结构存储在单个目录中，没有修订数据.没有组织/模块/修订结构.

The jars needed for dependency are stored in flat structure inside a single directory with no revision data. The organization / module /revision structure is absent.

ivy是否在核心产品中允许此类依赖性解析，还是我必须编写自定义解析器?

Does ivy allow such dependency resolutions in the core product or will I have to write a custom resolver?

谢谢

推荐答案

了解常春藤模式可以帮助我解决该问题.每当存储库中没有常春藤文件时，就永远不要指定常春藤模式.

Understanding ivy pattern helped me resolve the issue. The catch is never specify an ivy pattern whenever the repository doesn't have ivy files.

这篇关于旧版存储库的常春藤依赖管理的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！