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

Pants

But yes, in my description origin is pantsbuild/pants

Could probably make that more explicit if we wrote it up

Folks - I'm working up a deprecation removal RB - we have 1 - and after that the release prep RB.  I estimate ~4-5pm release
Let me know if you have anything close to that wire you want to get into 0.0.48

<@U04S45AHA>: are you going to try to work in the jarjar fix?

<https://rbcommons.com/s/twitter/r/2846/>

<@U053HNE90>: another alternative would be to change the rbt template so that it includes closes #&lt;PR-number&gt; for each bug. Then the commit that closed it would be the last comment on the PR.

That might be better, doesn't make it unduly difficult for contributors that can't push their own commits

The rbt patch though already has that info - so it would be double-entered in the commit message

ah, it hasn’t landed yet. <https://reviews.reviewboard.org/r/6833/>

Is there a way to get ivy to generate a partial classpath file even if some resolves fail?

Trying to get things to keep trucking if a couple artifacts don’t have associated javadocs for `idea` and `export`.

So - that should have been solved a long time ago!

If you add &lt;artifact/&gt; child elements to a dependency, they _must exist_
If you add a javadoc or sources conf mapping, they need not exist and should map or not map as the situation demands
If you want to do both, you need to add &lt;include/&gt; child elements

Are you getting the error in new code? You should not get that sort of error in master code

I’m getting it in new code, let my try again in master real quick

Master _should_ work all good, I spent a good deal of time getting this right and re-enabling commented out tests this week

I am still getting the problem in master. I believe it is caused by a jar which has `url=` set to the local fs, and thus cannot have javadocs or sources.

Causing it to fail with `export --libraries --libraries-sources --libraries-javadocs`

The thing to grab is the generated ivy.xml and command line, edit and play

My thought on this was to run 2 resolve passes, one for binaries (must succeed) and a second for sources and javadoc (ok to fail)