-
Notifications
You must be signed in to change notification settings - Fork 0
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
Migrate onto Java21 #1230
Comments
PRs (but update them with the latest cbioportal before merging them): |
CMO pipelines (though some of these applied to pipelines and/or genome-nexus-annotation-pipeline): Upgrade to Spring 5.3.31 Upgrade to Spring boot 2.7.18: Switch to mysql.com mysql-connector-j Only needed for cmo-pipelines. Pipelines didn't need this update but we did it anyway: Update to 3.5.1 for the maven shade plugin: This says to update to latest version of plugin: https://stackoverflow.com/questions/55748745/unable-to-parse-configuration-of-mojo-org-apache-maven-pluginsmaven-shade-plugi |
genome-nexus-annotation-pipeline: Updating byte-buddy + mockito because of this: I had trouble using a updated genome-nexus-java-api-client because I had to use a fork of the library we use to compile to code in order to compile with Java 21, and then it was throwing exceptions in the genome-nexus-annotation-pipeline because fields defined as non-optional/required in the GN swagger were not being returned to us on API calls. |
We were getting this error compiling: We manually downloaded the jar and pom from here: https://repo.spring.io/ui/native/plugins-release/org/springframework/social/spring-social-security/1.1.0.M4/ mvn install:install-file -Dfile=spring-social-security-1.1.0.M4.jar -DpomFile=spring-social-security-1.1.0.M4.pom We have done this for spring-social-security, spring-social-core, and spring-social-web. mvn install:install-file -Dfile=spring-social-core-1.1.0.M4.jar -DpomFile=spring-social-core-1.1.0.M4.pom We manually unpacked the jar in /home/wilson/.m2/repository/batik/batik/1.5/ and corrected the MANIFEST.MF file. We also had to for batik-rasterizer-1.5.jar. DON'T DO A mvn -U clean install jar xf batik-rasterizer-1.5.jar jar cf batik-rasterizer-1.5.jar . If there are other jar files then use 0 as an option.
|
we moved the "deploy jars into production and update pipelines3 to a java21 jvm" type of tasks to the card for integrating pipelines with the new "cbioportal-core" repository. |
As things stand, both the cmo-pipelines repository and the pipelines repository have been compiled and tested (at least unit tests) under a java21 jvm. Bringing both codebases into accord with the latest version of the cbioportal codebase now requires integration with the externalized core module which is available now here: https://github.com/cBioPortal/cbioportal-core In the current build, we are using these somewhat out of date timepoints: cmo-pipelinesThis PR knowledgesystems/cmo-pipelines#1100 builds off of the head of the master branch of cmo-pipelines. It links in dependency genome-nexus-annotation-pipeline at commit hash 0f4e72e5902e309f082083068b17bffaf2a86565 which was merged on (2023_10_11 via pr genome-nexus/genome-nexus-annotation-pipeline#267). That in turn has dependency on cbioportal at commit hash ee5802d836c05ed846d7d1ea3f584febdc07ffa8 which was merged on (2023_10_10). pipelinesThis PR https://github.com/knowledgesystems/pipelines/pull/460 builds off of the head of the master branch of pipelines. It links in dependency genome-nexus-annotation-pipeline at commit hash efd80bbbee60826dabfab1a8a26b1e2969a90508 which is part of a pending PR to genome-nexus-annotation-pipeline genome-nexus/genome-nexus-annotation-pipeline#272 which is built off the head of master. That in turn has dependency on cbioportal at commit hash ee5802d836c05ed846d7d1ea3f584febdc07ffa8 which was merged on (2023_10_10). A second direct dependency is present in pipelines on that same point in the history of cbioportal (ee5802d836c05ed846d7d1ea3f584febdc07ffa8) |
The genome-nexus-annotation-pipeline also compiles and runs tests under the Java 21 jvm. |
Done Condition (What do we need? Why do we need it? Keep this is small as possible!)
Technical Description (How are we going to achieve the above)
Potential Issues
Dependencies
Technical Requirements
Outside People/Teams
Changes
The text was updated successfully, but these errors were encountered: