Problem with maven central

[titusthefox04]

String ${packaging.type} not resolved create problem in maven central and in sbt project.

[chkal]

This is a duplicate of #572 and #571.

I think this is actually a sbt bug. Maven (and Gradle?) can handle this dynamic packaging type correctly.

[mkarg]

@spericas Do you know why we don't simply use <packaging>jar</packaging> instead?

[chkal]

AFAIK the packaging is different depending on the JDK version:

See:

https://github.com/eclipse-ee4j/jaxrs-api/blob/d2cadd2a5b22b4c7922a3f1d7c5e00506fccdd75/jaxrs-api/pom.xml#L91-L99

And:

https://github.com/eclipse-ee4j/jaxrs-api/blob/d2cadd2a5b22b4c7922a3f1d7c5e00506fccdd75/jaxrs-api/pom.xml#L144-L152

[mkarg]

Looks like this was done solely to make the OSGi packager (bnd) work as it is so outdated that it cannot handle JDK 9. I don't like that solution. OSGi is not part of neither Jakarta EE nor JAX-RS. I'd rather kick OSGi out right now. But what do others think?

[chkal]

Looks like this was done solely to make the OSGi packager (bnd) work as it is so outdated that it cannot handle JDK 9.

Yeah, looks like this was the reason for introducing the dynamic packing type.

I don't like that solution. OSGi is not part of neither Jakarta EE nor JAX-RS. I'd rather kick OSGi out right now. But what do others think?

AFAIK the OSGi manifests are required for the Glassfish integration. But I'm not familiar with the details.

I think we should keep the OSGi manifest. It doesn't do any harm and OSGi is still quite popular. Maybe bnd even supports Java 9 today? Perhaps fixing this would simply be a matter of updating the maven-bundle-plugin?

[mkarg]

At least on my development machine maven-bundle-plugin had no problem to process packaging type bundle on JDK 9+ without special handling of module-info, so I opened PR #628 as a potential solution for this issue.

[spericas]

@mkarg Must have been OSGi. I don't have a problem fixing it to jar.

[kwhat]

So, when is 2.2 being released so I can stop dealing with this problem.

[mkarg]

I am sorry to say there is no fixed deadline for 2.2, as this depends on ongoing negotiations between Oracle and the Eclipse Foundation.

@spericas @chkal Do you think it would be safe to merge #628 also into EE4J_8?

[spericas]

@mkarg We had to provide a pretty detailed explanation of all the changes that went into EE4J_8 for 2.1.1. I'd rather not check more changes into that branch.

[mkarg]

@spericas Understood. As I was not involved in that part of the release so dumb question: Did you have to manually write a report or how was this step performed?

[chkal]

I'm basically +1 for including this in the EE4J_8 branch. Especially because the issue affects many users and the fix is actually trivial. Maybe we could draft the explanation of the changes in the wiki or in the git repo so we can work on it together? Maybe having the draft in the git repo is actually a good way to go, because this way we can provide the explanation/changelog within the corresponding pull request!?!

[spericas]

@mkarg It was a manual process. Nothing it could not be done again, of course.

[mkarg]

@chkal +1
@spericas What do you think?

[mkarg]

@kwhat I think you can be happy: I just published JAX-RS 2.1.2 on Maven Central including the fix you requested. :-)

[spericas]

@mkarg Great!

[chkal]

@mkarg Thanks for your weekend work.