Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
wagyourtail authored Nov 19, 2024
1 parent 2c7c5a9 commit 292c260
Showing 1 changed file with 7 additions and 6 deletions.
13 changes: 7 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -180,21 +180,22 @@ I do not automatically make the configuration shadowed into your output.

#### Including newer dependencies on lower java version building

This is not recommended due to the following but is still possible.
It is recommended to just shade dependencies into your project and downgrade the combined output.
It is **strongly** not recommended due to the following but is still possible.
instead, you *should* just shade dependencies into your project and downgrade the combined output.
The dependencies may not be correctly represented in the pom with this method.

There may be issues with gradle metadata breaking because of how early gradle checks the java version,
you can disable this by setting `mavenPom` and `artifact` in the `metadataSources` function on repositories
to explicitly disable gradle metadata.
There may be issues with metadata breaking because of how early gradle checks the java version,
you can disable this by setting `artifact` in the `metadataSources` function on repositories
to explicitly disable metadata, if you are lucky, you may be able to include `mavenPom` as well, so trasitive dependencies can resolve, otherwise
**transitive dependencies will not be included**, and must be included manually.

for example:

```gradle
repositories {
mavenCentral {
metadataSources {
mavenPom()
mavenPom() // may still break with this line on some dependencies
artifact()
}
}
Expand Down

0 comments on commit 292c260

Please sign in to comment.