${packaging.type} variable in pom.xml breaks Ivy

Question

${packaging.type} variable in pom.xml breaks Ivy

glassfishrobot opened this issue 7 years ago · 12 comments

The ${packaging.type} variable introduced in 71c20bd breaks Ivy with the following output:

:: problems summary ::
:::: WARNINGS
		[NOT FOUND  ] javax.ws.rs#javax.ws.rs-api;2.1!javax.ws.rs-api.${packaging.type} (491ms)

	==== public: tried

	  https://repo1.maven.org/maven2/javax/ws/rs/javax.ws.rs-api/2.1/javax.ws.rs-api-2.1.${packaging.type}

		::::::::::::::::::::::::::::::::::::::::::::::

		::              FAILED DOWNLOADS            ::

		:: ^ see resolution messages for details  ^ ::

		::::::::::::::::::::::::::::::::::::::::::::::

		:: javax.ws.rs#javax.ws.rs-api;2.1!javax.ws.rs-api.${packaging.type}

		::::::::::::::::::::::::::::::::::::::::::::::

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.

Answer 1 · 2017-10-04T13:55:47.000Z

@ChristianCiach Commented
Duplicate of #571

Answer 2 · 2017-10-04T14:05:38.000Z

@maltem-za Commented
@ChristianCiach Ah, thanks, I didn't find that one (obviously).

Answer 3 · 2017-10-16T09:04:03.000Z

@maltem-za Commented
For anyone else who comes across this, you can fix it for Ivy by adding a filesystem resolver like this:

<filesystem name="mylocal">
  <ivy pattern= "${ivy.default.ivy.user.dir}/local/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]" />
  <artifact pattern= "${ivy.default.ivy.user.dir}/local/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]" />
</filesystem>

Then all you have to do is place the jar file in the configured location, for example:
~/ivy2/local/javax.ws.rs/javax.ws.rs-api/jars/javax.ws.rs-api-2.1.jar

Thanks to @mpetris for the solution.

Answer 4 · 2017-10-25T21:01:50.000Z

@Randgalt Commented
This really needs to be fixed ASAP. It breaks sbt as well. I don't understand the need for <packaging>${packaging.type}</packaging> in the pom anyway. Why not just make it JAR?

Answer 5 · 2017-10-25T22:58:04.000Z

@pavelbucek Commented
closing as duplicate of https://github.com/jax-rs/api/issues/571

Answer 6 · 2017-10-25T23:01:46.000Z

@Randgalt Commented
Sad that you've closed this @pavelbucek - #571 does not fix the problem.

Answer 7 · 2017-10-31T01:34:30.000Z

@nicktrav Commented
This is breaking things in the Pants build tool, which under the hood uses Ivy. I also don't understand why this issue was closed along with #571.

Seems like a trivial fix to just make this <packaging>jar</packaging>?

Answer 8 · 2017-10-31T01:50:19.000Z

@Randgalt Commented
@nicktrav see https://github.com/jax-rs/api/pull/576

Answer 9 · 2017-10-31T01:59:40.000Z

@nicktrav Commented
I'm very much in support. Left (non-passive-aggressive) my 👍 .

Answer 10 · 2018-02-10T22:19:26.000Z

Issue Imported From: https://github.com/jax-rs/api/issues/572
Original Issue Raised By:@maltem-za
Original Issue Assigned To: Unassigned
Original Issue Closed By:@pavelbucek

Answer 11 · 2018-11-28T12:54:46.000Z

issue persists:

any workaround for this ?

Answer 12 · 2018-11-28T13:25:46.000Z

You should use this artifact now: https://mvnrepository.com/artifact/jakarta.ws.rs/jakarta.ws.rs-api