Skip to content

Add docs for jarjar integration for main jar task #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
noeppi-noeppi merged 1 commit into from
Jan 11, 2026
Merged

Add docs for jarjar integration for main jar task #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions wiki/modgradle/docs/meta/setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -221,6 +221,25 @@ artifacts {
In this example, both sources and javadoc jar-files will be created during the build process.
However, only the sources will get published to maven and uploaded to mod hosting websites.

### Using JarJar as the main artifact

By default, ModGradle uses the `jar` task as the main artifact for publishing and uploading.
You can switch to using the `jarJar` task (and optionally adjust classifiers) like this:

```groovy
artifacts {
useJarJar(true)
}
```

This makes ModGradle use `jarJar` as the main artifact.
With `true`, it also applies the common “thin + bundled” layout:

- `jar` → `-thin`
- `jarJar` → no classifier

If you want to use `jarJar` without changing classifiers, call `useJarJar()` without arguments.

## resources

The `resources` block allows to specify in which files parameter expansion should take place.
Expand Down