jira的REST JAVA客户端中无法解决的父pom依赖性
我需要编写一个应用程序，该应用程序连接到我们的JIRA实例的REST API，并将特定数据同步到我们的另一个应用程序。
我想知道这个官方休息客户libary 是我最直接的方式。不幸的是，看来我只能添加到我的POM中。 我认为我会自己构建它并克隆回购。为了使Atlassian专有依赖性重新估计，我将Maven Repo代理添加到我的Maven的设置中。xml。 nofollow noreferrer“> atlassian deveraler developer document 。
不幸的是，我仍然无法打包API客户端，因为父pom的依赖性仍然无法解决。
<parent>
<groupId>com.atlassian.pom</groupId>
<artifactId>public-pom</artifactId>
<version>5.0.8</version>
</parent>
现在，我想知道我的方法是否是正确的。这个库甚至是为我的用户酶的，还是我应该从头开始对现有的jira休息端点实现我的API，因为我不开发集成的Jira-Plugin。还是我只是缺少一些微不足道的配置。
我的设置的添加。xml，其他所有内容，我都像 empty settings.xml一样毫不动摇。
...
<repository>
<id>atlassian-public</id>
<url>https://packages.atlassian.com/mvn/maven-external/</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
<checksumPolicy>warn</checksumPolicy>
</snapshots>
<releases>
<enabled>true</enabled>
<checksumPolicy>warn</checksumPolicy>
</releases>
</repository>
...
我已经试图从Atlassian社区本身获得一些帮助，但目前它们似乎并不反应迅速:(
I need to write an application, that connects to the REST API of our Jira instance and synchronizes specific data to another application of ours.
I figured this official REST client libary is my straightest way. Unfortunately it seems there is no ready-to-go jar dependecy I can just add to my POM.
I figured I will just build it myself and clone the repo. To enable the resoultion of Atlassian's proprietary dependencies, I added the Maven Repo Proxy to my Maven's settings.xml as suggested by
the Atlassian Developer Documentation.
Unfortunately I still can not package the API client, since the dependency of the parent POM remains unresolvable.
<parent>
<groupId>com.atlassian.pom</groupId>
<artifactId>public-pom</artifactId>
<version>5.0.8</version>
</parent>
Now, I wonder if my approach was even the correct. Is this library even meant for my usecase, or am I supposed to implement my API from scratch against the existing Jira REST endpoints since I don't develop an integrated Jira-Plugin. Or am I just missing some trivial configuration.
The addition to my settings.xml, everything else, I left untouched like in an empty settings.xml.
...
<repository>
<id>atlassian-public</id>
<url>https://packages.atlassian.com/mvn/maven-external/</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
<checksumPolicy>warn</checksumPolicy>
</snapshots>
<releases>
<enabled>true</enabled>
<checksumPolicy>warn</checksumPolicy>
</releases>
</repository>
...
I already tried to get some help from the Atlassian community itself, but they don't seem to be very responsive at the moment :(
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我建议您阅读这个atlassian资源。
看来该图书馆更适合需求，并且肯定会更积极地支持。您当然可以构建自己的图书馆，但我怀疑这会比仅向端点发送普通请求更好。
据我发现， public-pom 看起来非常实验性，根本没有记录。如果您想要快速方法 - 使用他们的已记录的端点
如果您想要一种更面向架构的方法，则可以构建一个带有预定端点的简单库，并使用骆驼之类的东西，以便于路由和日志记录。
I recommend you read this Atlassian resource.
It seems that this library is more suitable for needs, and it's surely supported more actively. You can of course build your own library, but I doubt that will be any better than just sending plain requests to endpoints.
From what I found, public-pom looks very experimental, and isn't documented at all. If you want a quick approach - use their documented endpoints
If you want a more architecture-oriented approach, you can build a simple library with predefined endpoints, and use something like Camel, for easy routing and logging.