No /usr/share/java/jaxb-api.jar in 4.0.0 about jaxb-api HOT 5 CLOSED

AFAIK this project has never been dealing with os specific installers/packages and it has no plans to do so.

from jaxb-api.

That seems quite dismissive? The "OS specific package" is just using something this project used to provide - an unversioned file in a specific place - and no longer does. The fact that it's an "OS specific package" doesn't seem particularly relevant.

In any case, the code is in dogtag-pki's upstream, there's nothing specific to Fedora there. I'd expect the /usr/share/java part might differ between distros, but ultimately dogtag-pki is, I think, always looking for this unversioned jaxb-api.jar file in "the Java directory", which jaxb-api previously installed but no longer does.

If the answer is "we intentionally removed that and projects that want to work with jaxb-api 4 shouldn't expect it to be there", that's fine. But I don't see what "os specific installers/packages" really has to do with anything?

from jaxb-api.

That seems quite dismissive? The "OS specific package" is just using something this project used to provide - an unversioned file in a specific place -

No, that has never been true. A file produced by this project since its inception in ~ 2005 has been published to maven repository (initially maven 1 repo on the java.net) only.

and no longer does. The fact that it's an "OS specific package" doesn't seem particularly relevant.

Why do you think this project is responsible for maintaining RPMs listed at https://rpmfind.net/linux/rpm2html/search.php?query=mvn(jakarta.xml.bind%3Ajakarta.xml.bind-api) or https://rpmfind.net/linux/rpm2html/search.php?query=mvn(javax.xml.bind%3Ajaxb-api) which are responsible for the creation of the links, docs etc and the file/symlink dogtag-pki and/or freeipa project expects?

In any case, the code is in dogtag-pki's upstream, there's nothing specific to Fedora there. I'd expect the /usr/share/java part might differ between distros, but ultimately dogtag-pki is, I think, always looking for this unversioned jaxb-api.jar file in "the Java directory", which jaxb-api previously installed but no longer does.

If the answer is "we intentionally removed that and projects that want to work with jaxb-api 4 shouldn't expect it to be there", that's fine. But I don't see what "os specific installers/packages" really has to do with anything?

the name of binary produced by this project was changed from jaxb-api.jar to jakarta.xml.bind-api.jar between versions 2.3.2 and 2.3.3. Nothing else has changed. What has not been produced, couldn't be removed. But someone else, ie some downstream consumer, could stop producing/maintaining rpms of course, but that is out of control of this project.

from jaxb-api.

Ah, jeez - sorry. The reason I thought this was an upstream issue is that I didn't think the downstream package build did anything to create that file, or changed anything about it between 2.3.3 and 4.0.0. I checked the diff between those builds twice. But looking at it again to write this comment, I see I missed a bit:

https://src.fedoraproject.org/rpms/jaxb-api/c/75d10a4b04ca7f289494cca295f78998a4ab27b5?branch=rawhide

it's the things that were removed between lines 46 and 48 that did this, and were removed, so that's why it went away. Don't know how I missed that twice before. If I'd seen it I would have kept this downstream and not filed an upstream issue. Sorry for the noise.

from jaxb-api.

no worries, glad to see we managed to resolve this in the end.

from jaxb-api.