Conversation
This reverts commit ff23253.
|
Ah this is why it wasn't working with 21. Why no merge yet after 3 months? |
|
@PerryCameron I think the original maintainer, @siordache, simply does not have time to regularly update the project anymore. He asked for co-maintainers a while ago and someone stepped up, but it seems that person also has abandoned the project. I currently have a patched version of the plugin installed locally that fixes this and an issue with kotlin build files and am thinking of forking this and publishing an updated version to plugin central (and of course continue to stream any patches upstream in case this repo gets active again). I didn't step up as a co-maintainer back then because this project is mainly Groovy and I am really a noob in that language, but maybe I should have. In the meantime, I have volunteered to become a co-maintainer, but @siordache did not reply yet. |
That sounds very promising 👍, Thanks! |
|
Thank you! Not yet. It's on my list. I will post here when it's done. |
|
@danielpeintner I have released a patched version of the plugin to plugin central. To use it, change the plugin id in your gradle build script fom Please report back if something doesn't work. And if it's of interest to anyone, I have done the same for the sister-plugin Badass-Jlink-Plugin. Sources for my patched version of the plugin: https://github.com/xzel23/badass-runtime-plugin |
Thank you a lot! It worked nicely 👍. |
Updates the runtime plugin to a fork with support for java 21, instead of the upstream https://github.com/beryx/badass-runtime-plugin. See beryx/badass-runtime-plugin#154 for more details. Also changed the java version back to 21.
* add runtime plugin for generating stand-alone images * add JReleaser configuration for github release and runtimes * Use runtime plugin fork Updates the runtime plugin to a fork with support for java 21, instead of the upstream https://github.com/beryx/badass-runtime-plugin. See beryx/badass-runtime-plugin#154 for more details. Also changed the java version back to 21. * Remove deploy github workflow We had a github workflow that would run on a tag push, creating a new release and uploading a zip of the language server. Jreleaser should take care of all that now, so the workflow is unnecessary. * Add changelog to github release notes So we don't have to manually add the release notes to the github release after it is published. I added a custom task to read in the full changelog, and parse out the entry for the latest version. The result is written out to a resources file that I pointed the github release config to. The jreleaser docs don't seem to be 100% clear on whether the changelog is actually what ends up in the release notes, but it would make sense to me, and the text in https://jreleaser.org/guide/latest/reference/release/github.html#_release_notes suggests it. --------- Co-authored-by: Miles Ziemer <mziemer@amazon.com>
|
I got co-maintainer status on this project from @siordache some years ago, but I have been too busy with other projects and have not worked with JavaFX in years. If anyone else want to step up and help maintain this plugin that would be great, but I think only @siordache have access to add co-maintainers. I will take a look at this PR. If I still have access as maintainer, I will merge this fix. |
| ext.badassRuntimePluginTag = Boolean.valueOf(badassRuntimePluginReleaseBuild) ? "v$ext.badassRuntimePluginVersion" : 'master' | ||
|
|
||
| group = 'org.beryx' | ||
| group = 'com.dua3.gradle' |
There was a problem hiding this comment.
If this is to be merged, then it would need to change back the original namespace org.beryx.
There was a problem hiding this comment.
Also remove all mention of the fork, and changes to groupId and description.
There was a problem hiding this comment.
I think what we want here is only the first commit in this PR.
Hi @DJViking, sorry, I have been really busy (like always), but I think I could step in here and do some maintenance work on this plugin. I do the same for its sibling, i.e., the jlink plugin by the same author. Hi @siordache, I think I could also help out a bit with this plugin. If you are okay with this, I volunteer to become a co-maintainer. |
|
@xzel23 could you please remove the last 3 commits from this pr so it can be merged? |
|
Hi @xzel23 , sorry for overlooking your previous request. I have now sent you an invitation to become a co-maintainer. |
|
Thank you @siordache. I think I'll have some time on the weekend to make the plugin Java 25 ready (and hopefully Gradle 9). |
|
@masterflitzer I'll look into this on the weekend. I think the current PR might be somewhat outdated. |
|
for gradle 9 there is #156, but jdk 25 would be amazing, thanks :) |
|
This PR is obsolete, I am preparing a Java 25 compatible release. |
This PR fixes #153: