You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _data/wg.yaml
+12-7Lines changed: 12 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -48,9 +48,11 @@ working-groups:
48
48
lts: false
49
49
completed: false
50
50
last-activity: 2025-04-25
51
-
last-update-date: 2025-03-13
51
+
last-update-date: 2025-04-28
52
52
last-update: |
53
-
It just started, but already lots of progress.
53
+
In the past month, the WG - Gizmo 2 successfully closed numerous issues, including improvements in error handling, support for instance field initializers, and updates to annotation handling. Key enhancements were made to Lambda singleton implementations and field check validations. Concurrently, several new issues were opened, still addressing challenges in error messaging, generic type handling, and improvements to operational efficiencies. The group remains focused on optimizing the Gizmo 2 framework while ensuring robust functionality and user experience.
54
+
55
+
(This status update was automatically generated using AI.)
54
56
deliverable: TBD
55
57
point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)"
Major update: The PR which switched from 'load classes with the same classloader as JUnit classes' to 'load classes with the classloader which will be used to run them' has merged. This closes ~8 outstanding issues (while potentially creating some more caused by eager augmention).
83
+
In the last month, the WG - Test classloading successfully closed significant issues related to classloader behavior, including fixing ServiceLoader errors and NullPointerExceptions that impacted test discovery. However, several issues were opened, focusing on recurring ServiceConfigurationErrors and additional classloader-related concerns. The team also initiated communications with the first blog detailing test classloading changes. This ongoing work aims to enhance Quarkus's test environment by ensuring proper classloader interactions and minimizing errors during testing.
84
+
85
+
(This status update was automatically generated using AI.)
82
86
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)"
We had several discussions to find the proper architecture/modularization. It will likely require conditional dependencies to avoid pulling AI-related "code" into the regular extension.
291
-
Thus, priorities shifted slightly to focus on "general" action in a first step.
294
+
In the past month, the WG - Chappie focused on enhancing the AI capabilities within Quarkus Dev Mode by successfully closing an issue related to refactoring the Workspace concept for broader usage. No new issues were opened during this period, indicating a focused effort on improving the underlying structure in preparation for future AI feature implementations in the Dev UI and CLI.
295
+
296
+
(This status update was automatically generated using AI.)
292
297
point-of-contact: "@phillip-kruger (@<strong>Phillip Krüger</strong> on Zulip)"
0 commit comments