Skip to content
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

Fix HackyCompile for Gradle 5.1+ to ignore compilation time reporting. #625

Merged
merged 1 commit into from
Sep 12, 2019

Conversation

gabizou
Copy link
Contributor

@gabizou gabizou commented Sep 10, 2019

An annoyance with some of the Gradle changes involves this change causing a JavaCompile task to try and register itself as being performance logged. The issue is that with how hacky the compilation task is performed, something something NPE from missing listeners will happen with Gradle 5.1+.

Yes, it's been discussed about getting a replacement, and there's a discussion that's cropped up from the issue above, this PR simply puts a bandaid fix that works all the way up to Gradle 5.6.2 (latest release), tested on Windows 10, and macOS with Gradle versions 5.2.1, 5.1.1, 5.5, and 5.6.2. This will at least buy us some time to eventually proceed with a way forward for using artifact transformers, which is likely going to need some more time to migrate to (and of course, requires that a lot of people again migrate up Gradle versions).

@clienthax
Copy link

Tested on gradle 5.1.1, works.

@LexManos
Copy link
Member

This will work as a interm solution until #622 gets fully tested and the java location issues get resolved.

@LexManos LexManos merged commit e7b9b54 into MinecraftForge:FG_3.0 Sep 12, 2019
@gabizou gabizou deleted the fix/gradle-5.1+ branch September 12, 2019 23:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants