Upgrade to Pants 2.15 and to scie-pants (#11)

Author: Benjy Weinberger

.github/workflows/pants.yaml

@@ -19,20 +19,15 @@ jobs:
     name: Perform CI Checks
     needs: org-check
     runs-on: ubuntu-20.04
-    strategy:
-      matrix:
-        # The python version to run Pants itself on.
-        python-version: [3.9]
     steps:
     - uses: actions/checkout@v3
-    - uses: pantsbuild/actions/init-pants@v2
+    - uses: pantsbuild/actions/init-pants@v4-scie-pants
       # This action bootstraps pants and manages 2-3 GHA caches.
       # See: github.com/pantsbuild/actions/tree/main/init-pants/
       with:
-        pants-python-version: ${{ matrix.python-version }}
-        # cache0 makes it easy to bust the cache if needed
+        # v0 makes it easy to bust the cache if needed
         # just increase the integer to start with a fresh cache
-        gha-cache-key: cache0-py${{ matrix.python-version }}
+        gha-cache-key: v0
         # The Kotlin backend uses named_caches for Coursier state,
         # so it is appropriate to invalidate on lockfile changes.
         named-caches-hash: ${{ hashFiles('3rdparty/jvm/default.lock') }}
@@ -47,14 +42,14 @@ jobs:
         # See https://pants.readme.io/docs/using-pants-in-ci for tips on how to periodically clean it up.
         # Alternatively you change gha-cache-key to ignore old caches.
     - name: Bootstrap Pants
-      run: ./pants --version
+      run: pants --version
     - name: Check Pants config files
-      run: ./pants tailor --check update-build-files --check
+      run: pants tailor --check update-build-files --check
     - name: Lint, compile, and test
-      run: ./pants lint check test '::'
+      run: pants lint check test '::'
     - name: Package / Run
       run: |
-        ./pants package ::
+        pants package ::
     - name: Upload Pants log
       uses: actions/upload-artifact@v3
       with:

3rdparty/jvm/default.lock

@@ -1,6 +1,6 @@
 # This lockfile was autogenerated by Pants. To regenerate, run:
 #
-#    ./pants generate-lockfiles
+#    pants generate-lockfiles
 #
 # --- BEGIN PANTS LOCKFILE METADATA: DO NOT EDIT OR REMOVE ---
 # {

README.md

@@ -13,15 +13,17 @@ for some other example layouts.
 
 # Running Pants
 
-You run Pants goals using the `./pants` wrapper script, which will bootstrap the
-configured version of Pants if necessary.
+You run Pants goals using the `pants` launcher binary, which will bootstrap the
+version of Pants configured for this repo if necessary.
+
+See [here](https://www.pantsbuild.org/docs/installation) for how to install the `pants` binary.
 
 # Goals
 
 Pants commands are called _goals_. You can get a list of goals with
 
 ```
-./pants help goals
+pants help goals
 ```
 
 Most goals take arguments to run on. To run on a single directory, just use the directory name.
@@ -30,19 +32,19 @@ To recursively run on a directory and all its subdirectories, add `::` to the en
 For example:
 
 ```
-./pants lint src: 3rdparty::
+pants lint src: 3rdparty::
 ```
 
 You can run on all changed files:
 
 ```
-./pants --changed-since=HEAD lint
+pants --changed-since=HEAD lint
 ```
 
 You can run on all changed files, and any of their "dependees":
 
 ```
-./pants --changed-since=HEAD --changed-dependees=transitive test
+pants --changed-since=HEAD --changed-dependees=transitive test
 ```
 
 # Example Goals
@@ -52,45 +54,45 @@ Try these out in this repo!
 ## Run `ktlint`
 
 ```
-./pants fmt ::  # Format all files.
-./pants fmt src/jvm  # Format only files in this directory (non-recursively).
-./pants lint src/jvm::  # Check that all files under `src/jvm` are formatted (recursively).
+pants fmt ::  # Format all files.
+pants fmt src/jvm  # Format only files in this directory (non-recursively).
+pants lint src/jvm::  # Check that all files under `src/jvm` are formatted (recursively).
 ```
 
 ## Check compilation
 
 ```
-./pants check ::  # Compile everything.
-./pants check src/jvm/org/pantsbuild/example/json/JsonExample.kt  # Compile a file and its deps.
+pants check ::  # Compile everything.
+pants check src/jvm/org/pantsbuild/example/json/JsonExample.kt  # Compile a file and its deps.
 ```
 
 ## Create a binary file
 
 Writes the result to the `dist/` folder.
 
 ```
-./pants package src/jvm/org/pantsbuild/example/json  # Build binaries in this directory.
-./pants package ::  # Create all binaries.
+pants package src/jvm/org/pantsbuild/example/json  # Build binaries in this directory.
+pants package ::  # Create all binaries.
 ```
 
 ## Determine dependencies
 
 ```
-./pants dependencies src/jvm::
-./pants dependencies --transitive src/jvm::
+pants dependencies src/jvm::
+pants dependencies --transitive src/jvm::
 ```
 
 ## Determine dependees
 
 That is, find what code depends on a particular files.
 
 ```
-./pants dependees src/jvm/org/pantsbuild/example/json::
-./pants dependees --transitive src/jvm/org/pantsbuild/example/json/JsonExample.kt
+pants dependees src/jvm/org/pantsbuild/example/json::
+pants dependees --transitive src/jvm/org/pantsbuild/example/json/JsonExample.kt
 ```
 
 ## Count lines of code
 
 ```
-./pants count-loc ::
+pants count-loc ::
 ```