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>You will very likely find similarities between this diagram and what you do in your projects. It is the OAuth2 authorization code flow is action: the user logs in to the application and authorizes it to access another service offering a poem creation on the user’s behalf.</p>
239
+
<p>You will very likely find similarities between this diagram and what you do in your projects. It is the OAuth2 authorization code flow in action: the user logs in to the application and authorizes it to access another service offering a poem creation on the user’s behalf.</p>
240
240
</div>
241
241
<divclass="paragraph">
242
242
<p>The demo shows that Quarkus MCP Client can work effectively in such architectures by being able to use access tokens acquired during the user login, without you having to write any custom code.</p>
<lastBuildDate>Wed, 21 May 2025 16:03:22 +0000</lastBuildDate>
8
+
<lastBuildDate>Wed, 21 May 2025 18:51:51 +0000</lastBuildDate>
9
9
10
10
11
11
<item>
@@ -60,7 +60,7 @@
60
60
</div>
61
61
</div>
62
62
<div class="paragraph">
63
-
<p>You will very likely find similarities between this diagram and what you do in your projects. It is the OAuth2 authorization code flow is action: the user logs in to the application and authorizes it to access another service offering a poem creation on the user&#8217;s behalf.</p>
63
+
<p>You will very likely find similarities between this diagram and what you do in your projects. It is the OAuth2 authorization code flow in action: the user logs in to the application and authorizes it to access another service offering a poem creation on the user&#8217;s behalf.</p>
64
64
</div>
65
65
<div class="paragraph">
66
66
<p>The demo shows that Quarkus MCP Client can work effectively in such architectures by being able to use access tokens acquired during the user login, without you having to write any custom code.</p>
@Tool(name = "user-name-provider", description = "Provides a name of the currently logged-in user") <i class="conum" data-value="1"></i><b>(1)</b>
<pclass="card-text"><spanclass="key">Description:</span> <spanclass="short-description">This working group will define and implement a consistent and configurable lifecycle model for Dev Services. It will shift the startup to the correct phase, enable optional reuse across dev and test modes, and clarify teardown and sharing behavior. The goal is to improve the developer experience.
208
+
<pclass="card-text"><spanclass="key">Description:</span> <spanclass="short-description">Gizmo 2 related tasks
<pclass="card-text"><spanclass="key">Point of Contact:</span> <spanclass="point-of-contact">@holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )</span>
214
+
<pclass="card-text"><spanclass="key">Point of Contact:</span> <spanclass="point-of-contact">@mkouba (@<strong>Martin Kouba</strong> on Zulip)</span>
215
215
</p>
216
216
217
217
</div>
218
218
<divclass="card-footer">
219
219
<divclass="icons">
220
220
221
-
<ahref="https://github.com/quarkusio/quarkus/discussions/47683" title="See the working group proposal"><i
221
+
<ahref="https://github.com/quarkusio/quarkus/discussions/46627" title="See the working group proposal"><i
<pclass="card-text"><spanclass="key">Description:</span> <spanclass="short-description">The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes.
243
+
<pclass="card-text"><spanclass="key">Description:</span> <spanclass="short-description">This working group will define and implement a consistent and configurable lifecycle model for Dev Services. It will shift the startup to the correct phase, enable optional reuse across dev and test modes, and clarify teardown and sharing behavior. The goal is to improve the developer experience.
<pclass="card-text"><spanclass="key">Point of Contact:</span> <spanclass="point-of-contact">@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)</span>
249
+
<pclass="card-text"><spanclass="key">Point of Contact:</span> <spanclass="point-of-contact">@holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )</span>
250
250
</p>
251
251
252
252
</div>
253
253
<divclass="card-footer">
254
254
<divclass="icons">
255
255
256
-
<ahref="https://github.com/quarkusio/quarkus/discussions/41867" title="See the working group proposal"><i
256
+
<ahref="https://github.com/quarkusio/quarkus/discussions/47683" title="See the working group proposal"><i
<ahref="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/" title="Discuss about the working group"><i
262
+
<ahref="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev" title="Discuss about the working group"><i
263
263
class="icon fa-solid fa-comments"></i></a>
264
264
265
265
</div>
@@ -268,37 +268,33 @@ <h2>Active working groups</h2>
<pclass="card-text"><spanclass="key">Description:</span> <spanclass="short-description">Gizmo 2 related tasks
278
+
<pclass="card-text"><spanclass="key">Description:</span> <spanclass="short-description">The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes.
<pclass="card-text"><spanclass="key">Point of Contact:</span> <spanclass="point-of-contact">@mkouba (@<strong>Martin Kouba</strong> on Zulip)</span>
284
+
<pclass="card-text"><spanclass="key">Point of Contact:</span> <spanclass="point-of-contact">@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)</span>
289
285
</p>
290
286
291
287
</div>
292
288
<divclass="card-footer">
293
289
<divclass="icons">
294
290
295
-
<ahref="https://github.com/quarkusio/quarkus/discussions/46627" title="See the working group proposal"><i
291
+
<ahref="https://github.com/quarkusio/quarkus/discussions/41867" title="See the working group proposal"><i
<ahref="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/Gizmo.202.2Ex.20WG.20chat" title="Discuss about the working group"><i
297
+
<ahref="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/" title="Discuss about the working group"><i
302
298
class="icon fa-solid fa-comments"></i></a>
303
299
304
300
</div>
@@ -307,6 +303,10 @@ <h2>Active working groups</h2>
0 commit comments