-
Notifications
You must be signed in to change notification settings - Fork 210
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
is the project dead? #315
Comments
I was also looking for a maintained fork. If there is not, maybe someone could take the task up and other contributors will join in? |
I tried to contact @srs via mail. Let's see if and what he'll answer. |
Since there doesn't seem to be anything happening here I forked it to https://github.com/node-gradle/gradle-node-plugin and started relocating the plugin, I mostly did this since I need #299 fixed but I kinda also want #316 |
thx! I try to contribute Gradle build cache support the coming days. |
@deepy Can you please enable Issues for the project? |
Sorry that I didn't get back. @srs did answer me that the project isn't dead and that he would be happy if someone would help manage it. I offered him my help. Unfortunately I didn't hear back since then. |
@iamareebjamal issues are enabled now :-) |
https://plugins.gradle.org/plugin/com.github.node-gradle.node - relocated plugin with a conditional fix for #299 now exists (since plugin portal does not handle snapshots) |
seems this can be a good replacement? https://plugins.gradle.org/plugin/com.liferay.node |
Hi. Sorry about being non-responsive. I have now started to work on this plugin again and I promise that I will start applying PR's. Also start adding other people wanting to contribute and help me manage this project. |
Great to have you back @srs ! |
nice. did you have a look at the changes in the fork https://github.com/node-gradle/gradle-node-plugin |
No, not yet. Would be happy to merge the code. What I am working on now will be tracked in 2.0 branch. Mostly towards cleaning up the plugin and make it more Kotlin friendly. |
Thanks @dlangerenken. |
@srs, looks like question is actual again: is project dead? For current moment I can resolve several issues, however I'd like to get owner's opinion before my coding. |
First I would like to thank you @srs for all you time and effort you put into this project. :) Secondly, I wanted to follow the previous comment, whether the project is dead now or not. :( I don't want to criticise, because I understand that maintaining open source software is a very time consuming job and at a certain point maybe more stress then fun. :/ But now there is a fork of this project https://github.com/node-gradle/gradle-node-plugin and I am not sure which one to use in the future. It would be very nice if @srs and @deepy can clarify what their plans with both projects are for the future. Thank's in advance. |
Since development has picked up again I'll start backporting (forwardporting?) to As long as this repo is a one-man show I'll continue working on the node-gradle "community" fork. Which ironically also is a one-man show (and like #315 (comment) also open to having more contributors). |
@srs maybe we should schedule a quick call some day and discuss the futures of these repositories? |
Hey, are there any updates regarding this situation? |
Yes. Don't use this project. |
Could a comment be added to the README and perhaps the Gradle plugin repository redirecting to https://github.com/node-gradle/gradle-node-plugin? I came here via #377 to find out. |
maybe it would be good to settle for a new location for a fork to be able to do PRs again.
The text was updated successfully, but these errors were encountered: