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

Upgrade to Gradle 4.7 #913

Closed
wants to merge 2 commits into from
Closed

Upgrade to Gradle 4.7 #913

wants to merge 2 commits into from

Conversation

3flex
Copy link
Member

@3flex 3flex commented May 20, 2018

I saw this was previously merged in #877, but somehow the changes are no longer in master.

@arturbosch
Copy link
Member

hey, yes I did the mistake to drop the commits instead of reverting them.
The new version of kotlin-dsl breaks our gradle plugin so we reverted this two commits to release new versions until @Mauin 's gradle rework is done.

@3flex
Copy link
Member Author

3flex commented May 21, 2018

What broke in the Gradle plugin with 4.7? I had a quick look at the gradle issues raised but couldn't see any related to this, except #876 which looks like it was trying to fix an issue that didn't actually exist.

CI checks on this PR pass...

I'd just close this but I'm trying to work on #485, and using latest Gradle may help (Kotlin DSL includes kotlin-compiler-embedded and there are some changes to the way classpath is calculated in the latest Kotlin DSL versions, so being able to just use the latest Gradle version may help avoid those bugs so having this merged now so I can rebase on top instead of waiting for the Gradle rework will help me)

Alternatively I'll just merge these two commits in my branch for the moment.

@arturbosch
Copy link
Member

That's exactly what was wrong: the classpath calculation. It seemed like the dependencies were not transitive anymore and we had to include every used dependency manually.

You can try to merge these two into your branch, increment the versions, build everything, and try to use detektCheck. You should see the classpath errors.

@3flex
Copy link
Member Author

3flex commented May 21, 2018

I'm still confused because detektCheck runs as part of the Travis CI check which passes on this PR... but I'll close, there must be something I'm missing (is it only when running detektCheck on other projects, and not when running on detekt itself?)

@3flex 3flex closed this May 21, 2018
@Mauin
Copy link
Collaborator

Mauin commented May 21, 2018

Just to confirm: The Gradle Plugin re-work also shows the same issue with Gradle v4.7 and due to bugs with the Gradle Test Kit will require Gradle v4.8 to be released as well.

@arturbosch
Copy link
Member

@3flex yes the selfanalysis runs fine. Its when you build a new version of the plugin and tries to run detektCheck, then the missing dependency exception occur with 4.7.

@arturbosch arturbosch added this to the RC7-2 milestone Jun 1, 2018
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.

None yet

3 participants