Skip to content

Commit

Permalink
lint
Browse files Browse the repository at this point in the history
Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
  • Loading branch information
ramonpetgrave64 committed Feb 9, 2024
1 parent a4e7ce4 commit ca401d7
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions internal/builders/gradle/README.md
Expand Up @@ -19,6 +19,7 @@ workflow the "Gradle builder" from now on.
- [Limitations](#limitations)
- [Generating Provenance](#generating-provenance)
- [Getting Started](#getting-started)
- [Multi-Project Builds](#multi-project-builds)
- [Private Repositories](#private-repositories)
- [Verification](#verification)

Expand Down Expand Up @@ -98,7 +99,8 @@ The Gradle builder requires you to specify the artifacts that you wish to attest
If you are using [multi-project builds](https://docs.gradle.org/current/userguide/intro_multi_project_builds.html), where each of your sub-projects' `src` are in separate subfolders, then you will need to add a task to copy over the artifact files to the root `./build` folder.

See this example to add to your sub-projects' `build.gradle.kts` file.
```

```kotlin
tasks.register<Copy>("copySubProjectBuild") {
from(layout.buildDirectory)
into("${rootProject.projectDir}/build/${project.name}")
Expand All @@ -111,7 +113,7 @@ tasks.named("build") {

This, for example, It will move `./app1/build/` and `./app2/build/` to `./build/app1/` and `./build/app2/`. You must then alter your input to `artifact-list`.

```
```yaml
...
artifact-list: >-
./build/app1/libs/app.jar,
Expand Down

0 comments on commit ca401d7

Please sign in to comment.