-
Notifications
You must be signed in to change notification settings - Fork 168
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 this project dead? #112
Comments
I recommend using the Insights -> Network tab to figure out which fork is most active. My fork was initially created specifically for the OpenComputers project, and I have no plans on further maintenance beyond that. |
You can also use Insights -> Forks. My fork was an attempt to upgrade the luaj project from old JDKs (1.2 - 1.4) to JDK 8+, and also with newer versions of ant (1.10+). It was performed as a subproject of another personal project of mine, and it seems to work with newer JDKs (even 17) for JSE. I managed to run it successfully on Windows 10, Linux Ubuntu 22.04 and MacOSX Monterey 12.6.3. However I wouldn't recommend it for production if it's what you have got in mind (at least not before thorough testing first). The issue is that I am much less familiar with ant than with maven or gradle. If your project includes deployment on mobiles, my fork is not for your use case. I am not familiar with the JME development and did not manage to compile it in this case (JME doesn't support many new language constructs, including generics). Therefore the JME part is not compiled by default in my fork (though the code is still there, and a compilation can still be attempted, with no guarantee, with Best wishes |
I merged a few of the pr's here and use mine for https://github.com/jsmacros/jsmacros-lua im not exactly actively maintaining it, but if people were to send pr's I would read them over at some poimt |
Dear @wagyourtail, Best regards |
I did extensive clean up and rework of luaj in my fork, common formatting, convert to maven, tests as junit5 as well as some bug fixes but Im not actively maintaining it. So while anyone is free to use my work I do not plan to go through the work again to make it match another fork. |
@fabrice-ducos part of my fork was merging @farmboy0 's fork, which converts to maven. iirc this includes java 8 update... as well as
|
Dear @farmboy0, @wagyourtail. |
Hi. My project was created for the Spigot plugin for Minecraft. It's a fix for some issues with the Spigot API integration, so there probably won't be any significant modifications for other projects. It's not currently in development, so I don't think there will be any further research. I apologize for the late response and thank you for your interest in the project. |
Hi. I'd recommend using @wagyourtail's fork ( Other fork details:
I noticed @lenrik1589's fork added Java 17 use of Looks like @hashsploit's fork is no longer maintained, it appears the only changes was to remove JME support and add support for Java 1.8+ for use in Maven + JitPack. https://github.com/hashsploit/clank/blob/feature/overhaul/build.gradle.kts#L64 I plan on using luaj in conjunction with LWJGL3 for scripting. Thanks for keeping this project alive! |
i am not sure i wish to continue working on the project, as i worked on it in conjunction with Kingdom-of-The-Moon/FiguraRewriteRewrite and (now inaccessible, likely private) Kingdom-of-The-Moon/luaj, which transitioned into FiguraMC/Figura and respectively FiguraMC/luaj but I have been removed from the team of people who work on it which made me lose all motivation to continue active work, i might keep working on it, but even slower than i did before… |
Which is the serious continuation of it?
https://github.com/LuaAbility/luaj
https://github.com/hashsploit/luaj
https://github.com/fabrice-ducos/luaj
https://github.com/elroy93/luaj
https://github.com/alekso56/luaj
https://github.com/wagyourtail/luaj
https://github.com/asiekierka/luaj
https://github.com/farmboy0/luaj
@MINUTE1084 @hashsploit @fabrice-ducos @elroy93 @alekso56 @wagyourtail @asiekierka @farmboy0
The text was updated successfully, but these errors were encountered: