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

Pants

<@U04S45AHA>:  Also, what is the diffstat of the overall change?

ie ClasspathEntry now carries the .ivy cache path in addition to the .pants.d/ivy/... path

57 files changed, 1041 insertions(+), 1243 deletions(-)

Um - the ArtifactClasspathEntry subclass to be precise

In the end it doesn't introduce any new concepts, it just kills 3+ old concepts that were half-baked/redundant to ClasspathProducts

I don't fix the JarLibrary UI, but I do fix resolution of these

The UI fix can come after, leaving for you and your design doc

i got started on the global removal patch

<@U053H6LQS>: if we backport fedor's zinc fix for java output, will square be ready to switch? i'd also like to kill jmake =x

alright, with <https://rbcommons.com/s/twitter/r/2806/> applied, the zinc/sbt/pants jar patchset compiles all of `./pants --config-override=pants.ini.isolated compile examples/{src,tests}/{java,scala}/::`

Yes, I’m ready to switch to zinc. I would really like Fedor’s fix in there, but if the problem is a bug in jmake, I will switch anyway.

<@U04S45AHA>: We have a plugin that reads from ivy_jar_products that I’d like to switch to compile_products.  First we need to get the path to the resolved .jar file, but also we’d like to get the original org/name/classifier that was requested so we can reliably strip the version off of the resolved filename.  Currently we do this by walking throug the ivy_jar_products data.  Will your new patch associate the M2Coordinate that was used to request a jar for the classpath with the classpath_products entry?

<@U053HHEDG> ^^ I’m talking about our copy-signed-jars plugin

I do a similar conversion for android stuff

That is awesome, thanks John. I am really excited for this change.

<@U053H6LQS>: output fix is up over here: <https://rbcommons.com/s/twitter/r/2810/>

Would there be interest in adding an optional `pylint` task to the `compile` goal for `python_library` targets?

Oh, I must have missed.  All I did was scan the options reference page

Neat, then I can use this for `tsar` the next time there is an internal release of `pants`