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

task 'classes' not found #5

Closed
robmoore opened this issue Jan 27, 2016 · 10 comments
Closed

task 'classes' not found #5

robmoore opened this issue Jan 27, 2016 · 10 comments

Comments

@robmoore
Copy link

I tried adding this to my build.gradle file and ran into the following error when building:

* What went wrong:
An exception occurred applying plugin request [id: 'com.gorylenko.gradle-git-properties', version: '1.4.10']
> Failed to apply plugin [id 'com.gorylenko.gradle-git-properties']
   > Task with name 'classes' not found in root project 'my-project'.

It looks like it assumes that I will have a classes task and I don't.

@n0mer
Copy link
Owner

n0mer commented Jan 27, 2016

@robmoore this plugin does not deal with 'classes' task in any way.

Maybe this is due to up-to-date check from #4

@robmoore
Copy link
Author

Odd. If I remove the plugin the issue isn't present and it wasn't present prior to adding the plugin.

@n0mer
Copy link
Owner

n0mer commented Jan 28, 2016

@robmoore please try previous version 1.4.7, will it work for you or not. This will show whether this error is caused by #4 or not :)

@thebignet
Copy link

@robmoore I've had this problem since 1.4.7. Try importing plugin the old way as described in https://plugins.gradle.org/plugin/com.gorylenko.gradle-git-properties

@robmoore
Copy link
Author

@thebignet Thanks for the tip. Using the old way works with all the versions I tried.

@n0mer I tried using the new way with 1.4.7-1.4.10 with no joy.

@n0mer
Copy link
Owner

n0mer commented Jan 28, 2016

@robmoore @thebignet i'm also using the old mechanism of importing this plugin.

let's return to this conversation, when gradle new plugin system will graduate from beta.

@robmoore
Copy link
Author

@n0mer It might be worth documenting this issue as I'm sure it will bite others. FWIW, I've used a number of other plugins using the new method and haven't had an issue with it until now.

BTW, I think I may be incorrect on what I said about the old way working with versions past 1.4.8. I just had to bump it back to 1.4.8.

@ezraroi
Copy link

ezraroi commented Feb 8, 2016

Looks like also when using the old buildScript with any version (1.4.6 -1.4.10) i am getting the classes error

n0mer added a commit that referenced this issue Mar 14, 2016
@n0mer n0mer mentioned this issue Mar 14, 2016
@sirgl
Copy link

sirgl commented Dec 15, 2016

I got this error again on version 1.4.17 with both old and new way of plugin import.

@sirgl
Copy link

sirgl commented Dec 15, 2016

Not reproduces in minimal possible configuration, I think it caused by parent project

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

No branches or pull requests

5 participants