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 can't find the actual correct syntax in the documentation

<@U0JSN507N>: yea, lower in the same file

I think both of our uses are not necessary

We could instead rely on the address mapper <@U0D9ZAH98>

<@U06A03HV1>: thanks! I'm trying to use a non-standard Maven repo. Am I reading correctly that I have to specify group/artifactId/version and set an `url` for each of those jars, even though the url will just reiterate the same group/artifact/version?

<@U0JSN507N>: no: if you set an ivy config that includes the non-standard repo, you should be good.

<@U06A03HV1>: How/where do I set my pants ivy config?

best hit i found was <https://pantsbuild.github.io/JVMProjects.html#toolchain>

`./pants help-advanced resolve.ivy` should have more info on that

...hm, except that doesn't seem to be where it is configured. sorry for the quick answer.

<@U0JSN507N>: ` ./pants help-advanced ivy` mentions `ivy-settings.xml`

<@U0607UFLH>: what is a reason to use #from_cache? What are you doing with result?

<@U0JSN507N>: if you look in the pants ivysettings you can see where we set the local m2 repos for android sdk. Should be at least a starting point. 
<@U0D9ZAH98>: maybe talk with @pl about it, he has a better idea of how hard that may be to replace.

<@U0607UFLH>: Yup, gotcha. I'm now reading through the Ivy documentation <http://ant.apache.org/ivy/history/latest-milestone/tutorial.html>

Patrick already answered question, thanks!

I mentioned a while back that I'm doing a bakeoff between Pants and Bazel. Bazel has a `genrule` that lets you run arbitrary code. How do you do that in Pants?

It is, first and foremost, _strongly discouraged_

Though I think we recently added an escape hatch to allow it

If you really want to run arbitrary code, it's suggested that you create a custom task as a loose source plugin and have it run it for you over the appropriate targets

if you're interested in adding a build step, the task api is the way to do it: <https://pantsbuild.github.io/dev_tasks.html>

This will get you caching and scheduling and all of the other goodies out of the box