You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(38) |
Nov
(98) |
Dec
(58) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(114) |
Feb
(123) |
Mar
(96) |
Apr
(66) |
May
(84) |
Jun
(72) |
Jul
(128) |
Aug
(126) |
Sep
(82) |
Oct
(80) |
Nov
(148) |
Dec
(55) |
2002 |
Jan
(137) |
Feb
(85) |
Mar
(118) |
Apr
(67) |
May
(71) |
Jun
(28) |
Jul
(69) |
Aug
(48) |
Sep
(83) |
Oct
(79) |
Nov
(54) |
Dec
(32) |
2003 |
Jan
(44) |
Feb
(47) |
Mar
(59) |
Apr
(57) |
May
(43) |
Jun
(45) |
Jul
(44) |
Aug
(39) |
Sep
(27) |
Oct
(62) |
Nov
(17) |
Dec
(23) |
2004 |
Jan
(41) |
Feb
(51) |
Mar
(38) |
Apr
(30) |
May
(25) |
Jun
(12) |
Jul
(11) |
Aug
(27) |
Sep
(16) |
Oct
(56) |
Nov
(23) |
Dec
(29) |
2005 |
Jan
(75) |
Feb
(82) |
Mar
(50) |
Apr
(77) |
May
(19) |
Jun
(104) |
Jul
(47) |
Aug
(42) |
Sep
(28) |
Oct
(143) |
Nov
(62) |
Dec
(13) |
2006 |
Jan
(20) |
Feb
(10) |
Mar
(59) |
Apr
(45) |
May
(25) |
Jun
(129) |
Jul
(162) |
Aug
(91) |
Sep
(15) |
Oct
(39) |
Nov
(186) |
Dec
(191) |
2007 |
Jan
(134) |
Feb
(140) |
Mar
(106) |
Apr
(77) |
May
(92) |
Jun
(63) |
Jul
(233) |
Aug
(102) |
Sep
(119) |
Oct
(63) |
Nov
(68) |
Dec
(32) |
2008 |
Jan
(69) |
Feb
(91) |
Mar
(129) |
Apr
(44) |
May
(18) |
Jun
(53) |
Jul
(50) |
Aug
(25) |
Sep
(11) |
Oct
(28) |
Nov
(67) |
Dec
(36) |
2009 |
Jan
(20) |
Feb
(24) |
Mar
(66) |
Apr
(53) |
May
(48) |
Jun
(48) |
Jul
(59) |
Aug
(82) |
Sep
(49) |
Oct
(30) |
Nov
(16) |
Dec
(16) |
2010 |
Jan
(52) |
Feb
(25) |
Mar
(36) |
Apr
(34) |
May
(14) |
Jun
(15) |
Jul
(14) |
Aug
(16) |
Sep
(23) |
Oct
(6) |
Nov
(4) |
Dec
(5) |
2011 |
Jan
(4) |
Feb
(22) |
Mar
(45) |
Apr
(9) |
May
(8) |
Jun
(13) |
Jul
(12) |
Aug
(4) |
Sep
(6) |
Oct
(10) |
Nov
(21) |
Dec
(5) |
2012 |
Jan
(6) |
Feb
(9) |
Mar
(25) |
Apr
(6) |
May
(4) |
Jun
(23) |
Jul
(6) |
Aug
(18) |
Sep
(21) |
Oct
(34) |
Nov
(19) |
Dec
(25) |
2013 |
Jan
(8) |
Feb
(34) |
Mar
(35) |
Apr
(4) |
May
(11) |
Jun
(4) |
Jul
(7) |
Aug
(5) |
Sep
(20) |
Oct
(12) |
Nov
(11) |
Dec
(7) |
2014 |
Jan
(10) |
Feb
(18) |
Mar
(50) |
Apr
(26) |
May
(53) |
Jun
(21) |
Jul
(12) |
Aug
(39) |
Sep
(43) |
Oct
(26) |
Nov
(8) |
Dec
(6) |
2015 |
Jan
(18) |
Feb
(32) |
Mar
(31) |
Apr
(42) |
May
(38) |
Jun
(13) |
Jul
(6) |
Aug
(11) |
Sep
(29) |
Oct
(25) |
Nov
(10) |
Dec
(11) |
2016 |
Jan
(24) |
Feb
(12) |
Mar
(13) |
Apr
(15) |
May
(22) |
Jun
(8) |
Jul
(12) |
Aug
(25) |
Sep
(8) |
Oct
(6) |
Nov
(13) |
Dec
(7) |
2017 |
Jan
(6) |
Feb
(29) |
Mar
(32) |
Apr
(8) |
May
(82) |
Jun
(42) |
Jul
(20) |
Aug
(17) |
Sep
(27) |
Oct
(14) |
Nov
(22) |
Dec
(6) |
2018 |
Jan
(12) |
Feb
(9) |
Mar
(22) |
Apr
(19) |
May
(14) |
Jun
(9) |
Jul
(9) |
Aug
(22) |
Sep
(22) |
Oct
(12) |
Nov
(13) |
Dec
(8) |
2019 |
Jan
(22) |
Feb
(3) |
Mar
(30) |
Apr
(20) |
May
(20) |
Jun
(6) |
Jul
(15) |
Aug
(25) |
Sep
(11) |
Oct
(24) |
Nov
(11) |
Dec
(6) |
2020 |
Jan
(9) |
Feb
(12) |
Mar
(29) |
Apr
(10) |
May
(22) |
Jun
(11) |
Jul
(15) |
Aug
(5) |
Sep
(6) |
Oct
(7) |
Nov
(7) |
Dec
(13) |
2021 |
Jan
(21) |
Feb
(5) |
Mar
(5) |
Apr
(6) |
May
(10) |
Jun
(7) |
Jul
(6) |
Aug
(8) |
Sep
(5) |
Oct
(9) |
Nov
(5) |
Dec
(6) |
2022 |
Jan
(5) |
Feb
(4) |
Mar
(8) |
Apr
(6) |
May
(5) |
Jun
(5) |
Jul
(10) |
Aug
(6) |
Sep
(7) |
Oct
(4) |
Nov
(4) |
Dec
(6) |
2023 |
Jan
(5) |
Feb
(5) |
Mar
(6) |
Apr
(4) |
May
(5) |
Jun
(6) |
Jul
(5) |
Aug
(5) |
Sep
(5) |
Oct
(5) |
Nov
(7) |
Dec
(8) |
2024 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
(2) |
May
|
Jun
(1) |
Jul
(1) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
From: David D. <dav...@or...> - 2024-08-23 12:44:39
|
Welcome to the latest OpenJDK Quality Outreach update! Everything is on track for the General Availability of Java 23 on September 17th [1] as the JDK 23 Release Candidate builds (RC2 - builds 37) are now available [2]. And before shifting your attention to JDK 24, make sure to check the Heads-Up below as it is related to an important JAXP update in JDK 23. The JVM Language Summit took place earlier this month in Santa Clara (California). During this unique conference, key updates around the Java platforms were presented and discussed. So, make sure to watch the JVMLS 2024 playlist [3] as videos are added regularly. And it's not really a surprise but Valhalla was a highly discussed topic. In his session [4], Brian Goetz (Java Language Architect) explained the proposed solution: value classes, null-restricted types, improved definite assignment analysis, and strict initialization. Around the same time-frame, Valhalla Early-Access builds implementing Value Classes and Objects were also made available [5], see the Release Notes [6] for the details. As usual, feedback should be reported to the proper mailing list [7]. [1] https://openjdk.org/projects/jdk/23/ [2] https://jdk.java.net/23/ [3] https://www.youtube.com/playlist?list=PLX8CzqL3ArzUEYnTa6KYORRbP3nhsK0L1 [4] https://www.youtube.com/watch?v=IF9l8fYfSnI [5] https://jdk.java.net/valhalla/ [6] https://openjdk.org/projects/valhalla/early-access [7] https://mail.openjdk.org/mailman/listinfo/valhalla-dev ## Heads-up - JDK 23: Prepare for a More Restrictive JAXP Configuration The Java platform supports XML processing with JAXP (Java APIs for XML Processing) that are based on a wide range of XML technologies and standards, which can make them challenging to secure. To mitigate risks, JAXP offers comprehensive security features [8], but the default settings of some security features are not strict, making them opt-in. To improve out-of-the-box security, future JDK releases will make XML processing more restrictive by default and JDKs 21 to 23 help developers prepare for these changes. ### JDK 21: JAXP Configuration File JDK 21 added `$JAVA_HOME/conf/jaxp.properties` as the default JAXP configuration file, property settings in this file reflect the current, built-in defaults for the JDK. JDK 21 also added the system property `java.xml.config.file` for specifying the location of a custom configuration file. For details, refer to JDK-8303530 [9] or the `java.xml` documentation [10]. ### JDK 23: Restrictive JAXP Configuration File Template JDK 23 adds `$JAVA_HOME/conf/jaxp-strict.properties.template`, a JAXP configuration file template that specifies more restrictive XML processing settings. It is recommended to test applications on these more restrictive settings to prepare them for a future JDK release that has them as default. The following steps should be used to test an application with that template: * copy the template file to a location outside of `$JAVA_HOME/conf`, e.g. `/<my_path>/jaxp-strict.properties` * run the application with the system property `java.xml.config.file` set to the file's path, e.g. `java -Djava.xml.config.file=/<my_path>/jaxp-strict.properties myApp` For details, please refer to JDK-8330542 [11]. [8] https://docs.oracle.com/en/java/javase/22/security/java-api-xml-processing-jaxp-security-guide.html#GUID-6E76FE41-A8C5-4F56-AB46-83A89B1E904A [9] https://bugs.openjdk.org/browse/JDK-8303530 [10] https://docs.oracle.com/en/java/javase/21/docs/api/java.xml/module-summary.html#Conf [11] https://bugs.openjdk.org/browse/JDK-8330542 ## JDK 24 Early-Access Builds The JDK 24 early-access builds 12 are available [12], and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes are available here [13]. ### Changes in recent JDK 24 builds that may be of interest: - JDK-8335638: Calling VarHandle.{access-mode} methods reflectively throws wrong exception - JDK-8329471: Remove GTK2 - JDK-8333772: Incorrect Kerberos behavior when udp_preference_limit = 0 - JDK-8304929: MethodTypeDesc throws an unchecked exception than ReflectiveOperationException … - JDK-4966250: SSLSessionContext.setSessionTimeout() documentation could be updated - JDK-8337506: Disable "best-fit" mapping on Windows command line - JDK-8336479: Provide Process.waitFor(Duration) - JDK-8336999: Verification for resource area allocated data structures in C2 - JDK-8335480: Only deoptimize threads if needed when closing shared arena - JDK-8335939: Hide element writing across the ClassFile API - JDK-8336489: Track scoped accesses in JVMCI compiled code - JDK-8334492: DiagnosticCommands (jcmd) should accept %p in output filenames and substitute PID - JDK-8334495: Use FFM instead of jdk.internal.misc.Unsafe in java.desktop font implementation - JDK-8333396: Use StringBuilder internally for java.text.Format.* formatting - JDK-8336815: Several methods in java.net.Socket and ServerSocket do not s… Note: A more exhaustive list of changes can be found here [14]. [12] https://jdk.java.net/24/ [13] https://jdk.java.net/24/release-notes [14] https://github.com/openjdk/jdk/compare/jdk-24+7...jdk-24+12 # Project Loom New Early-Access Builds The latest Loom early access builds (Builds 24-loom+3-33 -2024/7/27) are now available [15]. These builds, based on an incomplete version of JDK 24, improve the implementation of Java monitors (synchronized methods) to work better with virtual threads. These builds are intended for developers looking to "kick the tires" and provide feedback or bug reports. Feedback should be reported to the Loom mailing list [16] (subscription required). [15] https://jdk.java.net/loom/ [16] http://mail.openjdk.org/mailman/listinfo/loom-dev # JavaFX Early-Access Builds These are early access builds of the JavaFX 23 and 24 Runtime built from openjdk/jfx [17]. These builds enable JavaFX application developers to build and test their applications with JavaFX 23 and 24 on JDK 23 and 24 respectively. And although these builds are designed to work with JDK 23 EA, they are also known to work with JDK 21 and later versions. The latest early access builds of JavaFX 23 (Builds 27) are available [18], under the GNU General Public License, version 2, with the Classpath Exception. And similarly, the latest early access builds of JavaFX 24 (Builds 4) are available here [19]. [17] https://github.com/openjdk/jfx [18] https://jdk.java.net/javafx23/ [19] https://jdk.java.net/javafx24/ ## Topics of Interest - JDK 23 G1/Parallel/Serial GC changes https://tschatzl.github.io/2024/07/22/jdk23-g1-serial-parallel-gc-changes.html - How to Read a JDK Enhancement Proposal https://inside.java/2024/08/01/newscast-74/ - JFR Event to Detect Invocations of Deprecated Methods https://egahlin.github.io/2024/05/31/deprecated-event.html - JVMLS: Valhalla - Where Are We? https://www.youtube.com/watch?v=IF9l8fYfSnI - JVMLS: An Opinionated Overview on Static Analysis for Java https://inside.java/2024/08/20/jvmls-static-analysis/ - JVMLS: Rethinking Java String Concatenation https://inside.java/2024/08/19/jvmls-string-concatention/ - JVMLS: Project Babylon - Code Reflection https://inside.java/2024/08/14/jvmls-code-reflection/ - JVMLS: A Code Reflection Example - Translating Java to SPIR-V https://inside.java/2024/08/16/jvmls-spir-v/ - JVMLS: Java in 2024 Keynote https://inside.java/2024/08/12/jvmls-keynote/ ~ As always, please ping me if you encounter issues with an early-access build. And see you next month for the Java 23 launch! --David |
From: Jeff A. <ja...@fa...> - 2024-08-21 07:55:42
|
The project is happy to announce the general availability of Jython 2.7.4 at https://www.jython.org/download . v2.7.4 is a contains minor bug-fixes (thanks to all who contributed to triage and PRs) and security fixes by way of updated dependency JARs. Fuller details are at the link above, by following links on the page, and on our GitHub project. -- Jeff Allen |
From: Jeff A. <ja...@fa...> - 2024-08-03 08:08:04
|
Great to hear from you and what a kind offer. I agree with much of what you write about the value of a JVM implementation. If you've poked around the project you may have noticed some efforts towards a Jython 3, while keeping a 2.7 alive. These aim to use the dynamic language features to full advantage. It's quite slow progress. Early invokedynamic resources, including some of your own, have been important for understanding how we might do this (thanks). It is clear that your role as an early adopter has helped shape the feature. I'll reply with more specifics off-list. Jeff Allen On 01/08/2024 14:56, Charles Oliver Nutter wrote: > Hello fellow JVM language developers! > > I am a co-lead of JRuby for many years, and have had some passing > connection with previous Jython maintainers: Tobias Ivarsson, Frank > Wierzbicki, and others. I am jumping on this list to ask how I might > help Jython in my capacity as a JVM language hacker. I am also > attempting to secure funding to keep JRuby development going, and I > would like to see if it's possible to do the same for Jython. > > Despite the enormous resources that have been poured into alternative > Ruby and Python implementations over the past decade, I still believe > that "pure" JVM implementations are valuable to both the communities > that use these languages and to the JVM language community in general. > JRuby, over the past twenty years, has remained the only alternative > Ruby implementation to ever see significant production deployment. > This is in large part because we adhere to some level of JVM purity: > we run on any JVM, on any platform, without commercial entanglements. > We also try to turn the challenges of implementing a JVM dynamic > language into opportunities for OpenJDK to improve; InvokeDynamic, > Panama, and Loom have in large part been answers to those challenges. > Jython has also proven itself, and even though it has fallen behind > standard Python and does not fully utilize modern JVM features, it > remains one of the great success stories of JVM dynamic languages. > > I believe Jython remains an important project. I'd like to do what I > can to help it move forward and become a viable target for modern > Python applications. Can we have a discussion about some shared future > for our two projects? > > *Charles Oliver Nutter* > /Architect and Technologist/ > Headius Enterprises > https://www.headius.com > he...@he... -- Jeff Allen |
From: Charles O. N. <he...@he...> - 2024-08-01 14:53:06
|
Hello fellow JVM language developers! I am a co-lead of JRuby for many years, and have had some passing connection with previous Jython maintainers: Tobias Ivarsson, Frank Wierzbicki, and others. I am jumping on this list to ask how I might help Jython in my capacity as a JVM language hacker. I am also attempting to secure funding to keep JRuby development going, and I would like to see if it's possible to do the same for Jython. Despite the enormous resources that have been poured into alternative Ruby and Python implementations over the past decade, I still believe that "pure" JVM implementations are valuable to both the communities that use these languages and to the JVM language community in general. JRuby, over the past twenty years, has remained the only alternative Ruby implementation to ever see significant production deployment. This is in large part because we adhere to some level of JVM purity: we run on any JVM, on any platform, without commercial entanglements. We also try to turn the challenges of implementing a JVM dynamic language into opportunities for OpenJDK to improve; InvokeDynamic, Panama, and Loom have in large part been answers to those challenges. Jython has also proven itself, and even though it has fallen behind standard Python and does not fully utilize modern JVM features, it remains one of the great success stories of JVM dynamic languages. I believe Jython remains an important project. I'd like to do what I can to help it move forward and become a viable target for modern Python applications. Can we have a discussion about some shared future for our two projects? *Charles Oliver Nutter* *Architect and Technologist* Headius Enterprises https://www.headius.com he...@he... |
From: David D. <dav...@or...> - 2024-07-22 05:48:46
|
Welcome to the OpenJDK Quality Outreach summer update. JDK 23 is now in Rampdown Phase Two [1], its overall feature has been frozen a few weeks ago. Per the JDK Release Process, we have now turned our focus to P1 and P2 bugs, which can be fixed with approval [2]. Late enhancements are still possible, with approval, but the bar is now extraordinarily high. That also means that the JDK 23 Initial Release Candidates are fast approaching, i.e., August 8th [3]! So, and in addition to testing your projects with the latest JDK 23 early-access builds, it is now a good time to start testing with the JDK 24 early-access builds. Make sure to also check the heads-up below as some are related to JDK 23 and might have some impact, i.e., the first one being related to the eventual removal of the Security Manager and the second one discusses the removal of the legacy COMPAT locale provider. [1] https://mail.openjdk.org/pipermail/jdk-dev/2024-July/009252.html [2] https://openjdk.org/jeps/3#rdp-2 [3] https://openjdk.org/projects/jdk/23/ ## Heads-up - JDK 23: Subject.getSubject API Requires Allowing the Security Manager In JDK 17 and as announced in JEP 411 [4], the Security Manager was deprecated for removal. As part of that change, several Security Manager APIs, such as `AccessControlContext`, were deprecated for removal. The `Subject::doAs` and `Subject::getSubject` APIs depend on Security Manager related APIs even though they do not require Security Manager to be installed to use them. As of JDK 23 [5], to help applications prepare for the eventual removal of the Security Manager, subject authorization and the Subject APIs' behavior depend on allowing the Security Manager: - If the system property `java.security.manager` is set on the command line to the empty string, a class name, or the value `allow` then there is no behavior change compared to previous releases. - If the system property `java.security.manager` is not set on the command line or has been set on the command line to the value `disallow`, invoking the `Subject.getSubject` method will throw `UnsupportedOperationException`. Yet, running an application with `-Djava.security.manager=allow` is a temporary workaround to keep older code working. Maintainers of code using `Subject.doAs` and `Subject.getSubject` are strongly encouraged to migrate it with utmost priority to the replacement APIs, `Subject.callAs` and `Subject.current`. Make sure to check [5] and [6] for additional details. The jdeprscan tool [7] scans a JAR file for usage of deprecated API elements and is helpful to find code using these methods. Additionally, consider migrating as soon as possible code that stores a `Subject` in an `AccessControlContext` and invokes `AccessController.doPrivileged` with that context. Such code will stop working when the Security Manager is removed. [4] https://openjdk.org/jeps/411 [5] https://jdk.java.net/23/release-notes#b15 [6] https://inside.java/2024/07/08/quality-heads-up/ [7] https://dev.java/learn/jvm/tools/core/jdeprscan/ ## Heads-up - JDK 23: Unicode / Removal of COMPAT Locale Provider ### A Quick History of Locale Data in the JDK Before the Unicode Consortium created the Common Locale Data Repository (CLDR) in 2003 to manage locale data, the JDK had to provide its own collection. It did so successfully and in JDK 8 supported about 160 locales. To reduce maintenance effort, allow better interoperability between platforms, and improve locale data quality, the JDK started to move towards CLDR in 2014: - JDK 8 comes with two locale data providers, which can be selected with the system property java.locale.providers: . JRE/COMPAT for the JDK’s legacy data collection (default) . CLDR for the CLDR data . a custom locale provider can be implemented - JDK 9 picks CLDR by default - JDK 21 issues a warning on JRE/COMPAT There are plenty of minor and a few notable differences between the legacy data and CLDR - the recently rewritten JEP 252 [8] lists a few of them. ### Locale Data in JDK 23 JDK 23 [9] removes legacy locale data. As a consequence, setting java.locale.providers to JRE or COMPAT has no effect. Projects that are still using legacy locale data are highly encouraged to switch to CLDR as soon as possible. Where that is infeasible, two alternatives remain: - Create custom formatters with patterns that mimic the legacy behavior and use them everywhere where locale-sensitive data is written or parsed. - Implement a custom locale data provider [10]. For more details on that as well as on CLDR in the JDK in general, please check JEP 252 [8] that has been recently rewritten to provide better information and guidance. [8] https://openjdk.org/jeps/252 [9] https://bugs.openjdk.org/browse/JDK-8325568 [10] https://docs.oracle.com/en/java/javase/22/docs/api/java.base/java/util/spi/LocaleServiceProvider.html ## Heads-up - JDK 23: Initial Leyden Early-Access Builds Project Leyden published its first early-access builds (24-leyden+2-8 2024/6/20) [11]. The initial release is focused on improving Java applications start-up time, but other Leyden optimizations will be explored in future releases. Below are some of the highlights of these Leyden EA builds: - Ahead-of-time compilation of Java methods to natively execute them as soon as the application starts up in the production run; - Ahead-of-time resolution of constant pool entries allows the AOT compiler to generate better code and for your application to start faster; - Ahead-of-time generation of Dynamic Proxies and reflection data as frameworks use those extensively during start-up time; - A unified Cache Data Store (CDS) archive to simplify the creation of the CDS archive, while supporting multiple types of optimization artifacts; - Loaded Classes in the CDS archive as soon the application starts up; - Class loader lookup cache to help application frameworks perform repeated lookups without repeatedly scanning the classpath; - Archived Method Profiles to reach Java application peak performance faster. The easiest way to start with Leyden features is by using the java program in the Leyden Early Access Release with the -XX:CacheDataStore flag. More details of this Leyden EA Build can be found in the release notes [12]. [11] https://jdk.java.net/leyden/ [12] https://github.com/openjdk/leyden/blob/leyden-ea1-release-notes/README.md ## JDK 23 Early-Access Builds The JDK 23 early-access builds 32 are available [13], and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes are available here [14] and the Javadoc here [15]. [13] https://jdk.java.net/23/ [14] https://jdk.java.net/23/release-notes [15] https://download.java.net/java/early_access/jdk23/docs/api/ ## JDK 24 Early-Access Builds The JDK 24 early-access builds 7 are available [16], and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes are available here [17]. ### Changes in recent JDK 24 builds that may be of interest: - JDK-8334299: Deprecate LockingMode option, along with LM_LEGACY and LM_MONITOR - JDK-8330846: Add stacks of mounted virtual threads to the HotSpot thread … - JDK-8333649: Allow different NativeCall encodings - JDK-8333755: NumberFormat integer only parsing breaks when format has suffix - JDK-8330842: Support AES CBC with Ciphertext Stealing (CTS) in SunPKCS11 - JDK-8327793: Deprecate jstatd for removal - JDK-8248981: Specify list of standard message digest and mgf algorithms for RSASSA-PSS signature - JDK-8334580: Deprecate no-arg constructor BasicSliderUI() for removal - JDK-8320448: Accelerate IndexOf using AVX2 - JDK-8333749: Consolidate ConstantDesc conversion in java.base - JDK-8329141: Obsolete RTM flags and code - JDK-8330198: Add some class loading related perf counters to measure VM startup - JDK-8330699: Obsolete -XX:+UseEmptySlotsInSupers - JDK-8334734: Remove specialized readXxxEntry methods from ClassReader This is only a curated list, a complete list of changes can be found here [18]. [16] https://jdk.java.net/24/ [17] https://jdk.java.net/24/release-notes [18] https://github.com/openjdk/jdk/compare/jdk-24+0...jdk-24+7 ## Topics of Interest - Integrity by Default - Inside Java Newscast https://inside.java/2024/07/18/newscast-73/ - Java and AI? - Inside Java Newscast https://inside.java/2024/07/04/newscast-72/ - What Happened to String Templates? - Inside Java Newscast https://inside.java/2024/06/20/newscast-71/ - Java Language Futures - Spring 2024 Edition https://inside.java/2024/07/01/java-language-futures/ - Project Loom - Structured Concurrency https://inside.java/2024/07/13/structured-concurrency/ - How to Build Custom Java Runtimes with Jlink https://inside.java/2024/06/21/build-runtimes-with-jlink/ ## July 2024 Critical Patch Update Released As part of the July 2024 CPU, Oracle released OpenJDK 22.0.2, JavaFX 22.0.2, JDK 22.0.2, JDK 21.0.4 LTS, JDK 17.0.12 LTS, JDK 11.0.24 LTS, JDK 8u421 as as well as JDK 8u421-perf. ~ We still have a few days before JDK 23 enters into the Release Candidate phase so please make sure to test your projects on the latest early-access builds and report any issue… but that shouldn't be a reason to not enjoy the summer and recharge your batteries! 😎 --David |
From: David D. <dav...@or...> - 2024-06-10 07:51:46
|
Welcome to the latest OpenJDK Quality Outreach update! JDK 23, scheduled for General Availability on September 17, 2024, is now in Rampdown Phase One (RDP1) [1]. At this point, the overall JDK 23 feature set is frozen (see the final list of JEPs integrated into JDK 23 below) and only low-risk enhancements might still be considered. The coming weeks should be leveraged to identify and resolve as many issues as possible, i.e. before JDK 23 enters the Release Candidates phase in early August [2]. We count on you to test your projects and help us make JDK 23 another solid release! This time, we are covering several heads-up related to JDK 23 : Deprecate the Memory-Access Methods in sun.misc.Unsafe for Removal and default annotation processing policy change. Also, make sure to check the new Loom early-access builds which have an improved Java monitors implementation to work better with virtual threads. [1] https://mail.openjdk.org/pipermail/jdk-dev/2024-June/009053.html [2] https://openjdk.org/projects/jdk/23/ ## Heads-Up - JDK 23: Deprecate the Memory-Access Methods in sun.misc.Unsafe for Removal As mentioned in a previous communication [3], there’s a plan to ultimately remove the sun.misc.Unsafe memory-access methods as the platform offers safer alternatives. JEP 471 (Deprecate the Memory-Access Methods in sun.misc.Unsafe for Removal) [4] outlines in more detail this plan including the initial step which is happening in JDK 23, i.e., all of the sun.misc unsafe memory-access methods are now marked as deprecated for removal. This will cause, in JDK 23, compile-time deprecation warnings for code that refers to these methods, alerting library developers to their forthcoming removal. A new command-line option also enables application developers and users to receive runtime warnings when those methods are used. Developers relying on those sun.misc.Unsafe APIs for access memory are strongly encouraged to start, if they haven't done so yet, the migration from the sun.misc.Unsafe APIs to supported replacements. For more details, make sure to read JEP 471 (Deprecate the Memory-Access Methods in sun.misc.Unsafe for Removal). [3] https://mail.openjdk.org/pipermail/quality-discuss/2024-January/001132.html [4] https://openjdk.org/jeps/471 ## Heads-Up - JDK 23: Changes Default Annotation Processing Policy Annotation processing is a compile-time feature, where javac scans the to-be-compiled source files for annotations and then the class path for matching annotation processors, so they can generate source code. Up to JDK 22, this feature is enabled by default, which may have been reasonable when it was introduced in JDK 6 circa 2006, but from a current perspective, in the interest of making build output more robust against annotation processors being placed on the class path unintentionally, this is much less reasonable. Hence, starting with JDK 23, javac requires an additional command-line option to enable annotation processing. ### New `-proc` Value To that end, the pre-existing option `-proc:$policy` was extended, where `$policy` can now have the following values: - `none`: compilation _without_ annotation processing, this policy exists since JDK 6 - `only`: annotation processing _without_ compilation, this policy exists since JDK 6 - `full`: annotation processing followed by compilation, this policy is the default in JDK ≤22 but the value itself is new (see next section for versions that support it) Up to and including JDK 22, code bases that require annotation processing before compilation could rely on javac's default behavior to process annotations but that is no longer the case. Starting with JDK 23, at least one annotation-processing command line option needs to be present. If neither `-processor`, `--processor-path`, now `--processor-module-path` is used, `-proc:only` or `-proc:full` has to be provided. In other words, absent other command line options, `-proc:none` is the default on JDK 23. ### Migration to `-proc:full` Several measures were undertaken to help projects prepare for the switch to `-proc:full`: - As of the April 2024 JDK security updates, support for `-proc:full` has been backported to 17u (17.0.11) and 11u (11.0.23) for both Oracle JDK and OpenJDK distributions. Additionally, Oracle's 8u release (8u411) also supports `-proc:full`. - Starting in JDK 21, javac prints an informative message if implicit usage of annotation processing under the default policy is detected. With `-proc:full` backported, it is possible to configure a build that will work the same before and after the change in javac's default policy. Additional details can be found in the original proposal [5]. [5] https://mail.openjdk.org/pipermail/jdk-dev/2024-May/009028.html ## Heads-up - Loom: New EA builds with improved Java monitors implementation to work better with virtual threads Project Loom published new early-access builds [6]. These builds have an improved object monitor implementation that should prevent virtual threads from pinning their carrier thread in the following situations: - when blocking on entering a synchronized method/statement because the object's associated monitor is held by another thread, - when parking (e.g. when doing socket I/O) while in a synchronized method, - when calling `Object.wait` while in a synchronized method. The changes for `Object.wait`/timed-`wait` is the main change since the previous Loom EA build. The Loom team is looking for help to test the changes, i.e., trying out these builds with code that is known to use virtual threads and with libraries that are "very synchronized". The primary goal is to gauge both reliability and performance. Right now, the focus is on being functional and reliable. Please note that the performance for some cases isn't yet fully on par with blocking on j.u.concurrent locks and condition objects. As before, JFR events can be used to identify remaining cases of pinning, parking or blocking in a class initializer for example. The system property `jdk.tracePinnedThreads`, which used to print stack traces when threads are pinned, no longer outputs anything. Please send feedback via email to the Loom mailing list [7] (subscription required). [6] https://jdk.java.net/loom/ [7] http://mail.openjdk.org/mailman/listinfo/loom-dev ## JDK 23 Early-Access Builds JDK 23 early-access builds 26 are now available [8] with the Release Notes here [9] and the javadocs here[10]. Those builds are provided under the GNU GPL v2, with the Classpath Exception. ### JEPs integrated into JDK 23: - JEP 455: Primitive Types in Patterns, instanceof, and switch (Preview) - JEP 466: Class-File API (2nd Preview) - JEP 467: Markdown Documentation Comments - JEP 469: Vector API (8th Incubator) - JEP 471: Deprecate the Memory-Access Methods in sun.misc.Unsafe for Removal - JEP 473: Stream Gatherers (2nd Preview) - JEP 474: ZGC: Generational Mode by Default - JEP 476: Module Import Declarations (Preview) - JEP 477: Implicitly Declared Classes and Instance Main Methods (3rd Preview) - JEP 480: Structured Concurrency (3rd Preview) - JEP 481: Scoped Values (3rd Preview) - JEP 482: Flexible Constructor Bodies (2nd Preview) ### Changes in recent JDK 23 builds that may be of interest: - JDK-8331670: Deprecate the Memory-Access Methods in sun.misc.Unsafe for Removal - JDK-8051959: Add thread and timestamp options to java.security.debug system property - JDK-8321428: Deprecate for removal the package java.beans.beancontext - JDK-8319990: Update CLDR to Version 45.0 - JDK-8331975: Enable case-insensitive check in ccache and keytab entry lookup - JDK-8328083: degrade virtual thread support for GetObjectMonitorUsage - JDK-8326666: Remove the Java Management Extension (JMX) Subject Delegation feature - JDK-8295111: dpkg appears to have problems resolving symbolically linked native libraries - JDK-8330077: Allow max number of events to be buffered to be configurable to avoid OVERFLOW_EVENT - JDK-8332476: j.u.r.RandomGeneratorFactor.create(long|byte[]) should throw rather than silently fallback to no-arg create() - JDK-8329113: Deprecate -XX:+UseNotificationThread - JDK-8331202: Support for Duration until another Instant - JDK-8316138: Add GlobalSign 2 TLS root certificates - JDK-8330276: Console methods with explicit Locale - JDK-8330005: RandomGeneratorFactory.getDefault() throws exception when the runtime image only has java.base module - JDK-6968351: httpserver clashes with delayed TCP ACKs for low Content-Length - JDK-8331021: Deprecate and then obsolete the DontYieldALot flag - JDK-8330607: Deprecate -XX:+UseEmptySlotsInSupers - JDK-8320522: Remove code related to `RegisterFinalizersAtInit` - JDK-8329636: Deprecate -XX:+PreserveAllAnnotations - JDK-8322234: Remove obsolete desktop integration from Linux installers - JDK-8328649: Disallow enclosing instances for local classes in constructor prologues - JDK-8330734: JFR: Re-engineer mirror class mechanism - JDK-8300148: Consider using a StoreStore barrier instead of Release barrier on ctor exit - JDK-8329997: Add provisions for checking memory segment alignment constraints - JDK-8305457: Implement java.io.IO - JDK-8321314: Reinstate disabling the compiler's default active annotation processing - JDK-6942632: Hotspot should be able to use more than 64 logical processors on Windows - JDK-8332614: Type-checked ConstantPool.entryByIndex and ClassReader.readEntryOrNull - JDK-8206447: InflaterInputStream.skip receives long but it's limited to Integer.MAX_VALUE Note: A more exhaustive list of changes can be found here [11]. [8] https://jdk.java.net/23/ [9] https://jdk.java.net/23/release-notes [10] https://download.java.net/java/early_access/jdk23/docs/api/ [11] https://github.com/openjdk/jdk/compare/jdk-23+17...jdk-23+26 ## New Jextract Early-Access Builds New Jextract early-access builds have been made available [12]. These builds are based on JDK 22 and bring multiple enhancements. For additional details, make sure to check [13]. Moreover, a new jextract guide [14] has been published. [12] https://jdk.java.net/jextract/ [13] https://mail.openjdk.org/pipermail/jextract-dev/2024-May/001699.html [14] https://github.com/openjdk/jextract/blob/master/doc/GUIDE.md ## JavaFX Early-Access Builds These are early access builds of the JavaFX 23 Runtime built from openjdk/jfx [15]. These builds enable JavaFX application developers to build and test their applications with JavaFX 23 on JDK 23. Although these builds are designed to work with JDK 23EA, they are also known to work with JDK 21 and later versions. The latest early access builds of JavaFX 23 are available here [16], under the GNU General Public License, version 2, with the Classpath Exception. JavaFX 23 API Javadocs [17] are also available. [15] https://github.com/openjdk/jfx [16] https://jdk.java.net/javafx23/ [17] https://download.java.net/java/early_access/javafx23/docs/api/overview-summary.html ## Topics of Interest - All Java 23 Features - Inside Java Newscast https://inside.java/2024/06/06/newscast-70/ - Module Imports in Java 23 - Inside Java Newscast https://inside.java/2024/05/16/newscast-69/ - Java 23: JavaDoc Hits the Markdown on Comments - Inside Java Newscast https://inside.java/2024/05/01/newscast-68/ - Java 23: Restoring the Balance with Primitive Patterns - Inside Java Newscast https://inside.java/2024/04/04/newscast-66/ - Java in 2024 - Constant evolution, delivered. https://inside.java/2024/06/01/java-in-2024-keynote/ - Introduction to JDK Mission Control https://inside.java/2024/05/18/jmc-intro/ - What's New in JMC 9? - Sip of Java https://inside.java/2024/04/21/sip096/ - Programmer's Guide to JDK Flight Recorder https://inside.java/2024/04/12/programmer-guide-to-jfr/ - A Decade of JDK Updates in OpenJDK https://inside.java/2024/04/09/a-decade-of-jdk-updates/ - Data-Oriented Programming - Version 1.1 https://inside.java/2024/05/23/dop-v1-1-introduction/ ~ As usual, let us know if you find any issues while testing your project(s) with the latest JDK early-access builds. Thank you! --David |
From: Stefan R. <ste...@gm...> - 2024-04-05 00:13:16
|
Dear Folks, most of you probably got the APIdia announcement already via jython-user (for those who didn't, it is appended below). Since this is the dev list, I would like to point out that also a snapshot of the Jython 3 core ( github.com/jython/jython/tree/main) is available on APIdia at https://apidia.net/java/Jython/3.0.0-snapshot Jython 3 is pre-alpha and experimental, so it is not accessible by the search on the landing page apidia.net -- just directly via the given link. --- original announcement to jython-users --- Dear Jythonistas, Jython and Java enthusiasts, with this email I proudly announce that a new Java API documentation website is in town and Jython is among the first projects being hosted. Please check it out at apidia.net/java/Jython The documentation resembles Javadoc but with some improvements. Perhaps most notably, it revives the package and class side navigation, which Javadoc used to have until Java 12. (That was removed due to deprecation of frames. On APIdia, it is implemented in a future-proof way.) The search field was intended as a replacement, but I always felt that a structured API navigation and a search field are really two things. To address that, on APIdia you have both. Similar to Javadoc, the search field searches names of classes/interfaces etc., members, packages and modules. On APIdia, it also features regex functionality (e.g. "|", "^", "$" work as "or", "start" and "end", respectively) with following special rules: spaces are interpreted as ".*", which means you can type space-separated snippets of a long name to quickly specify your target. If the search text contains a ".", fully qualified names are searched. While you navigate through docs, the site maintains a parameterized url that can serve as a link to the current view state. As of this writing, APIdia hosts the full Java 22 standard library and several hundred artifacts from Maven Central. In addition to Jython, that includes Guava, all other Jython dependencies, Netty, Jetty, JavaFX, Jakarta and Java EE artifacts, most of Apache commons and Spring to some extent. All hosted projects are fully interlinked. Various design details are improved over Javadoc. To name some, function args have mouseover tooltip texts (if corresponding docs are available). Summary lines are robust: sentences do not end prematurely with common abbreviations like "e.g.", "i.e." and so on. Common patterns such as "Note: ...", "Warning: ...", "Issue: ..." etc. are rendered as proper admonition boxes. Functions transparently indicate if some other function is overridden, implemented, hidden or redeclared, whether and where from doc is inherited, and whether deprecation is inherited. In the top-right menu, you can edit visibility settings and turn on private methods, internal packages and modules. If you check and uncheck the boxes, the site adjusts the displayed content accordingly. So, if you want to hack on Jython internals, this is the place for you. With this functionality, the site is still lightweight and fast. Since it is free of tracking, you won't be bothered by annoying cookie banners. What's more to say? APIdia launched just days ago, so what it needs now is users. If you like the site, please spread the word to your fellow devs and kindly provide feedback, so it can improve. Happy API documentation browsing! Stefan |
From: David D. <dav...@or...> - 2024-04-02 09:46:12
|
Welcome to the latest OpenJDK Quality Outreach update! Java 22 was just released along with JavaFX 22 [1][2]. Thank you to all the projects who contributed to those releases by testing and providing feedback using their respective early-access builds. And to celebrate that, the Java DevRel Team hosted a +4h live-stream with guests such as Brian Goetz, Viktor Klang, Alan Bateman, etc. You can watch the launch stream replay here [3]. The JDK 23 schedule is now known [4] with rampdown starting early June and general availability sets for mid-September. So far, 2 JEPs have been targeted to JDK 23: - JEP 455: Primitive Types in Patterns, instanceof, and switch (Preview) [5] - JEP 466: Class-File API (2nd Preview) [6] The focus should now be shifted to testing your project(s) on JDK 23. And don't forget that the Oracle setup-java github action [7] supports, amongst others, the latest OpenJDK 23 Early-Access builds. So, JDK 23 EA testing is literally one pipeline away. [1] https://mail.openjdk.org/pipermail/jdk-dev/2024-March/008827.html [3] https://jdk.java.net/javafx22/ [3] https://www.youtube.com/live/AjjAZsnRXtE?feature=shared&t=278 [4] https://openjdk.org/projects/jdk/23/ [5] https://openjdk.org/jeps/455 [6] https://openjdk.org/jeps/466 [7] https://github.com/oracle-actions/setup-java ## Heads-up: JDK 20-23: Support for Unicode CLDR Version 42 The JDK update to CLDR version 42 included a change where regular spaces in date/time formats (and some other formatted values) were replaced with (narrow) non-breaking spaces. This lead to issues for existing code that relied on parsing such strings. To address that, JDK 23 allows loose matching of spaces when parsing date/time strings. Loose matching is performed in the lenient parsing style for both date/time parsers in `java.time.format` and `java.text` packages. In the default strict parsing style, those spaces are considered distinct as before. Please read this updated heads-up [9] for details on how to configure strict/lenient parsing in the `java.time.format` (strict by default) and `java.text` (lenient by default) packages. [9] https://inside.java/2024/03/29/quality-heads-up/ ## Heads-up: macOS 14 users running on Apple silicon systems should update directly to macOS 14.4.1 An issue introduced by macOS 14.4 caused some Java processes, regardless of the Java version, to terminate unexpectedly on Apple silicon (AArch64). On March 25 Apple released macOS 14.4.1 and indicated on their support site that it addresses this issue. Oracle can confirm that after applying macOS 14.4.1 we are unable to reproduce the problem. So, Java users on macOS 14 running on Apple silicon systems should skip macOS 14.4 and update directly to macOS 14.4.1. More details can be found on https://blogs.oracle.com/java/post/java-on-macos-14-4 ## JDK 23 Early-Access Builds The JDK 23 EA builds 16 are available [10], and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes [11] are also available. ### Changes in recent JDK 23 builds that may be of interest: - JDK-8324774: Add DejaVu web fonts (reported by AssertJ) - JDK-8327385: Add JavaDoc option to exclude web fonts from generated documentation (reported by AssertJ) - JDK-8328638: Fallback option for POST-only OCSP requests - JDK-8320362: Load anchor certificates from Keychain keystore - JDK-8327875: ChoiceFormat should advise throwing UnsupportedOperationException for unused methods - JDK-8296244: Alternate implementation of user-based authorization Subject APIs that doesn’t depend on Security Manager APIs - JDK-8327818: Implement Kerberos debug with sun.security.util.Debug - JDK-7036144: GZIPInputStream readTrailer uses faulty available() test for end-of-stream - JDK-8319251: Change LockingMode default from LM_LEGACY to LM_LIGHTWEIGHT - JDK-8327651: Rename DictionaryEntry members related to protection domain - JDK-8321408: Add Certainly roots R1 and E1 - JDK-8164094: javadoc allows to create a @link to a non-existent method - JDK-8325496: Make TrimNativeHeapInterval a product switch - JDK-8174269: Remove COMPAT locale data provider from JDK - JDK-8322750: Test "api/java_awt/interactive/SystemTrayTests.html" failed because … - JDK-8139457: Relax alignment of array elements - JDK-8256314: JVM TI GetCurrentContendedMonitor is implemented incorrectly - JDK-8326908: DecimalFormat::toPattern throws OutOfMemoryError when pattern is empty string - JDK-8247972: incorrect implementation of JVM TI GetObjectMonitorUsage - JDK-8325580: Remove "alternatives --remove" call from Java rpm installer - JDK-8326838: JFR: Native mirror events - JDK-8326106: Write and clear stack trace table outside of safepoint - JDK-8323183: ClassFile API performance improvements - JDK-8324829: Uniform use of synchronizations in NMT - JDK-8326586: Improve Speed of System.map - JDK-8318761: MessageFormat pattern support for CompactNumberFormat, ListFormat, and DateTimeFormatter - JDK-8265372: Simplify PKCS9Attribute - JDK-8317431: Implement simpler Comparator when building certification paths - JDK-8327093: Add truncate function to BitMap API Note: A more detailed list of changes can be found here [12]. [10] https://jdk.java.net/23/ [11] https://jdk.java.net/23/release-notes [12] https://github.com/openjdk/jdk/compare/jdk-23+10...jdk-23+16 ## JavaFX 23 Early-Access Builds These are early access builds of the JavaFX 23 Runtime built from openjdk/jfx [13]. These builds enable JavaFX application developers to build and test their applications with JavaFX 23 on JDK 23. Although these builds are designed to work with JDK 23, they are also known to work with JDK 17 and later versions. The latest early access builds of JavaFX 23 Builds 10 (2024/3/26) are available [14], under the GNU General Public License, version 2, with the Classpath Exception. [13] https://github.com/openjdk/jfx [14] https://jdk.java.net/javafx23/ ## Topics of Interest: - The Arrival of Java 22 https://inside.java/2024/03/19/the-arrival-of-java-22/ - JDK 22 Release Notes Review (video) https://inside.java/2024/03/14/newscast-65/ - Java 22 in 2 Minutes https://inside.java/2024/03/21/sip095/ - (Dirty?) Tricks in Java 22 https://inside.java/2024/02/29/newscast-64/ - JDK 22 Security Enhancements https://seanjmullan.org/blog/2024/03/20/jdk22 - Java 17 to 21 - A Showcase of JDK Security Enhancements https://inside.java/2024/03/03/jfokus-jdk-security-changes/ - Netflix - Bending Pause Times to Your Will with Generational ZGC https://netflixtechblog.com/bending-pause-times-to-your-will-with-generational-zgc-256629c9386b - MethodHandle Primer https://jornvernee.github.io/methodhandles/2024/01/19/methodhandle-primer.html - Pruning Dead Exception Handlers https://jornvernee.github.io/hotspot/jit/2024/02/16/prune-dead-exception-handlers.html - Update on String Templates (JEP 459) https://mail.openjdk.org/pipermail/amber-spec-experts/2024-March/004010.html - The State of OpenJDK https://inside.java/2024/02/23/fosdem2024-openjdk-state/ - Project Wakefield - The JDK Wayland Desktop on Linux https://inside.java/2024/03/24/openjdk-wakefield/ - Project Leyden - Capturing Lightning in a Bottle https://inside.java/2024/02/28/leyden/ - jlink - Java's Custom Runtime Builder https://inside.java/2024/02/25/jlink-stackwalker/ - Modern Java in Action https://inside.java/2024/03/09/jfokus-modern-java-action/ - New Java Platform Extension for VS Code Release https://inside.java/2024/03/27/vscode-extension-update/ ~ That's it for this instalment. And don't forget to ping me if you encounter issues with JDK 23 EA builds. --David |
From: David D. <dav...@or...> - 2024-02-20 09:08:37
|
Welcome to the latest OpenJDK Quality Outreach update! The first JDK 22 Release Candidates builds are now available [1]. At this stage, only P1 issues will still be evaluated. And with the JDK 22 General Availability set for March 19th, it is now time to fully focus on JDK 23. At the time of writing, one JEP has already been integrated in JDK 23, i.e., JEP 455: 'Primitive Types in Patterns, instanceof, and switch (Preview)' [2]. But new JEP candidates [3][4] have recently been announced, so things should evolve rapidly. I'd like to thank those of you who have already provided feedback on the JDK 22 EA builds. Feedback is always extremely useful, even more, when it comes early in the development cycle. Another area where we need your help is Loom. So, please make sure to check the heads-up below that discusses the so-called Virtual Threads "pinning" issue. [1] https://openjdk.org/projects/jdk/22/ [2] https://openjdk.org/jeps/455 [3] https://openjdk.org/jeps/465 [4] https://openjdk.org/jeps/466 ## Heads-up: Virtual Threads “Pinning” Issue Virtual threads became a permanent feature in JDK 21. This feature has been extremely well received by the Java ecosystem but there are still a few pain points. Much has been written about the so-called "pinning" issue that arises with synchronized methods or synchronized statements. The two most common cases are (a) a virtual thread parks (ex. doing socket I/O) while in a synchronized method, and (b) a virtual thread blocks entering a synchronized method because the object's associated monitor is held by another thread. In both cases, the underlying carrier/native thread is not "released" to do other work. Performance and scalability may suffer and in some cases, starvation and deadlock might happen. This recent "Virtual Threads Next Steps" video [5] explains in more details the why's and discusses some potential solutions. New Loom early-access builds haven been recently published [6]. Those Loom EA builds have changes to the object monitor implementation that do not pin for these two common cases. The Loom team needs your help to test these updated object monitors with code that you know is using virtual threads and with libraries that are heavily synchronized. The goal is to gauge both reliability and performance. The simplest way to report an issue or feedback is to use the Loom mailing list [7]. For the VM savvy, testing with both `-XX:LockingMode=1` (current default) and `-XX:LockingMode=2` would be extremely helpful as that would exercise the two locking modes currently implemented by the HotSpot VM. [5] https://inside.java/2024/02/17/virtual-threads-next-steps/ [6] https://jdk.java.net/loom/ [7] https://mail.openjdk.org/pipermail/loom-dev/ ## JDK 22 Release Candidates The JDK 22 Release Candidate builds (builds 36) are available [8] and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes are available here [9], and the javadocs here [10]. [8] https://jdk.java.net/22/ [9] https://jdk.java.net/22/release-notes [10] https://download.java.net/java/early_access/jdk22/docs/api/ ## JDK 23 Early-Access Builds The JDK 23 Early-Access builds 10 are available [11], and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes are available here [12]. ### Changes in recent JDK 23 builds that may be of interest: - JDK-8324287: Record total and free swap space in JFR - JDK-8275338: Add JFR events for notable serialization situations - JDK-8324665: Loose matching of space separators in the lenient date/time parsing mode - JDK-8324066: "clhsdb jstack" should not by default scan for j.u.c locks because it can be very slow - JDK-8323699: MessageFormat.toPattern() generates non-equivalent MessageFormat pattern - JDK-8325221: Obsolete TLABStats - JDK-8322535: Change default AArch64 SpinPause instruction - JDK-8323746: Add PathElement hashCode and equals - JDK-8325570: Update to Graphviz 9.0.0 - JDK-8303866: Allow ZipInputStream.readEnd to parse small Zip64 ZIP files - JDK-8320458: Improve structural navigation in API documentation - JDK-8324068: Improve references to tags in the Doc Comment Spec - JDK-8322366: Add IEEE rounding mode corruption check to JNI checks - JDK-8321545: Override toString() for Format subclasses - JDK-8324301: Obsolete MaxGCMinorPauseMillis - JDK-8324632: Update Zlib Data Compression Library to Version 1.3.1 - JDK-8324771: Obsolete RAMFraction related flags - JDK-8323645: Remove unused internal sun.net.www.protocol.jar.URLJarFileCa… - JDK-8325150: (tz) Update Timezone Data to 2024a - JDK-8324571: JDK 23 L10n resource files update Note: Complete list of changes can be found here [13]. [11] https://jdk.java.net/23/ [12] https://jdk.java.net/23/release-notes [13] https://github.com/openjdk/jdk/compare/jdk-23+6...jdk-23+10 ## JavaFX Early-Access Builds: These are early access builds of the JavaFX 22 & 23 Runtime built from openjdk/jfx [14]. These builds enable JavaFX application developers to build and test their applications with JavaFX 22 & 23 on JDK 22 & 23 respectively. Although these builds are designed to work with JDK 22 and above, they are also known to work with JDK 17 and later versions. The latest early access builds of JavaFX 22 Builds 29 are available [15], under the GNU General Public License, version 2, with the Classpath Exception. JavaFX 22 API Javadocs [16] are also available. The latest early access builds of JavaFX 23 Builds 5 are available [17], under the GNU General Public License, version 2, with the Classpath Exception. JavaFX 23 API Javadocs [18] are also available. [14] https://github.com/openjdk/jfx [15] https://jdk.java.net/javafx22/ [16] https://download.java.net/java/early_access/javafx22/docs/api/overview-summary.html [17] https://jdk.java.net/javafx23/ [18] https://download.java.net/java/early_access/javafx23/docs/api/overview-summary.html ## Topics of Interest - Java Renaissance Keynote https://inside.java/2024/02/05/java-renaissance/ - Managing Throughput with Virtual Threads - Sip of Java https://inside.java/2024/02/04/sip094/ - Data-Oriented Programming in Java 21 - JEP Café https://inside.java/2024/02/08/jepcafe22/ - Does Java 22 Kill Build Tools? - Inside Java Newscast https://inside.java/2024/02/15/newscast-63/ - JDK 22 G1/Parallel/Serial GC changes https://tschatzl.github.io/2024/02/06/jdk22-g1-parallel-gc-changes.html - Java 22 Previews Statements Before super(...) and this(...) https://inside.java/2024/02/01/newscast-62/ - State of jextract https://cr.openjdk.org/~mcimadamore/panama/jextract_changes.html - FOSDEM 2024: FFM API - A (quick) peek under the hood https://inside.java/2024/02/13/fosdem2024-ffm-api/ - FOSDEM 2024: Virtual Threads - Next Steps https://inside.java/2024/02/17/virtual-threads-next-steps/ - Java Language Update - Early 2024 Edition https://inside.java/2024/02/18/java-language-update-early-2024-update/ - When Should a Compiler Expand Garbage Collection Barriers? https://robcasloz.github.io/blog/2024/02/14/when-should-a-compiler-expand-garbage-collection-barriers.html - Emulating C# LINQ in Java using Code Reflection https://openjdk.org/projects/babylon/articles/linq - Automatic differentiation of Java code using Code Reflection https://openjdk.org/projects/babylon/articles/auto-diff ## Java Cryptographic Roadmap Update The Java Cryptographic Roadmap [19] has been updated with the following planned changes. * Enable XML Signature secure validation mode by default on JDK 11 and JDK 8 - Target date changed from the July 2024 CPU to the April 2024 CPU. - This change has already been made in JDK 17 and later releases. * Disable DTLS 1.0 in JDK 17 and 11 with the July 2024 CPU - This change has already been made in JDK 20 and later releases. - DTLS is not available in releases prior to JDK 9. [19] https://www.java.com/en/jre-jdk-cryptoroadmap.html ~ That's it for this installment. As usual, if you have issues, or questions, please ping me. --David |
From: David D. <dav...@or...> - 2024-01-26 11:30:33
|
Greetings! We are starting 2024 with JDK 22 as it has just entered Rampdown Phase 2 [1]. And with the initial JDK 22 Release Candidates now less than 2 weeks away (Feb. 8th) [2], it is time to shift our attention to JDK 23. After multiple rounds of incubations and preview, the Foreign Function & Memory API is becoming standard and permanent in JDK 22. If we put its 'Function' angle aside, this API also offers a standard and secure way to access off-heap API. And that brings us to the heads-up below 'Deprecate the memory-access methods in sun.misc.Unsafe for removal in a future release' as developers still using sun.misc.Unsafe for accessing memory are strongly encouraged to start preparing their plans to migrate away from those unsafe methods. [1] https://mail.openjdk.org/pipermail/jdk-dev/2024-January/008675.html [2] https://openjdk.org/projects/jdk/22/ ## Heads-up: Deprecate the Memory-Access Methods in sun.misc.Unsafe for Removal in a Future Release The effort focused on enforcing the integrity of the Java platform [3] continues! The next phase in that long but important initiative will most likely target the sun.misc.Unsafe API used for accessing memory. Those methods alone represent 79 methods out of the 87 sun.misc.Unsafe methods! This draft JEP [4] outlines the plan to deprecate for removal the sun.misc.Unsafe Memory-Access methods, the reasons, and the standard alternatives. As the draft plan suggests, the first step will be to deprecate all memory-access methods (on-heap, off-heap, and bimodal) for removal. This will cause compile-time deprecation warnings for code that refers to the methods, alerting library developers to their forthcoming removal. In addition, a new command-line option will allow users to receive runtime warnings when those methods are used. This command-line will help users to assess if their codebase uses those unsafe API to access memory. It should be mentioned that other tools such as JFR and jdeprscan can also be used to detect the use of those deprecated APIs. Library developers are strongly encouraged to migrate from sun.misc.Unsafe to the supported replacements, so that applications can migrate smoothly to modern JDKs. The initial step will be to conduct investigations to understand if, how, and where sun.misc.Unsafe methods are used to access memory. [3] https://openjdk.org/jeps/8305968 [4] https://openjdk.org/jeps/8323072 ## Heads-up: Java Array Element Alignment - Weakening of Some Methods Guarantees ? Some methods make promises about Java array element alignment that are too strong. There are some ongoing reflexions to change the implementation (and the specification) of `MethodHandles::byteArrayViewVarHandle`, `MethodHandles::byteBufferViewVarHandle`, `ByteBuffer::alignedSlice`, and `ByteBuffer::alignmentOffset` to weaken the guarantees they make about the alignment of Java array elements, in order to bring them in line with the guarantees made by an arbitrary JVM implementation. For more details, make sure to check JDK-8320247 [5] and the related PR [6] but in a nutshell, the new behaviour would be : - The `VarHandle` returned by `MethodHandles::byteArrayViewVarHandle` would only support `get` and `set` methods, and all other access methods would throw an exception. - The `VarHandle` returned by `MethodHandles::byteBufferViewHandle` would only support the `get` and `set` access methods when a heap buffer is used, and all other access methods would throw an exception when used with a heap buffer. Direct byte buffers will continue to work the same way. - The `ByteBuffer::alignmentOffset` and `ByteBuffer::alignedSlice` methods would throw an exception if the buffer is a heap buffer, and the given `unitSize` is greater than 1. If you have relevant feedback about this potential change, please make sure to bring it to the core-libs-dev mailing list [7], or comment on the PR [6]. [5] https://bugs.openjdk.org/browse/JDK-8320247 [6] https://github.com/openjdk/jdk/pull/16681 [7] https://mail.openjdk.org/pipermail/core-libs-dev/ ## JDK 22 Early-Access Builds JDK 22 Early-Access builds 33 are now available [8], and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes [9] and the javadocs [10] are also available. ### Changes in recent JDK 22 builds that may be of interest: - JDK-8320597: RSA signature verification fails on signed data that does not encode params correctly [Reported by Apache POI] - JDK-8322214: Return value of XMLInputFactory.getProperty() changed from boolean to String in JDK 22 early access builds [Reported by Apache POI] - JDK-8322725: (tz) Update Timezone Data to 2023d - JDK-8321480: ISO 4217 Amendment 176 Update - JDK-8314468: Improve Compiler loops - JDK-8314295: Enhance verification of verifier - JDK-8316976: Improve signature handling - JDK-8317547: Enhance TLS connection support - JDK-8318971: Better Error Handling for Jar Tool When Processing Non-existent Files - JDK-8323659: LinkedTransferQueue add and put methods call overridable offer Note: A complete list of changes can be found here [11]. [8] https://jdk.java.net/22/ [9] https://jdk.java.net/22/release-notes [10] https://download.java.net/java/early_access/jdk22/docs/api/ [11] https://github.com/openjdk/jdk/compare/jdk-22+27...jdk-22+33 ## JDK 23 Early-Access builds JDK 23 Early-Access builds 7 are available [12] for testing. These EA builds are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes [13] are also available. ### Changes in recent JDK 23 builds that may be of interest: - JDK-8320597: RSA signature verification fails on signed data that does not encode params correctly [Reported by Apache POI] - JDK-8322214: Return value of XMLInputFactory.getProperty() changed from boolean to String in JDK 22 early access builds [Reported by Apache POI] - JDK-8321545: Override toString() for Format subclasses - JDK-8322366: Add IEEE rounding mode corruption check to JNI checks - JDK-8322383: G1: Only preserve marks on objects that are actually moved - JDK-8275338: Add JFR events for notable serialization situations - JDK-8320458: Improve structural navigation in API documentation - JDK-8320786: Remove ThreadGroup.stop - JDK-8320532: Remove Thread/ThreadGroup suspend/resume - JDK-8312150: Remove -Xnoagent option - JDK-8322829: Refactor nioBlocker to avoid blocking while holding Thread's interrupt lock - JDK-8322725: (tz) Update Timezone Data to 2023d - JDK-8321480: ISO 4217 Amendment 176 Update - JDK-8318971: Better Error Handling for Jar Tool When Processing Non-existent Files - JDK-8321594: NativeThreadSet should use placeholder for virtual threads - JDK-8321940: Improve CDSHeapVerifier in handling of interned strings - JDK-8321802: (zipfs) Add validation of incorrect LOC signature in ZipFileSystem - JDK-8322841: Parallel: Remove unused using-declaration in MutableNUMASpace - JDK-8319626: Override toString() for ZipFile - JDK-8322878: Including sealing information Class.toGenericString() Note: A more exhaustive changes list can be found here [14]. [12] https://jdk.java.net/23/ [13] https://jdk.java.net/23/release-notes [14] https://github.com/openjdk/jdk/compare/jdk-23+1...jdk-23+7 ## JavaFX 22 & 23 Early-Access Builds These are early access builds of the JavaFX 22 Runtime built from openjdk/jfx [14]. These builds enable JavaFX application developers to build and test their applications with JavaFX 22 on JDK 22. Although JavaFX 22 is designed to work with JDK 22, it is also known to work with JDK 17 and later versions. The latest early access builds of JavaFX 22 Builds 26 (2024/1/20) are available [15], under the GNU General Public License, version 2, with the Classpath Exception. JavaFX 22 API Javadocs [16] are also available. The first early access builds (2024/1/19) of JavaFX 23 are now also available [17]. [14] https://github.com/openjdk/jfx [15] https://jdk.java.net/javafx22/ [16] https://download.java.net/java/early_access/javafx22/docs/api/overview-summary.html [17] https://jdk.java.net/javafx23/ ## Topics of Interest - Podcast “The Panama Effect” with Jorn Vernee https://inside.java/2024/01/08/podcast-032/ - Java's Plans for 2024 - Inside Java Newscast https://inside.java/2024/01/18/newscast-61/ - Java 22 Unpacking - Inside Java Newscast https://inside.java/2023/12/07/newscast-59/ - Java Highlights of 2023 - Inside Java Newscast https://inside.java/2023/12/21/newscast-60/ - JDK 21: The GCs keep getting better https://kstefanj.github.io/2023/12/13/jdk-21-the-gcs-keep-getting-better.html - Java SE Security Developer’s Guide https://docs.oracle.com/en/java/javase/21/security/index.html#Java-Platform%2C-Standard-Edition - Another VS Code Extension for Java https://inside.java/2023/12/03/java-vscode-extension/ ## January 2024 Critical Patch Update Released As part of the January 2024 CPU, Oracle released OpenJDK 21.0.2, JDK 21.0.2 LTS, JDK 17.0.10 LTS, 11.0.22 LTS, 8u401, and 8u401-perf. ~ As usual, let us know if you find any quirks while testing your project(s) with the latest JDK early-access builds. --David |
From: Jython t. <st...@bu...> - 2024-01-12 18:15:42
|
ACTIVITY SUMMARY (2024-01-05 - 2024-01-12) Jython tracker at https://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 346 ( +0) closed 2504 ( +0) total 2850 ( +0) Open issues with patches: 22 Most recent 15 issues with no replies (15) ========================================== #2938: import MessageSource does not work anymore with jython2.7.2 https://bugs.jython.org/issue2938 #2936: can't use SO_EXCLUSIVEADDRUSE in jython2.7.2 https://bugs.jython.org/issue2936 #2934: Filereader.read: TypeError: read(): 1st arg can't be coerced t https://bugs.jython.org/issue2934 #2916: Saving output of script which has korean string to a file https://bugs.jython.org/issue2916 #2898: Fix serialization format https://bugs.jython.org/issue2898 #2886: doing relative imports in a loop causes bad performance due to https://bugs.jython.org/issue2886 #2878: java.lang.OutOfMemoryError: Java heap space https://bugs.jython.org/issue2878 #2876: NullPointer exception PyModule.java https://bugs.jython.org/issue2876 #2874: Jython 2.7 is not able to import an EBCDIC file on z/OS https://bugs.jython.org/issue2874 #2866: Interface default methods disregarded by the method resolver https://bugs.jython.org/issue2866 #2864: Importing second instance of httplib causes an error https://bugs.jython.org/issue2864 #2854: from module import * leads to wild goose chase https://bugs.jython.org/issue2854 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 #1612: array.array should use specialized bulk operations to initiali https://bugs.jython.org/issue1612 #1435: traceback doesn't include Java stack trace in user functions https://bugs.jython.org/issue1435 #1336: PyDeque should likely subclass PySequence https://bugs.jython.org/issue1336 |
From: Jython t. <st...@bu...> - 2024-01-05 18:05:40
|
ACTIVITY SUMMARY (2023-12-29 - 2024-01-05) Jython tracker at https://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 346 ( +0) closed 2504 ( +0) total 2850 ( +0) Open issues with patches: 22 Most recent 15 issues with no replies (15) ========================================== #2938: import MessageSource does not work anymore with jython2.7.2 https://bugs.jython.org/issue2938 #2936: can't use SO_EXCLUSIVEADDRUSE in jython2.7.2 https://bugs.jython.org/issue2936 #2934: Filereader.read: TypeError: read(): 1st arg can't be coerced t https://bugs.jython.org/issue2934 #2916: Saving output of script which has korean string to a file https://bugs.jython.org/issue2916 #2898: Fix serialization format https://bugs.jython.org/issue2898 #2886: doing relative imports in a loop causes bad performance due to https://bugs.jython.org/issue2886 #2878: java.lang.OutOfMemoryError: Java heap space https://bugs.jython.org/issue2878 #2876: NullPointer exception PyModule.java https://bugs.jython.org/issue2876 #2874: Jython 2.7 is not able to import an EBCDIC file on z/OS https://bugs.jython.org/issue2874 #2866: Interface default methods disregarded by the method resolver https://bugs.jython.org/issue2866 #2864: Importing second instance of httplib causes an error https://bugs.jython.org/issue2864 #2854: from module import * leads to wild goose chase https://bugs.jython.org/issue2854 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 #1612: array.array should use specialized bulk operations to initiali https://bugs.jython.org/issue1612 #1435: traceback doesn't include Java stack trace in user functions https://bugs.jython.org/issue1435 #1336: PyDeque should likely subclass PySequence https://bugs.jython.org/issue1336 |
From: Jeff A. <ja...@fa...> - 2023-12-31 16:19:49
|
I managed to do this (in 2.7.3): >>> from java.lang import Double >>> from java.util import Arrays >>> from java.util.function import DoubleBinaryOperator >>> class DoubleSum(DoubleBinaryOperator): ... applyAsDouble = Double.sum ... >>> doubleSum = DoubleSum() >>> dd = list(map(float, range(10))) >>> dd [0.0, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0] >>> Arrays.stream(dd).reduce(-3.0, doubleSum) 42.0 I chose Double here for a quick test, rather than Float, because I wasn't sure the coercion to float would work. There does not seem to be a way to supply Double.sum directly but you can wrap it as shown in the right type with the right method name. This seems to me not far from what the Java compiler is doing for you when you use ::. I haven't stepped through to see what happens under the covers. Is this better than the delegation you indicate? Jeff On 30/12/2023 22:26, Albert Cardona wrote: > Hi all, > > Is there any way to use something akin to the double colon notation, > to use a static method as a Function in a collection stream? > > Otherwise, if I have to instantiate it as a jython class that then > delegates to the static method, performance suffers greatly. > > For example, how can one use java.lang.Float's sum method, which takes > two floating-point numbers as arguments, in a reduce operation? > > Thank you. > > Best wishes, > > Albert > > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev -- Jeff Allen |
From: Albert C. <sap...@gm...> - 2023-12-30 22:27:11
|
Hi all, Is there any way to use something akin to the double colon notation, to use a static method as a Function in a collection stream? Otherwise, if I have to instantiate it as a jython class that then delegates to the static method, performance suffers greatly. For example, how can one use java.lang.Float's sum method, which takes two floating-point numbers as arguments, in a reduce operation? Thank you. Best wishes, Albert |
From: Jython t. <st...@bu...> - 2023-12-29 18:05:39
|
ACTIVITY SUMMARY (2023-12-22 - 2023-12-29) Jython tracker at https://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 346 ( +0) closed 2504 ( +0) total 2850 ( +0) Open issues with patches: 22 Most recent 15 issues with no replies (15) ========================================== #2938: import MessageSource does not work anymore with jython2.7.2 https://bugs.jython.org/issue2938 #2936: can't use SO_EXCLUSIVEADDRUSE in jython2.7.2 https://bugs.jython.org/issue2936 #2934: Filereader.read: TypeError: read(): 1st arg can't be coerced t https://bugs.jython.org/issue2934 #2916: Saving output of script which has korean string to a file https://bugs.jython.org/issue2916 #2898: Fix serialization format https://bugs.jython.org/issue2898 #2886: doing relative imports in a loop causes bad performance due to https://bugs.jython.org/issue2886 #2878: java.lang.OutOfMemoryError: Java heap space https://bugs.jython.org/issue2878 #2876: NullPointer exception PyModule.java https://bugs.jython.org/issue2876 #2874: Jython 2.7 is not able to import an EBCDIC file on z/OS https://bugs.jython.org/issue2874 #2866: Interface default methods disregarded by the method resolver https://bugs.jython.org/issue2866 #2864: Importing second instance of httplib causes an error https://bugs.jython.org/issue2864 #2854: from module import * leads to wild goose chase https://bugs.jython.org/issue2854 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 #1612: array.array should use specialized bulk operations to initiali https://bugs.jython.org/issue1612 #1435: traceback doesn't include Java stack trace in user functions https://bugs.jython.org/issue1435 #1336: PyDeque should likely subclass PySequence https://bugs.jython.org/issue1336 |
From: Jython t. <st...@bu...> - 2023-12-22 18:05:33
|
ACTIVITY SUMMARY (2023-12-15 - 2023-12-22) Jython tracker at https://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 346 ( +0) closed 2504 ( +0) total 2850 ( +0) Open issues with patches: 22 Most recent 15 issues with no replies (15) ========================================== #2938: import MessageSource does not work anymore with jython2.7.2 https://bugs.jython.org/issue2938 #2936: can't use SO_EXCLUSIVEADDRUSE in jython2.7.2 https://bugs.jython.org/issue2936 #2934: Filereader.read: TypeError: read(): 1st arg can't be coerced t https://bugs.jython.org/issue2934 #2916: Saving output of script which has korean string to a file https://bugs.jython.org/issue2916 #2898: Fix serialization format https://bugs.jython.org/issue2898 #2886: doing relative imports in a loop causes bad performance due to https://bugs.jython.org/issue2886 #2878: java.lang.OutOfMemoryError: Java heap space https://bugs.jython.org/issue2878 #2876: NullPointer exception PyModule.java https://bugs.jython.org/issue2876 #2874: Jython 2.7 is not able to import an EBCDIC file on z/OS https://bugs.jython.org/issue2874 #2866: Interface default methods disregarded by the method resolver https://bugs.jython.org/issue2866 #2864: Importing second instance of httplib causes an error https://bugs.jython.org/issue2864 #2854: from module import * leads to wild goose chase https://bugs.jython.org/issue2854 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 #1612: array.array should use specialized bulk operations to initiali https://bugs.jython.org/issue1612 #1435: traceback doesn't include Java stack trace in user functions https://bugs.jython.org/issue1435 #1336: PyDeque should likely subclass PySequence https://bugs.jython.org/issue1336 |
From: Jython t. <st...@bu...> - 2023-12-15 18:05:37
|
ACTIVITY SUMMARY (2023-12-08 - 2023-12-15) Jython tracker at https://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 346 ( +0) closed 2504 ( +0) total 2850 ( +0) Open issues with patches: 22 Most recent 15 issues with no replies (15) ========================================== #2938: import MessageSource does not work anymore with jython2.7.2 https://bugs.jython.org/issue2938 #2936: can't use SO_EXCLUSIVEADDRUSE in jython2.7.2 https://bugs.jython.org/issue2936 #2934: Filereader.read: TypeError: read(): 1st arg can't be coerced t https://bugs.jython.org/issue2934 #2916: Saving output of script which has korean string to a file https://bugs.jython.org/issue2916 #2898: Fix serialization format https://bugs.jython.org/issue2898 #2886: doing relative imports in a loop causes bad performance due to https://bugs.jython.org/issue2886 #2878: java.lang.OutOfMemoryError: Java heap space https://bugs.jython.org/issue2878 #2876: NullPointer exception PyModule.java https://bugs.jython.org/issue2876 #2874: Jython 2.7 is not able to import an EBCDIC file on z/OS https://bugs.jython.org/issue2874 #2866: Interface default methods disregarded by the method resolver https://bugs.jython.org/issue2866 #2864: Importing second instance of httplib causes an error https://bugs.jython.org/issue2864 #2854: from module import * leads to wild goose chase https://bugs.jython.org/issue2854 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 #1612: array.array should use specialized bulk operations to initiali https://bugs.jython.org/issue1612 #1435: traceback doesn't include Java stack trace in user functions https://bugs.jython.org/issue1435 #1336: PyDeque should likely subclass PySequence https://bugs.jython.org/issue1336 |
From: David D. <dav...@or...> - 2023-12-13 17:27:39
|
Welcome to the final OpenJDK Quality Outreach update of 2023! JDK 22, scheduled for General Availability on March 19, 2024, is now in Rampdown Phase One (RDP1) [1]. At this point, the overall JDK 22 feature set is frozen (see the final list of JEPs integrated into JDK 22 below) and only low-risk enhancements might still be considered. The coming weeks should be leveraged to identify and resolve as many issues as possible, i.e. before JDK 22 enters the Release Candidates phase in early February 2024. So, we count on you to test your projects and help us make JDK 22 another solid release! [1] https://mail.openjdk.org/pipermail/jdk-dev/2023-December/008535.html ## JDK 22 Early-Access Builds JDK 22 Early-Access builds 27 are now available [2] with the Release Notes here [3]. Those builds are provided under the GNU GPL v2, with the Classpath Exception. ### JEPs integrated into JDK 22: - JEP 423: Region Pinning for G1 - JEP 447: Statements before super(…) (Preview) - JEP 454: Foreign Function & Memory API - JEP 456: Unnamed Variables & Patterns - JEP 457: Class-File API (Preview) - JEP 458: Launch Multi-File Source-Code Programs - JEP 459: String Templates (2nd Preview) - JEP 460: Vector API (7th Incubator) - JEP 461: Stream Gatherers (Preview) - JEP 462: Structured Concurrency (2nd Preview) - JEP 463: Implicitly Declared Classes and Instance Main Methods (2nd Preview) - JEP 464: Scoped Values (2nd Preview) ### Changes in recent JDK 22 builds that may be of interest: - JDK-8318646: Integer#parseInt("") throws empty NumberFormatException message [Reported by Apache Lucene] - JDK-8318082: ConcurrentModificationException from IndexWriter [Reported by JOOQ] - JDK-8319450: New methods java.net.InetXAddress.ofLiteral() miss @since tag [Reported by JaCoCo] - JDK-8321164: javac w/ annotation processor throws AssertionError: Filling jrt:/… during … [Reported by Hibernate] - JDK-8310644: Make panama memory segment close use async handshakes - JDK-8302233: HSS/LMS: keytool and jarsigner changes - JDK-8211238: New @Deprecated JFR event - JDK-8319124: Update XML Security for Java to 3.0.3 - JDK-8306055: Add a built-in Catalog to JDK XML module - JDK-8319244: implement JVMTI handshakes support for virtual threads - JDK-8319196: ExecutableElement.getReceiverType doesn't return receiver types for methods loaded from bytecode - JDK-8318759: Add four DigiCert root certificates - JDK-8317374: Add Let's Encrypt ISRG Root X2 - JDK-8306116: Update CLDR to Version 44.0 - JDK-8287843: File::getCanonicalFile doesn't work for \\?\C:\</?\C:\> style paths DOS device paths - JDK-8288899: java/util/concurrent/ExecutorService/CloseTest.java failed with "InterruptedException: sleep interrupted" - JDK-8311596: Add separate system properties for TLS server and client for maximum chain length - JDK-8318160: javac does not reject private method reference with type-variable receiver - JDK-8305753: Allow JIT compilation for -Xshare:dump - JDK-8187591: -Werror turns incubator module warning to an error - JDK-8318096: Introduce AsymmetricKey interface with a getParams method - JDK-8319174: Enhance robustness of some j.m.BigInteger constructors - JDK-8288899: Changes to java.util.concurrent.ForkJoinPool and ForkJoinTask - JDK-8272215: Add InetAddress methods for parsing IP address literals - JDK-8316996: Catalog API Enhancement: add a factory method - JDK-8305814: Update Xalan Java to 2.7.3 - JDK-8313643: Update HarfBuzz to 8.2.2 - JDK-8316030: Update Libpng to 1.6.40 Note: A more comprehensive list of changes can be found here [4]. [2] https://jdk.java.net/22/ [3] https://jdk.java.net/22/release-notes [4] https://github.com/openjdk/jdk/compare/jdk-22+20...jdk-22+27 ## JDK 23 Early-Access Builds Given that JDK 22 is in Rampdown Phase, the initial JDK 23 EA builds are now also available [5]. These EA builds are provided under the GNU General Public License v2, with the Classpath Exception. [5] https://jdk.java.net/23/ ## JavaFX 22 Early-Access Builds These are early-access builds of the JavaFX 22 [8] Runtime built from openjdk/jfx [9]. This allows JavaFX application developers to build and test their applications with JavaFX 22 on JDK 22. The JavaFX 22 API Javadocs are also available [10]. The JavaFX runtime is delivered as an SDK and as a set of jmods for each platform. You can use the SDK to compile and run JavaFX applications. You can use the jmods with jlink to create a JDK that includes the JavaFX modules, and optionally, your modular application. JavaFX 22 is designed to work with JDK 22,but it is known to work with JDK 17 and later versions. [8] https://jdk.java.net/javafx22/ [9] https://github.com/openjdk/jfx [10] https://download.java.net/java/early_access/javafx22/docs/api/overview-summary.html ## Topics of Interest: - Java 22 Unpacking - Inside Java Newscast https://inside.java/2023/12/07/newscast-59/ - Java On The GPU - Inside Java Newscast https://inside.java/2023/11/16/newscast-58/ - Better Java Streams with Gatherers - Inside Java Newscast https://inside.java/2023/11/02/newscast-57/ - Another VS Code Extension for Java https://inside.java/2023/12/03/java-vscode-extension/ - Introducing Generational ZGC https://inside.java/2023/11/28/gen-zgc-explainer/ - Improved Emoji Support in Java 21 - Sip of Java https://inside.java/2023/11/20/sip089/ - JDK Tool Access from JShell - Sip of Java https://inside.java/2023/10/23/sip085/ - Optimizing your equals() methods with Pattern Matching - JEP Cafe https://inside.java/2023/11/10/jepcafe21/ - Package a JavaFX Application as a Platform Specific Executable https://inside.java/2023/11/14/package-javafx-native-exec/ - Open sourcing Jipher for FIPS regulated environments https://blogs.oracle.com/developers/post/open-sourcing-jipher - In-memory HttpServer Handler https://inside.java/2023/11/06/in-memory-http-server-handler/ - Java Architects Answer Your Questions https://inside.java/2023/10/26/ama-java-architects/ - Hazelcast Jet on Generational ZGC https://kstefanj.github.io/2023/11/07/hazelcast-on-generational-zgc.html ~ As usual, let us know if you find any quirks while testing your project(s) with the latest JDK early-access builds. And as the year-end is approaching, I'd like to thank you for being part of the OpenJDK Quality Outreach Program. I hope that you will disconnect a bit to spend time with your family and your friends. See you in 2024 with Java 22 and Java 23! |
From: Jython t. <st...@bu...> - 2023-12-08 18:05:32
|
ACTIVITY SUMMARY (2023-12-01 - 2023-12-08) Jython tracker at https://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 346 ( +0) closed 2504 ( +0) total 2850 ( +0) Open issues with patches: 22 Most recent 15 issues with no replies (15) ========================================== #2938: import MessageSource does not work anymore with jython2.7.2 https://bugs.jython.org/issue2938 #2936: can't use SO_EXCLUSIVEADDRUSE in jython2.7.2 https://bugs.jython.org/issue2936 #2934: Filereader.read: TypeError: read(): 1st arg can't be coerced t https://bugs.jython.org/issue2934 #2916: Saving output of script which has korean string to a file https://bugs.jython.org/issue2916 #2898: Fix serialization format https://bugs.jython.org/issue2898 #2886: doing relative imports in a loop causes bad performance due to https://bugs.jython.org/issue2886 #2878: java.lang.OutOfMemoryError: Java heap space https://bugs.jython.org/issue2878 #2876: NullPointer exception PyModule.java https://bugs.jython.org/issue2876 #2874: Jython 2.7 is not able to import an EBCDIC file on z/OS https://bugs.jython.org/issue2874 #2866: Interface default methods disregarded by the method resolver https://bugs.jython.org/issue2866 #2864: Importing second instance of httplib causes an error https://bugs.jython.org/issue2864 #2854: from module import * leads to wild goose chase https://bugs.jython.org/issue2854 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 #1612: array.array should use specialized bulk operations to initiali https://bugs.jython.org/issue1612 #1435: traceback doesn't include Java stack trace in user functions https://bugs.jython.org/issue1435 #1336: PyDeque should likely subclass PySequence https://bugs.jython.org/issue1336 |
From: Jython t. <st...@bu...> - 2023-12-01 18:31:04
|
ACTIVITY SUMMARY (2023-11-24 - 2023-12-01) Jython tracker at https://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 346 ( +0) closed 2504 ( +0) total 2850 ( +0) Open issues with patches: 22 Most recent 15 issues with no replies (15) ========================================== #2938: import MessageSource does not work anymore with jython2.7.2 https://bugs.jython.org/issue2938 #2936: can't use SO_EXCLUSIVEADDRUSE in jython2.7.2 https://bugs.jython.org/issue2936 #2934: Filereader.read: TypeError: read(): 1st arg can't be coerced t https://bugs.jython.org/issue2934 #2916: Saving output of script which has korean string to a file https://bugs.jython.org/issue2916 #2898: Fix serialization format https://bugs.jython.org/issue2898 #2886: doing relative imports in a loop causes bad performance due to https://bugs.jython.org/issue2886 #2878: java.lang.OutOfMemoryError: Java heap space https://bugs.jython.org/issue2878 #2876: NullPointer exception PyModule.java https://bugs.jython.org/issue2876 #2874: Jython 2.7 is not able to import an EBCDIC file on z/OS https://bugs.jython.org/issue2874 #2866: Interface default methods disregarded by the method resolver https://bugs.jython.org/issue2866 #2864: Importing second instance of httplib causes an error https://bugs.jython.org/issue2864 #2854: from module import * leads to wild goose chase https://bugs.jython.org/issue2854 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 #1612: array.array should use specialized bulk operations to initiali https://bugs.jython.org/issue1612 #1435: traceback doesn't include Java stack trace in user functions https://bugs.jython.org/issue1435 #1336: PyDeque should likely subclass PySequence https://bugs.jython.org/issue1336 |
From: Jython t. <st...@bu...> - 2023-11-24 18:15:39
|
ACTIVITY SUMMARY (2023-11-17 - 2023-11-24) Jython tracker at https://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 346 ( +0) closed 2504 ( +0) total 2850 ( +0) Open issues with patches: 22 Most recent 15 issues with no replies (15) ========================================== #2938: import MessageSource does not work anymore with jython2.7.2 https://bugs.jython.org/issue2938 #2936: can't use SO_EXCLUSIVEADDRUSE in jython2.7.2 https://bugs.jython.org/issue2936 #2934: Filereader.read: TypeError: read(): 1st arg can't be coerced t https://bugs.jython.org/issue2934 #2916: Saving output of script which has korean string to a file https://bugs.jython.org/issue2916 #2898: Fix serialization format https://bugs.jython.org/issue2898 #2886: doing relative imports in a loop causes bad performance due to https://bugs.jython.org/issue2886 #2878: java.lang.OutOfMemoryError: Java heap space https://bugs.jython.org/issue2878 #2876: NullPointer exception PyModule.java https://bugs.jython.org/issue2876 #2874: Jython 2.7 is not able to import an EBCDIC file on z/OS https://bugs.jython.org/issue2874 #2866: Interface default methods disregarded by the method resolver https://bugs.jython.org/issue2866 #2864: Importing second instance of httplib causes an error https://bugs.jython.org/issue2864 #2854: from module import * leads to wild goose chase https://bugs.jython.org/issue2854 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 #1612: array.array should use specialized bulk operations to initiali https://bugs.jython.org/issue1612 #1435: traceback doesn't include Java stack trace in user functions https://bugs.jython.org/issue1435 #1336: PyDeque should likely subclass PySequence https://bugs.jython.org/issue1336 |
From: Jeff A. <ja...@fa...> - 2023-11-18 16:45:30
|
On 15/11/2023 18:59, Dhaval Shah wrote: > Recently I have been exploring Python 3. And being a long time Java > developer decided to start contributing to Jython. > > So how do I start contributing to Jython 3? Cool. I'll be in touch off-list, but since you ask these questions here ... > I have gone through https://www.jython.org/jython-3-roadmap and not > sure if this has made progress -> https://github.com/jython/jython3#readme Some. It's still fairly reliable as it goes. > Or is this a dev dump of Jython 3? -> > https://github.com/aaveshdev/jython3 ? I don't know what that is. Jython 3 is hiding in plain sight on the main (not master) branch of the official repo: https://github.com/jython/jython/tree/main . When it works, we'll make "main" the default. At present, it consists of a core interpreter and the unit tests that show the approach taken will probably work. A lot of the code in there is dead Jython 2 code, preserved because I imagine Jython 3 building on it, and I think those who created it deserve to be in the Git history. It's not working out like that so far because the core interpreter is so different. > Or Is Jython3 still sleeping? It wakes, hunts for a bit, then sleeps again. It's mostly just me animating it. Paid work, Jython 2 and other study take turns with Jython 3. > Thanks > Dhaval Thanks for your interest Jeff |
From: Jython t. <st...@bu...> - 2023-11-17 18:05:40
|
ACTIVITY SUMMARY (2023-11-10 - 2023-11-17) Jython tracker at https://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 346 ( +0) closed 2504 ( +0) total 2850 ( +0) Open issues with patches: 22 Most recent 15 issues with no replies (15) ========================================== #2938: import MessageSource does not work anymore with jython2.7.2 https://bugs.jython.org/issue2938 #2936: can't use SO_EXCLUSIVEADDRUSE in jython2.7.2 https://bugs.jython.org/issue2936 #2934: Filereader.read: TypeError: read(): 1st arg can't be coerced t https://bugs.jython.org/issue2934 #2916: Saving output of script which has korean string to a file https://bugs.jython.org/issue2916 #2898: Fix serialization format https://bugs.jython.org/issue2898 #2886: doing relative imports in a loop causes bad performance due to https://bugs.jython.org/issue2886 #2878: java.lang.OutOfMemoryError: Java heap space https://bugs.jython.org/issue2878 #2876: NullPointer exception PyModule.java https://bugs.jython.org/issue2876 #2874: Jython 2.7 is not able to import an EBCDIC file on z/OS https://bugs.jython.org/issue2874 #2866: Interface default methods disregarded by the method resolver https://bugs.jython.org/issue2866 #2864: Importing second instance of httplib causes an error https://bugs.jython.org/issue2864 #2854: from module import * leads to wild goose chase https://bugs.jython.org/issue2854 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 #1612: array.array should use specialized bulk operations to initiali https://bugs.jython.org/issue1612 #1435: traceback doesn't include Java stack trace in user functions https://bugs.jython.org/issue1435 #1336: PyDeque should likely subclass PySequence https://bugs.jython.org/issue1336 |
From: Stefan R. <ste...@gm...> - 2023-11-16 15:33:45
|
Hello Dhaval, thank you for your interest in Jython. In addition to Jython 3 roadmap, recommended reads are https://www.jython.org/jython-3-mvp https://the-very-slow-jython-project.readthedocs.io/en/latest/ As you already noticed, https://github.com/jython/jython3 is *not* the right place - it is a discontinued approach and sandbox. Jython 3 is developed under the main branch (not master) of the usual Jython repo: https://github.com/jython/jython/tree/main So far I did not work with that branch myself but I guess a starting point would be to clone it, build it (gradle), check out current state. Read Jeff Allen's recent commit messages for that branch - they are usually very descriptive. Best Stefan Am Mi., 15. Nov. 2023 um 20:00 Uhr schrieb Dhaval Shah < dha...@gm...>: > I used Jython initially when it came out open (as in funded/in news etc) > sometime between 2005/2006. > > There are several reasons I liked Jython. However things were not > conducive at work to use Jython or in personal space to contribute to > Jython. > > Recently I have been exploring Python 3. And being a long time Java > developer decided to start contributing to Jython. > > So how do I start contributing to Jython 3? > > I have gone through https://www.jython.org/jython-3-roadmap and not sure > if this has made progress -> https://github.com/jython/jython3#readme > > Or is this a dev dump of Jython 3? -> https://github.com/aaveshdev/jython3 > ? > > There are some suggestions to use GraalPy, and I am not comfortable with > either using GraalPy or contributing to it. > > Or Is Jython3 still sleeping? > > Thanks > Dhaval > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Dhaval S. <dha...@gm...> - 2023-11-15 19:00:12
|
I used Jython initially when it came out open (as in funded/in news etc) sometime between 2005/2006. There are several reasons I liked Jython. However things were not conducive at work to use Jython or in personal space to contribute to Jython. Recently I have been exploring Python 3. And being a long time Java developer decided to start contributing to Jython. So how do I start contributing to Jython 3? I have gone through https://www.jython.org/jython-3-roadmap and not sure if this has made progress -> https://github.com/jython/jython3#readme Or is this a dev dump of Jython 3? -> https://github.com/aaveshdev/jython3 ? There are some suggestions to use GraalPy, and I am not comfortable with either using GraalPy or contributing to it. Or Is Jython3 still sleeping? Thanks Dhaval |