Now, I have a package which depends on rxtx, which basically is a jar file without %add_maven_depmap. Since I use maven myself, I need that info which %add_maven_depmap otherwise provides.

So, what do I do? I have tried to figure out away to provide that info myself, but I'm too dumb. Should I file a bug against rxtx, with a %add_maven_depmap patch? Or?

There's a bit of a learning curve to these tools, and some are even specific to Fedora because of our requirements.

You could definitely file a bug asking for rxtx to be packaged with some maven metadata as part of their build. %add_maven_depmap is deprecated and %mvn_artifact/%mvn_install [1] should be used in place. I could see maintainers being a slightly reluctant to grow the BuildRequires to things like javapackages-local, and xmvn but it seems like the right thing to do.

I was thinking of some other solutions like creating your own pom for rxtx, and just placing it along with the jar into the reactor cache so that you can resolve it for the build. However your poms still wouldn't be able to resolve rxtx if some other package were to depend on you, so I would see this as a last resort.

Cheers,