-
-
Notifications
You must be signed in to change notification settings - Fork 448
[7.0] Re-implement Mavenizer invocation as a task #996
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.
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
[7.0] Re-implement Mavenizer invocation as a task #996
Conversation
All documentation pages will be moved to MinecraftForge/Documentation OR its own repo if necessary when the time comes
docs/Overview.md
Outdated
|
|
||
| ```groovy | ||
| plugins { | ||
| id 'net.minecraftforge.gradle' version '7.0.0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replacing 7.0.0 with or similar would help prevent people from adding an old version, instead encouraging them to look on Gradle Plugin Portal. See EventBus' readme for an example of this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a way that we can get a badge in the file with the latest version number.
May be worth adding that badge.
[](https://plugins.gradle.org/plugin/net.minecraftforge.gradle)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It won't be up on the plugin portal until 7.0.0, but yeah, that's worth putting on the README and the main documentation page.
This PR re-implements the Mavenizer invocation to once again be a Gradle task that is run. However, this time I've taken the proper measures to ensure that the dependency resolves consistently with its assigned resolvable configuration (i.e. a classpath) and that the proper attributes are accounted for in time.
Additionally, ForgeGradle will check if the output directory for the Minecraft dependency exists before the
compileJavatask is run. This does not fix any issues, but instead gives a useful error message telling the consumer to re-sync the project rather than leaving them stuck with cryptic "class not found" compiler errors.If no feedback or changes are requested by the end of the day, I will squash and merge this PR and close any related issues (except for #992).