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

Pants

```1) fork `while 1; do ./pants changed-loop $target; ./pants bundle.npm $target; done` (runs forever)
2) run `./pants run.npm -- webpack-server` (runs forever)
3) iterate on changing sources```

no need for a changed-loop in the really crude get it working world if you're going to resort to while 1

when just editing files in the named target

<@U046T6T90>: ^ that look like something you guys could use?

you have something similar... wondering whether that would be a sufficient replacement

I'd have to look at the details of this thing, but possibly yeah

Which does pretty much what you describe there

<@U053H6LQS> and I have been discussing potential syntax for specifying shading rules on a `jvm_binary`. Lots of options, but I think we’re settling between
```jvm_binary(name=’my-app’,
  shading_rules = [ 
    Shading.Exclude(‘pattern’),
    Shading.Relocate(from, to),
  ],
)
```

and 
```
jvm_binary(name=’my-app’,
  shading_rules = shading_rules([ 
    Shading.Exclude(‘pattern’),
    Shading.Relocate(from, to),
  ], … &lt;reserved for more arguments&gt; ...),
)
```

The latter option we both think is uglier, but it follows the same pattern used by `jar_rules([])`

I think the `jar_rules` wrapper looks outdated and is unnecessary to include in BUILD files, in the same manner that `pants()` was

If the list is of uniform type I like the bare list

jar_rules might not be of the same type though

so that would need to split into 2 parameters

I'm excited to see shading support for users!

<@U04S45AHA>: qq, in your comment on <https://rbcommons.com/s/twitter/r/2715/> you mentioned using a factory for GR like `GoalRunner.Factory(options_bootstrapper, working_set, runtracker, reporting).setup()` etc - is there some benefit to using a factory there vs just moving runtracker and reporting directly into GoalRunner.__init__()?

Just the mentioned one of no side-effects in constructors allowing sane tests and reasoning in general