I've asked this before, but nobody answered, so I'll give it another try. How can I package my compiled Java/Scala library code as a jar? I only see the

deploy_jar

target, but that will include all the dependencies in the jar, which isn't what I want.

Pants would need rules written to produce a plain jar like that.

@famous-author-71879 would this JAR contain just a single compiled java_library, or also all of its transitive first party deps (but no third-party deps)?

No deps

We might not even need that, I was just so surprised to see that it's not there.

I perceive that you may be implicitly assuming that there has been regular development attention made to the JVM backends including a consistent roadmap for what to implement. That is not the case unfortunately. While there briefly was a commercial sponsor for some JVM work more than a year ago (through Toolchain), that sponsorship was non-recurring and there has not really been any consistent development effort made to the JVM code since.

This is true. The roadmap is whatever interested parties want it to be. So far no one has asked for this, but it makes sense. In fact I think it would be straightforward to implement.

For now we don't know if we're going to be using Pants, and even if we do, I have to clarify with my team if this is even a strict requirement or if we can do without that

Well, I was more hinting towards you implementing it if you need it... 🙂

If we need this, we may well decide to implement it ourselves