-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Suggestions for plugin improvements #15
Comments
Is there currently a collision or need to redirect? As for publications, there's #10, but as I'm currently the only person actively working on the fork I've not really looked at it. As for compatibility, I want to finish the backporting before dropping any compatibility and where I work there's a few people still on Gradle 4 so initially it'd probably be Gradle 4.10 as lowest version (to get access to some of the new APIs) but I'm open to the idea of dropping Gradle 4 support a few months later :-) |
@deepy , agree with you regarding the minimal version. And yes, there are not collision at gradle.org (sorry for inconvenience). I'll take a look on publication and return with proposed PR (and build system configuration details) |
I think yes. |
Because of issue srs/gradle-node-plugin#315 I suggest to:
Rename plugin (to avoid collision on the plugin storage).Redirect source code to this project of the newly published pluginUse Gradle 5.4.1 (the latest one)The text was updated successfully, but these errors were encountered: