Skip to content
This repository has been archived by the owner on Aug 20, 2024. It is now read-only.

Allow for new plugin mechanism #78

Open
ambition-consulting opened this issue Sep 20, 2016 · 2 comments
Open

Allow for new plugin mechanism #78

ambition-consulting opened this issue Sep 20, 2016 · 2 comments
Labels

Comments

@ambition-consulting
Copy link

As stated here, since gradle 2.1 a new plugin mechanism (using "id") should be supported. When applied, I get various errors on URI schemes not being supported though. Only using the legacy plugin mechanism (with buildscript and apply plugin) will result in correct behaviour.

@ysb33r
Copy link
Owner

ysb33r commented Sep 20, 2016

Indeed. The problem is described on the Gradle Forum: https://discuss.gradle.org/t/plugins-block-does-not-handle-classpath-correctly-under-certain-circumstances/18222/9.

IIRC it was fixed in the Gradle 3.0 release.

@ysb33r ysb33r added the gradle label Sep 20, 2016
@ambition-consulting
Copy link
Author

ambition-consulting commented Sep 20, 2016

I am currently using gradle 2.12. When I switch to gradle 3.0, I will double check if it works. If so, a short hint in the README might help?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants