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
<p>This _working group aims to make the <a href="https://github.com/dmlloyd/gizmo/tree/gizmo2">Gizmo 2 POC</a> production-ready and integrate it into Quarkus core.</p>
9
-
<ul>
10
-
<li>Point of contact: @mkouba (@<strong>Martin Kouba</strong> on Zulip)</li>
In the past month, the WG - Gizmo 2 closed two important issues, focusing on refining default flags for classes and members, as well as addressing API limitations regarding method body construction within the Gizmo framework. No new issues were opened during this period, suggesting a careful consolidation of existing features and ongoing focus on enhancing the Gizmo 2 functionality.
22
-
23
-
(This status update was automatically generated using AI.)
24
-
25
-
**NOTE:** The Gizmo API is almost finalized. A Beta 2 has been released, and tests to use Gizmo 2 in Arc have been started.
26
-
deliverable: TBD
27
-
point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)"
In the last month, the WG - Test classloading successfully resolved multiple issues, including improvements to test executions in Quarkus 3.22, addressing classloader errors, and ensuring compatibility with various IDEs. However, several new issues were opened, focusing on logging behavior during tests, test ordering in multi-profile scenarios, and heap consumption changes in the transition to Quarkus 3.23. These discussions indicate ongoing efforts to refine the testing framework and enhance overall functionality.
@@ -56,6 +29,33 @@ working-groups:
56
29
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)"
<p>This _working group aims to make the <a href="https://github.com/dmlloyd/gizmo/tree/gizmo2">Gizmo 2 POC</a> production-ready and integrate it into Quarkus core.</p>
38
+
<ul>
39
+
<li>Point of contact: @mkouba (@<strong>Martin Kouba</strong> on Zulip)</li>
In the past month, the WG - Gizmo 2 closed two important issues, focusing on refining default flags for classes and members, as well as addressing API limitations regarding method body construction within the Gizmo framework. No new issues were opened during this period, suggesting a careful consolidation of existing features and ongoing focus on enhancing the Gizmo 2 functionality.
51
+
52
+
(This status update was automatically generated using AI.)
53
+
54
+
**NOTE:** The Gizmo API is almost finalized. A Beta 2 has been released, and tests to use Gizmo 2 in Arc have been started.
55
+
deliverable: TBD
56
+
point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)"
0 commit comments