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

Pants

I'll straw man the RB based on that and see what other folks say there

So you have something that drives the need to have the address spec_path != sources_rel_path

I know other codegen just synthesizes addresses that work in this regard to align with where the sources are

Is that something you could do if I deprecated the parameter?

For example, SimpleCodeGen does this address alignment, but also passes in sources_rel_path, which is redundant and I can kill that today

I think our need fell out of some complicated `java_sources` hackery that is now dead.  If `SimpleCodeGen` can get around this, so can we.  In fact I'll probably just port this task over to `SimpleCodeGen` soon

Though I'm curious, why do you want to kill this?

Because there is no need to expose an unused parameter whose only purpose for an end user is to allow violation of the rule a target owns sources only in it's tree

...and reasonable but unused is an infinite pit for parameter addition

Not suggesting that it should remain if it's unused

Its unused save for SimpleCodeGen in pants

For that matter I might have been passing it as a matter of cargo-cult/paranoia rather than any good reason

And I suspect that `SimpleCodeGen` usage is ultimately derived from my own usage internally

So yeah, mystery solved.  If you can kill it upstream, we'll kill it when we upgrade

I commented on the RB. We have uses of  `sources_rel_path` in our ruby plugin but its just following the example of other targets.  We don’t need it for anything so please kill it.

Hey <@U06A03HV1> and/or <@U066LC126> can you take another look at <https://rbcommons.com/s/twitter/r/2729/> ?  It's not clear to me that it's safe to remove the symlink indirection there, but otherwise the change is ready to go

<@U053HNE90>: the compile_classpath is guaranteed to contain only things that exist under .pants.d

in the case of ivy jars, that is accomplished via the symlinks