PDE Build - 使用不同的 preTagPath 值从 SVN 获取映射文件中指定的功能和插件
当尝试从 SVN 存储库获取功能和插件时，我需要从不同的子路径中提取它们。遵循的地图文件格式如下：
<feature|plugin>@<id>=SVN,<tag>[:revision],<svnRepositoryURL>,<preTagPath>,<postTagPath>
这是我在单个地图文件中的内容：
[email protected]=SVN,trunk:HEAD,https://url.to.repository,movement,com.sag.tfg.motion
[email protected]=SVN,trunk:HEAD,https://url.to.repository,movement,com.sag.tfg.motion.feature
[email protected]=SVN,trunk=HEAD,https://url.to.repository,core,com.sag.base.util
仅获取前两项，而没有获取第三项。我认为这可能是由于具有不同的 preTagPath 值（例如，移动与核心）。获取操作是否对单个映射文件中的 preTagPath 或 postTagPath 值施加任何类型的约束或限制？
When attempting to fetch features and plug-ins from an SVN repository, I am in need of pulling them from different sub-paths. The map file format being followed is as follows:
<feature|plugin>@<id>=SVN,<tag>[:revision],<svnRepositoryURL>,<preTagPath>,<postTagPath>
Here is what I have in a single map file:
[email protected]=SVN,trunk:HEAD,https://url.to.repository,movement,com.sag.tfg.motion
[email protected]=SVN,trunk:HEAD,https://url.to.repository,movement,com.sag.tfg.motion.feature
[email protected]=SVN,trunk=HEAD,https://url.to.repository,core,com.sag.base.util
Only the first two items are being fetched while the third one is not. I'm thinking this may be due to having different preTagPath values (e.g., movement versus core). Does the fetch operation impose any type of constraints or restrictions on having the preTagPath or postTagPath values being equal to one another in a single map file?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
第三项似乎请求 trunk=HEAD 而不是前两项中的 trunk:HEAD。
应该是：
The third item seems to be requesting trunk=HEAD rather than trunk:HEAD as in the first two.
Should it be: