JDK 18: Rampdown Phase 1 & Early-Access builds 27
Francesco, Thank you for being part of the OpenJDK Quality Outreach Program. As year-end 2021 approaches, I'd like to share some updates on JDK 18, which is scheduled for General Availability on March 22, 2022. JDK 18 has now entered Rampdown Phase One (RDP1) [1], which means that the main-line has been forked into a dedicated JDK 18 stabilization repository. At this point, the overall JDK 18 feature set is now frozen and no additional JEPs will be targeted to JDK 18. Only low-risk enhancements that add small bits of missing functionality or improve usability might still be considered. The next few weeks should be leveraged to try to identify and resolve as many issues as possible (i.e. before JDK 18 enters the Release Candidates phase). And as you can see below, JDK 18 EA Builds 26 & 27 include fixes for issues that were reported by you! So thank you for your help contributing to the overall quality of OpenJDK! [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2021-December/006287.html ## JEP 400 - UTF-8 by Default All JEPs are now integrated, but we would like to draw your attention to JEP 400 especially if you are deploying on Windows as it might induce some incompatible behavior on that platform. JEP 400 [2] is changing the default charset to UTF-8. This aligns with the existing `newBufferedReader`/`Writer` methods of the `java.nio.file.Files` class where UTF-8 is the default when no explicit charset is set. By making UTF-8 the default charset, the JDK I/O APIs will now always work in the same, predictable manner, with no need to pay attention to the host and or user’s environment! Further, we encourage you to test your project(s) with the latest JDK 18 Early Access builds. We don't expect issues on macOS and Linux as their default encoding is already UTF-8. On Windows, especially for East Asian locales such as Chinese/Japanese/Korean, some incompatible behavior could be anticipated. If that’s the case, please consider a mitigation strategy [3]. [2] https://openjdk.java.net/jeps/400 [3] https://inside.java/2021/10/04/the-default-charset-jep400/ ## JDK 18 JDK 18 Early-Access builds 27 are now available [4], and are provided under the GNU General Public License v2, with the Classpath Exception. Make sure to check the Release Notes [5]. As usual, we encourage you to test your project(s) using those EA builds and provide us feedback. [4] https://jdk.java.net/18/ [5] https://jdk.java.net/18/release-notes ### JEPs integrated to JDK 18: - JEP 400: UTF-8 by Default - JEP 408: Simple Web Server - JEP 413: Code Snippets in Java API Documentation - JEP 416: Reimplement Core Reflection with Method Handles - JEP 417: Vector API (Third Incubator) - JEP 418: Internet-Address Resolution SPI - JEP 419: Foreign Function & Memory API (Second Incubator) - JEP 420: Pattern Matching for switch (Second Preview) - JEP 421: Deprecate Finalization for Removal ### Changes in recent builds that maybe of interest: Build 27: - JDK-8266435: WBMPImageReader.read() should not truncate the input stream [Reported by PDFBox] - JDK-8278078: Cannot reference super before supertype constructor has been called - JDK-8177819: DateTimeFormatterBuilder zone parsing should recognise DST - JDK-8277965: Enclosing instance optimization affects serialization - JDK-8275821: Optimize random number generators developed in JDK-8248862 using Math.unsignedMultiplyHigh() - JDK-8225181: KeyStore should have a getAttributes method - JDK-8275082: Update XML Security for Java to 2.3.0 - JDK-8278270: ServerSocket is not thread safe - JDK-8277863: Deprecate sun.misc.Unsafe methods that return offsets Build 26: - JDK-8277451: j.l.r.Field::set on static field with invalid argument type should throw IAE [Reported by Hibernate & ByteBuddy] - JDK-8258117: jar tool sets the time stamp of module-info.class entries to the current time [Reported by Apache Maven] - JDK-8268743: Require a better way for copying data between MemorySegments and on-heap arrays [Reported by Apache Lucene] - JDK-8277986: Typo in javadoc of java.util.zip.ZipEntry#setTime [Reported by Apache Ant] - JDK-8277861: Terminally deprecate Thread.stop - JDK-8276665: ObjectInputStream.GetField.get(name, object) should throw ClassNotFoundException - JDK-8271623: Omit enclosing instance fields from inner classes that don't use it - JDK-8231107: Allow store password to be null when saving a PKCS12 KeyStore - JDK-8193682: Infinite loop in ZipOutputStream.close() - JDK-8277459: Add `jwebserver` tool [see Topics of Interest] Build 25: - JDK-8259643: ZGC can return metaspace OOM prematurely - JDK-8277212: GC accidentally cleans valid megamorphic vtable inline caches - JDK-8276970: Default charset for PrintWriter that wraps PrintStream - JDK-8272773: Configurable card table card size - JDK-4337793: Mark non-serializable fields of java.security.cert.Certificate and CertPath Build 24: - JDK-8275056: Allow G1 heap regio
[jira] [Commented] (SYNCOPE-1654) Inconsistent Realm search FIQL expressions between JPA and Elasticsearch engines
[
https://issues.apache.org/jira/browse/SYNCOPE-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456890#comment-17456890
]
ASF subversion and git services commented on SYNCOPE-1654:
--
Commit 2fa7e28874acfeca8b6124ffec94d7f0a2d0d9ba in syncope's branch
refs/heads/master from Misagh Moayyed
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=2fa7e28 ]
Switch CAS to use 6.5.x / Spring Boot 2.6.x (#296)
* switch cas to use 6.5 rc2
* resume with boot 2.6 upgrade
* update spring cloud gateway
* upgrade to boot 2.6
* Upgrading Groovy
* Fix test cases; make sure exceptions are caught in SAML2 metadata generation
process
* assign a name to the syncope authn handler matching master-content and
auth-module
* Upgrading Tomcat
* Upgrading Spring Boot
* Upgrading Payara
* Upgrading Wildfly
* Getting Started Guide: reviewed for 3.0
* [SYNCOPE-1651] Reviewing delegation validation logic
* Upgrading gmavenplus-plugin
* Reference Guide reviewed and compelted for 3.0 up to Customization
* Typos in Reference Guide 3.0
* [SYNCOPE-1654] Allowing to search realm by key or full path
* Upgrading Swagger UI and Checkstyle
* Upgrading Bouncycastle
* Upgrading Wicket
* upgrade to spring boot 2.6; fixes build issues
* fix checkstyle
* restore spring cloud contract wiremock version
* update pac4j to match latest CAS 6.5 SNAPSHOT
Co-authored-by: Francesco Chicchiriccò
> Inconsistent Realm search FIQL expressions between JPA and Elasticsearch
> engines
>
>
> Key: SYNCOPE-1654
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1654
> Project: Syncope
> Issue Type: Bug
> Components: core, extensions
>Affects Versions: 2.1.10
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Labels: elasticsearch
> Fix For: 2.1.11, 3.0.0
>
>
> Searching by Realm when JPA search engine is configured requires expressions
> like
> {code}
> realm==c5b75db1-fce7-470f-b780-3b9934d82a9d
> {code}
> When Elasticsearch search engine is configured, the following is required
> instead:
> {code}
> realm==/even
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SYNCOPE-1651) Invalid users can be specified in X-Syncope-Delegated-By
[
https://issues.apache.org/jira/browse/SYNCOPE-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456889#comment-17456889
]
ASF subversion and git services commented on SYNCOPE-1651:
--
Commit 2fa7e28874acfeca8b6124ffec94d7f0a2d0d9ba in syncope's branch
refs/heads/master from Misagh Moayyed
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=2fa7e28 ]
Switch CAS to use 6.5.x / Spring Boot 2.6.x (#296)
* switch cas to use 6.5 rc2
* resume with boot 2.6 upgrade
* update spring cloud gateway
* upgrade to boot 2.6
* Upgrading Groovy
* Fix test cases; make sure exceptions are caught in SAML2 metadata generation
process
* assign a name to the syncope authn handler matching master-content and
auth-module
* Upgrading Tomcat
* Upgrading Spring Boot
* Upgrading Payara
* Upgrading Wildfly
* Getting Started Guide: reviewed for 3.0
* [SYNCOPE-1651] Reviewing delegation validation logic
* Upgrading gmavenplus-plugin
* Reference Guide reviewed and compelted for 3.0 up to Customization
* Typos in Reference Guide 3.0
* [SYNCOPE-1654] Allowing to search realm by key or full path
* Upgrading Swagger UI and Checkstyle
* Upgrading Bouncycastle
* Upgrading Wicket
* upgrade to spring boot 2.6; fixes build issues
* fix checkstyle
* restore spring cloud contract wiremock version
* update pac4j to match latest CAS 6.5 SNAPSHOT
Co-authored-by: Francesco Chicchiriccò
> Invalid users can be specified in X-Syncope-Delegated-By
>
>
> Key: SYNCOPE-1651
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1651
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.1.10
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.1.11, 3.0.0
>
>
> {{X-Syncope-Delegated-By}} header values like {code}user_not_found{code}
> (where {{user_not_found}} does not match any exiting user) do not throw any
> processing exceptions and result into values like {code}user_found delegated
> by user_not_found{code} (where {{user_found}} is the authenticating user) for
> Audit and metadata.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [syncope] mmoayyed merged pull request #296: Switch CAS to use 6.5.x / Spring Boot 2.6.x
mmoayyed merged pull request #296: URL: https://github.com/apache/syncope/pull/296 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [syncope] mmoayyed commented on pull request #296: Switch CAS to use 6.5.x / Spring Boot 2.6.x
mmoayyed commented on pull request #296: URL: https://github.com/apache/syncope/pull/296#issuecomment-989956498 Sure. I updated the PR. I think GH might be confused after the branch was merged with master. This branch was sync'd with master once, but it seems like GH does not recognize the changes as those that might already be merged with master. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [syncope] ilgrosso commented on a change in pull request #296: Switch CAS to use 6.5.x / Spring Boot 2.6.x
ilgrosso commented on a change in pull request #296: URL: https://github.com/apache/syncope/pull/296#discussion_r765530473 ## File path: client/idrepo/console/pom.xml ## @@ -124,7 +124,7 @@ under the License. org.apache.logging.log4j - log4j-slf4j18-impl + log4j-slf4j-impl Review comment: Thanks for explanation, LGTM! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [syncope] mmoayyed commented on a change in pull request #296: Switch CAS to use 6.5.x / Spring Boot 2.6.x
mmoayyed commented on a change in pull request #296: URL: https://github.com/apache/syncope/pull/296#discussion_r765529126 ## File path: client/idrepo/console/pom.xml ## @@ -124,7 +124,7 @@ under the License. org.apache.logging.log4j - log4j-slf4j18-impl + log4j-slf4j-impl Review comment: (Copying the answer here as well so it's available for the public) > This is to mainly to align with CAS, and to also align with the now-stable slf4j version, to avoid these: ``` java.lang.ClassCastException: class org.slf4j.helpers.NOPLoggerFactory cannot be cast to class org.apache.logging.slf4j.Log4jLoggerFactory (org.slf4j.helpers.NOPLoggerFactory and org.apache.logging.slf4j.Log4jLoggerFactory are in unnamed module of loader org.springframework.boot.loader.LaunchedURLClassLoader ``` Ref: https://github.com/apereo/cas/pull/5261 Ref: https://github.com/apereo/cas/pull/5264 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
