Skip to content

Use JabRef's JDK21 build#10004

Merged
koppor merged 13 commits into
mainfrom
use-jdk21
Jun 28, 2023
Merged

Use JabRef's JDK21 build#10004
koppor merged 13 commits into
mainfrom
use-jdk21

Conversation

@koppor

@koppor koppor commented Jun 11, 2023

Copy link
Copy Markdown
Member

Background:

Idea:

  • Use stable JDK whereever possible (tests, gradle execution, ...)
  • Use patched JDK21 when building end user binaries.

Binaries:

Ancient stories:

Before jpackage, we used install4j - see #5312 for details.

Mandatory checks

  • Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
  • Tests created for changes (if applicable)
  • Manually tested changed features in running JabRef (always required)
  • Screenshots added in PR description (for UI changes)
  • Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
  • Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

koppor and others added 3 commits June 12, 2023 00:20
Co-authored-by: Christoph <siedlerkiller@gmail.com>
@JabRef JabRef deleted a comment from github-actions Bot Jun 11, 2023
Comment thread build.gradle
modularity.inferModulePath.set(false)

toolchain {
languageVersion = JavaLanguageVersion.of(20)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That needs to be 21

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought,, 20 is the latest release version (21 is in ramp down, isn't it? - https://openjdk.org/projects/jdk/21/). That version is used generally (tests, ...). Exception; When using jlink, 21 is used. I thought, it is a good idea.to modify one workflow only instead of changing all (JDK custom build download etc)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I change this with sed in deployment.yml

@Siedlerchr

Siedlerchr commented Jun 12, 2023

Copy link
Copy Markdown
Member

Can't we just use the GitHub artifacts that are build and upload them to our server?

Think this pr is a bit too early

@Siedlerchr Siedlerchr closed this Jun 12, 2023
@koppor

koppor commented Jun 12, 2023

Copy link
Copy Markdown
Member Author

Can't we just use the GitHub artifacts that are build and upload them to our server?

Artifacts are cleared after 30days. Should we build the JDK each month?

Think this pr is a bit too early

I assume the patch will take two or three JDK releases until it is included. Don't want to wait such a long time.

I also see this PR as unblocker for a release using java-keyring to store passwords "properly".

@Siedlerchr

Siedlerchr commented Jun 12, 2023

Copy link
Copy Markdown
Member

I mean building the jdk once using CI (like they do), then uploading the artifact to our server
https://github.com/openjdk/jdk/blob/master/.github/workflows/build-linux.yml

Seems to be easier to copy the existing workflow

@koppor

koppor commented Jun 12, 2023

Copy link
Copy Markdown
Member Author

The build is even created automatically. main ("OpenJDK GHA Sanity Checks'") calls all build workflows.

Example: https://github.com/JabRef/jdk/actions/runs/5239968107/jobs/9460305999

grafik

Windows fails at GetJTreg (as ist also does at the main repository)

@koppor

koppor commented Jun 12, 2023

Copy link
Copy Markdown
Member Author

grafik

@koppor

koppor commented Jun 12, 2023

Copy link
Copy Markdown
Member Author

The artifacts will be available after the complete run. See actions/upload-artifact#181 for more information.

@Siedlerchr

Copy link
Copy Markdown
Member

Yes, we just need to get this jtreg download fixed

@koppor

koppor commented Jun 12, 2023

Copy link
Copy Markdown
Member Author

Yes, we just need to get this jtreg download fixed

They also happen at the main repository (https://github.com/JabRef/jdk/actions/runs/5239968107/jobs/9460306443). Thus, I hope, someone of the OpenJDK team picks up.

@koppor koppor reopened this Jun 12, 2023
@koppor

koppor commented Jun 12, 2023

Copy link
Copy Markdown
Member Author

at 14c2fef (#10004), I updated to the build generated at JabRef/jdk21#1.

@koppor

koppor commented Jun 12, 2023

Copy link
Copy Markdown
Member Author

Build available at https://builds.jabref.org/pull/10004/merge/

The about dialog is of strange size here (Windows). Does anyone else also experience issues here?

image

@koppor koppor marked this pull request as ready for review June 28, 2023 19:56
@koppor

koppor commented Jun 28, 2023

Copy link
Copy Markdown
Member Author

We need to move forward because of JabRef release blocking issues. In case something breaks, we will need to investigate then.

@koppor koppor merged commit 456cd0e into main Jun 28, 2023
@koppor koppor deleted the use-jdk21 branch June 28, 2023 19:57
@Siedlerchr

Siedlerchr commented Jun 29, 2023 via email

Copy link
Copy Markdown
Member

@koppor

koppor commented Jun 29, 2023

Copy link
Copy Markdown
Member Author

We will also probably add notarizations and singing for the mac jdk version as well

I put #10041 to the v5.10 milestone.

@Siedlerchr

Copy link
Copy Markdown
Member

jdk 21 mac path is probably:
/Users/christophs/Downloads/jdk-21.jdk/Contents/Home/bin

signing overall of the jdk https://github.com/openjdk/jdk/blob/master/doc/building.md#macos-1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants