Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

We have a use-case for having multiple targets publish to the same `(org, name)` but with different `classifier`s. Is there opposition to allowing multiple targets contribute (non-intersecting) `Publication`s to a single artifact publish?

i don't mind. as long as there is some checking to ensure that different targets aren't overwriting one another in that same namespace.

...er. <@U053HHEDG> : that may run afoul of the pushdb

since currently we're assuming you're publishing everything for a particular version at once

and having them be in separate targets would allow for a split publish

Yeah, I would have to change the exiting jar publish code to consolidate the Publications before publishing them

it seems like it would be better just to use different org/names maybe?

<@U053HHEDG>: that's not enough though... what if i only have one of the two targets in the context?

Uhg, you’d get a published artifact with missing files

Hmm, maybe we can mark a `provides=` artifact as “partial”, and make a new target that references targets with partial provided artifacts? We could add a task to copy (or symlink) the publishable products produced by the partial artifacts, and the jar_publish would just publish that

<@U053HHEDG>: what's the usecase for splitting here?

or, what's the usecase for having a split where things have the same name?

this is easy if they have different names

I agree; unfortunately we already are publishing a few artifacts like this with maven that have lots of consumers that expect things to be this way..

The particular case is that we publish a shaded jar with `classifier=shaded`, and also the java_library() it depends on

It looks like we can use —publish-extras and —individual-plugins and an internal wrapper around jvm_binary to get it to publish a just a single Publication with the `shaded` classifier, but there’s still the problem of it having the same `provides` as the jar_library

Anyway, I’m heading home for the day now, we can think more on this tomorrow

would native support for a shaded publish be easier?

If it allowed for also publishing the java library under the same (org, name)

i don't see why not... it would just be one target at that point, no?

jvm binaries can only have one `source` file though :stuck_out_tongue:

We could maybe make a `shaded_library` I guess?

The published binary is actually downloaded and run I think

It’s the whole fatjar; people are using our internal nexus to distribute executables