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

Gradle 2.13 - ClassNotFoundException for org.gradle.logging #58

Closed
eoftedal opened this issue Sep 26, 2016 · 3 comments
Closed

Gradle 2.13 - ClassNotFoundException for org.gradle.logging #58

eoftedal opened this issue Sep 26, 2016 · 3 comments

Comments

@eoftedal
Copy link

eoftedal commented Sep 26, 2016

...
Caused by: java.lang.ClassNotFoundException: org.gradle.logging
   at com.netflix.nebula.lint.StyledTextService.<init>(StyledTextService.groovy:17)
   at com.netflix.nebula.lint.plugin.LintGradleTask$1.lintFinished(LintGradleTask.groovy:48)
...

Looks like you are accessing some gradle internal features, and that those are not working properly

@eoftedal
Copy link
Author

I would suggest that instead of failing if none can be found, you default to a dummy implementation that just does non-colored output using standard output mechanisms.

@eoftedal eoftedal changed the title Gradle 3.1 - ClassNotFoundException for org.gradle.logging Gradle 2.13 - ClassNotFoundException for org.gradle.logging Sep 26, 2016
@eoftedal
Copy link
Author

eoftedal commented Sep 26, 2016

(Had to rename this issue, because I was fooled by gradlew which invoked an older version of gradle)

I'm wondering if there's a bug here: https://github.com/nebula-plugins/gradle-lint-plugin/blob/master/src/main/groovy/com/netflix/nebula/lint/StyledTextService.groovy#L21
Shouldn't it say:
factoryClass = Class.forName('org.gradle.logging.StyledTextOutputFactory')
instead of
factoryClass = Class.forName('org.gradle.logging')

@rspieldenner
Copy link
Contributor

fixed in #61

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 a pull request may close this issue.

2 participants