Code changes required after JDK-8291473
Filip Krakowski
filip.krakowski at hhu.de
Fri Aug 5 10:23:38 UTC 2022
Hi,
is it a question of maintainability (diverging branches in case of
patches, etc.), which would stand in the way of this, or a question of
the infrastructure that would be required? In the latter case, I could
try to set something up to accomplish the job of automatically creating
releases from each pushed tag matching a version number.
Since the project is hosted on GitHub, I could implement a GitHub
Action, which would be triggered on each pushed tag. This Action would
then compile the code for different platforms (Linux, macOS, Windows -
GitHub provides images for each), create a release inside the repository
and attach the created binaries to it. The repository already contains a
GitHub Action for building and testing jextract, which I could use as a
starting point.
Best regards,
Filip
On 04.08.22 21:14, Maurizio Cimadamore wrote:
>
> On 04/08/2022 20:08, Filip Krakowski wrote:
>> Each branch would therefore only produce binaries when it receives a
>> new tag. Could this work?
>
> I'd have to check - my feeling is that, no that would not be possible.
>
> Another issue is that we'd need to keep updating the main github
> branch every few months (not a big issue).
>
> Maurizio
>
>
More information about the jextract-dev
mailing list