来自远程 p2 存储库的pluginPath 和依赖项
在我的 pde 构建中，我使用 pluginPath 属性来解析本地 p2 存储库的依赖项，例如：
DpluginPath=${basedir}/../../../plugins:/cache/3pp/site/mockito/1.8.2:/cache/3pp/site/spring/3.0.1< /代码>
我正在尝试找到如何有效地将缓存从 HTTP p2 物化到本地文件。
我知道我可以使用 ant-contrib 进行循环并为每个依赖项调用 p2.mirror 任务。对我来说特别重要的是最大限度地减少网络开销 - 以保持快速构建。
但是，是在本地文件系统上声明依赖关系并具体化 p2 存储库的更好方法吗？
In my pde build I'm using pluginPath property to resolve dependencies from local p2 repositories for example:
DpluginPath=${basedir}/../../../plugins:/cache/3pp/site/mockito/1.8.2:/cache/3pp/site/spring/3.0.1
I'm trying to find how to effectively materialize caches from HTTP p2 to local files.
I know that I could use ant-contrib for looping and invoke p2.mirror task for each dependency. Specially important is for me is minimalizing network overhead - to keep builds fast.
But, is the better way to declare dependency and materialize p2 repositories on local filesystem?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
要将 p2 存储库提供到您的构建中，您应该将所有存储库放置在
repoBaseLocation中。然后，默认情况下transformedRepoLocation将是您的构建所使用的可运行存储库，并且您不需要使用pluginPath。请参阅重用元数据< /a>.如何将存储库放入
repoBaseLocation取决于您。如果稳定的存储库尚不存在，您可以将其镜像到一个常见的已知位置（当前构建目录之外的目标目录），并让您的构建将它们复制到每个构建的每个repoBaseLocation中。To feed p2 repositories into your build, you should place all of your repos in
repoBaseLocation. Then by defaulttransformedRepoLocationwill be the runnable repo that is consumed by your build, and you shouldn't need to play withpluginPath. See Reusing Metadata.How you get your repos into the
repoBaseLocationis then up to you. You could mirror stable repos into a common known location (a target directory outside of your current build directory) if they don't exist already, and have your build copy them into eachrepoBaseLocationper build.