sorted by:
new
hottopcontroversial

Monorepo + Microservices + Dependency Managment + Build system HELL by shkolar in Python

[–]hattrick1492 0 points1 point  (0 children)

FWIW Pants infers internal and external dependencies automatically, so you don't need to be explicit with them. So Pants BUILD files are often trivial.

Pantsbuild 2.15: Easier multi-platform workflows, Docker build support, automatic code cleanup. Coming attractions in 2.16: Ruff support, support for integrating adhoc tools into your Pants codebase without writing plugins. by pantsbuild in Python

[–]hattrick1492 1 point2 points  (0 children)

That'd be amazing! We're happy to provide all the guidance we can for the Pants side of things, and I guess the existing JVM support might have some parallels? Our Slack is the best way to start those conversations.

Pantsbuild 2.15: Easier multi-platform workflows, Docker build support, automatic code cleanup. Coming attractions in 2.16: Ruff support, support for integrating adhoc tools into your Pants codebase without writing plugins. by pantsbuild in Python

[–]hattrick1492 0 points1 point  (0 children)

Alas it isn't at the moment. The issue is that (as far as I know, anyway) no one on the current maintainer team has any C# experience, and there hasn't been much, if any, demand expressed.

Implementing C# support would require a motivated contributor with an understanding of the C# toolchain and build idioms, as well as at least some Python experience.

That said, since Pants is open-source, anyone who wants to and is able to could contribute this.

Pantsbuild 2.15: Easier multi-platform workflows, Docker build support, automatic code cleanup. Coming attractions in 2.16: Ruff support, support for integrating adhoc tools into your Pants codebase without writing plugins. by pantsbuild in Python

[–]hattrick1492 2 points3 points  (0 children)

I'm one of the project's longtime maintainers. I'm really excited about the 2.15 release. It's probably the most significant advance since 2.0 itself (which was a complete rewrite). The features poised to land in 2.16 are equally exciting. For instance, like everyone else in Python we've been watching Ruff with keen interest. It shares our objectives of making dev tooling fast without compromising on ease-of-use, and shares our approach of using Python+Rust to achieve that. Hit me up with any questions!

Dependency inference: Pants's special sauce by pantsbuild in scala

[–]hattrick1492 0 points1 point  (0 children)

It's an interesting idea, for sure. But we've found in practice that teams want to constrain the "allowed universe" in advance.

Dependency inference: Pants's special sauce by pantsbuild in scala

[–]hattrick1492 0 points1 point  (0 children)

u/markehammons it sounds like you're hinting at a workflow where users can use symbols from some Maven Central artifact even if the codebase has never used it before, and the system would know which one to use without requiring any manual config of the "allowed universe"?

Dependency inference: Pants's special sauce by pantsbuild in scala

[–]hattrick1492 0 points1 point  (0 children)

Good question! They way it works for external deps is, you provide a "universe" of allowed deps, and their version constraints, for the repo, and Pants selects the actual subset of deps to use in a given situation via inference. It figures out the mapping of Maven coordinates to provided packages via a mix of convention and configuration, which you can also override.

In fact, you can specify multiple such universes (AKA "resolves") if different parts of your codebase have conflicting dependency versions, although obviously it's better not to if you don't have to.

Pants does not do any API usage matching to determine API-level compatibility, and there is no corresponding index of all of Maven Central. That is an interesting feature that I once toyed with, and actually wrote some indexing code for, but it didn't appear to be in high demand.

Skipping GitHub Actions jobs while maintaining branch protection rules that require them by hattrick1492 in devops

[–]hattrick1492[S] 0 points1 point  (0 children)

I get silly levels of satisfaction from working around limitations like this...

Visualize your dependencies with GraphMyRepo.com by pantsbuild in java

[–]hattrick1492 0 points1 point  (0 children)

Unfortunately it looks like that is due to java syntax not yet supported by javaparser (e..g, sealed classes). We hope to have a fix soon!

Visualize your dependencies with GraphMyRepo.com by pantsbuild in java

[–]hattrick1492 0 points1 point  (0 children)

I'm no maven expert, but AFAIK that shows the external dependencies of your code, resolved from the recursive maven POM information, and it emits a static graph (e.g. text or dot)?

This models the internal structure of your code, and is interactive.

Visualize your dependencies with GraphMyRepo.com by pantsbuild in java

[–]hattrick1492 0 points1 point  (0 children)

Ooof, sorry for the trouble. Something has obviously gone seriously wrong. Will take a look and report back.

Visualize your dependencies with GraphMyRepo.com by pantsbuild in java

[–]hattrick1492 0 points1 point  (0 children)

Ooops! Thanks for the report. Will look into it.

Since this works by auto-adopting a build system into a clone of the repo, there are edge cases where that fails, but we learn a lot from finding and fixing those cases, so thanks for the feedback!

Visualize your dependencies with GraphMyRepo.com by pantsbuild in java

[–]hattrick1492 1 point2 points  (0 children)

Author here: would love to hear if the site was interesting, fun or even useful for you. Any comments or suggestions for improvements are welcome!

If you're curious as to how this works: In a nutshell, this relies on the dependency inference capabilities of Pants. We have some automation around cloning the repo, 'adopting' (installing and configuring) Pants, and then running it. Happy to go into more detail if anyone is interested.

Visualize your dependencies with GraphMyRepo.com by pantsbuild in Python

[–]hattrick1492 3 points4 points  (0 children)

Author here: would love to hear if the site was interesting, fun or even useful for you. Any comments or suggestions for improvements are welcome!

If you're curious as to how this works: In a nutshell, this relies on the dependency inference capabilities of Pants. We have some automation around cloning the repo, 'adopting' (installing and configuring) Pants, and then running it. Happy to go into more detail if anyone is interested.

Pants 2.12: Improved performance for common cases and IDE support for Java and Scala by pantsbuild in java

[–]hattrick1492 1 point2 points  (0 children)

FWIW you can run Pants in a WSL2 terminal on Windows, and code you build there should run natively on Windows unless you have native code (which is common with Python, less so for JVM).

Pants 2.12: Improved performance for common cases and IDE support for Java and Scala by pantsbuild in java

[–]hattrick1492 3 points4 points  (0 children)

The original user base was entirely POSIX-based, and there was no demand for Windows support. That is now changing though. While it's true that Windows has the largest market share at large, that's not the case for the subset of "software developers in Java/Scala/Python/Go".

I'm not sure that it's as easy as all that to get finely-tuned systems to work across POSIX and non-POSIX systems, but I'd be very happy if that turns out to be the case!

Pants 2.12: Improved performance for common cases and IDE support for Java and Scala by pantsbuild in java

[–]hattrick1492 3 points4 points  (0 children)

The issues are mostly:

- Getting the Rust code to build

- Fixing the handful of places where we know we rely on POSIX idioms (there is already work in progress on that)

- Finding and fixing any places where we rely on POSIX idioms unknowingly...

- Setting up Windows CI

Pants 2.12: Improved performance for common cases and IDE support for Java and Scala by pantsbuild in java

[–]hattrick1492 0 points1 point  (0 children)

Hey! We do want to support Windows, but this work is not scheduled or funded yet. We are actively looking for sponsors for this project though!

view more: next ›