-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
${packaging.type} variable in pom.xml breaks Ivy #572
Comments
@ChristianCiach Commented |
@maltem-za Commented |
@maltem-za Commented
Then all you have to do is place the jar file in the configured location, for example: Thanks to @mpetris for the solution. |
@Randgalt Commented |
@pavelbucek Commented |
@Randgalt Commented |
@Randgalt Commented |
@nicktrav Commented |
|
You should use this artifact now: https://mvnrepository.com/artifact/jakarta.ws.rs/jakarta.ws.rs-api |
The ${packaging.type} variable introduced in 71c20bd breaks Ivy with the following output:
Judging by the todo comment in pom.xml you are aware of the issue, but perhaps you are not aware that, in its current state, this still breaks Ivy. It also breaks the download link on mvnrepository.com, by the way.
Here is the same issue in a different project with some interesting comments: ronmamo/reflections#169
I can resolve the issue manually by putting the jar files into my Ivy cache directory. As I'm using IntelliJ IDEA and the IvyIDEA plugin I can't use the system property fix mentioned in the link above (or can't figure out how). Maybe there is a better way to resolve this with Ivy, but I'm not sure as I'm quite new to it.
The text was updated successfully, but these errors were encountered: