Skip to content

Commit

Permalink
Better command examples; fix version string location
Browse files Browse the repository at this point in the history
  • Loading branch information
DSouzaM committed Mar 4, 2025
1 parent fe4cc94 commit 2a476eb
Showing 1 changed file with 10 additions and 4 deletions.
14 changes: 10 additions & 4 deletions DEVELOPING.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,13 +19,19 @@ You can use the various commands in the [Gradle build lifecycle](https://docs.gr
Some examples (all executed from the root of the repository):

```bash
# Build all projects
# Compile all projects
./gradlew assemble

# Build only the native-gradle-plugin (for example)
# Run unit tests in all projects
./gradlew test

# Run functional tests in all projects
./gradlew funTest

# Compile only the native-gradle-plugin (for example)
./gradlew :native-gradle-plugin:assemble

# Build and run all tests
# Build and run all tests, complete (and very long) build
./gradlew build
```

Expand Down Expand Up @@ -53,7 +59,7 @@ To do this, first modify the project as necessary, and then build and publish th
The above command publishes to a "common" repository located at `build/common-repo`.

Next, update the project build files:
1. Update the version string. The version can be found manually by searching for the published artifacts in `~/.m2/repository/org/graalvm/buildtools/native/`, or alternatively by checking the `nativeBuildTools` property [here](gradle/libs.versions.toml).
1. Update the version string. The version can be found manually by searching for the published artifacts in `build/common-repo`, or alternatively by checking the `nativeBuildTools` property [here](gradle/libs.versions.toml).
2. Update the list of repositories to include and prioritize the common repo.

### Gradle
Expand Down

0 comments on commit 2a476eb

Please sign in to comment.