Description of problem: Currently collectd-java ships with a bundled collectd-api.jar but comes with no maven metadata that would allow the classes provided by the aforementioned jar file to be made available at build time to packages needing it. How reproducible: Always. Steps to Reproduce: rpm -qp --provides collectd-java-5.7.1-2.el7.x86_64.rpm Actual results: collectd-java = 5.7.1-2.el7 collectd-java(x86-64) = 5.7.1-2.el7 Expected results: collectd-java = 5.7.1-2.el7 collectd-java(x86-64) = 5.7.1-2.el7 mvn(org.collectd:collectd-api)
I know next to nothing about Java, let alone Maven, so bear with me, but wouldn't collectd need to provide a pom.xml file too? At least https://fedoraproject.org/wiki/Packaging:Java seems to suggest that.
That's correct, ideally we'd want to see upstream shipping their own pom.xml file but there are ways to auto-generate it via the Maven install plugin, as an example [1]. [1] http://maven.apache.org/plugins/maven-install-plugin/examples/generic-pom-generation.html
Ok. I don't have much time to look into this, but if you can come up with a patch either here or upstream I'll make sure it gets applied.
Andrea, did you have a change to look into this?
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.