June 2026 - wildfly-dev - Jboss List Archives

Possible component upgrades report - elytron-web:4.x

by thofman＠redhat.com

3 hours, 35 minutes

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:2.x

by thofman＠redhat.com

6 hours, 38 minutes

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

22 hours, 29 minutes

1
0
0 / 0

A maven plugin project for misc utilities?

by Brian Stansberry

I want to create a trivial maven plugin with a mojo that does just one small function. I could create a repo just for that, with a repo name and artifactId to match. Or I could give it a more generic name / artifactId and if we need other things like my mojo we could just add them. WDYT? In general I don't like grab-bag projects and I'd oppose adding anything complex or likely at all to need much maintenance into any shared project. We used to have the licenses plugin mixed in a project with something else, and we're better off with it in its own project. But my thing will likely be maybe 10 lines of non-boilerplate code. It's that kind of thing I'm thinking about. Writing this, I'm convincing myself I should start with a single-purpose thing and if there's every a concrete use case for some other similar thing we can fork it and create a new repo. -- Brian Stansberry Collaborative Partner - IBM Architect, JBoss EAP WildFly Project Lead He/Him/His

2 days, 21 hours

2
1
0 / 0

Promote MCP server features to default stability level

by Jean-Frederic Mesnil

Hi, I’ve created a new issue to promote MCP server features to default stability level[1]. The intent is to make WildFly a MCP server where users could integrate their applications as MCP server resources (tools, resources) and open them to AI ecosystem. The scope is narrow and focuses only on MCP server features. The code has been in development for quite some time and we are in the process of implementing the latest MCP server specification. As part of this promotion, we need to iron out the code, fill gaps in the testing, provide documentation, etc. as described in our feature process document[2]. Only features and packages of the WildFly AI feature pack that provides MCP server capabilities are planned to move to default stability level. There are many other capabilities (including MCP client, LLM, WASM) provided by the feature pack that will remain at the experimental level. Best regards, Jeff [1] https://github.com/wildfly/wildfly-proposals/issues/829 [2] https://docs.wildfly.org/wildfly-proposals/FEATURE_PROCESS.html -- Jeff Mesnil Software Engineer Red Hat JBoss EAP http://jmesnil.net/ IBM Unless otherwise stated above: Compagnie IBM France Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex RCS Nanterre 552 118 465 Forme Sociale : S.A.S. Capital Social : 664 614 175,50 € SIRET : 552 118 465 03644 - Code NAF 6203Z

3 days, 8 hours

2
5
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

4 days, 3 hours

1
0
0 / 0

Discussion on sharing Claude skills

by jdenise＠redhat.com

5 days, 6 hours

2
2
0 / 0

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

6 days, 7 hours

1
0
0 / 0

Possible component upgrades report - elytron-web:4.x

by thofman＠redhat.com

1 week

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:2.x

by thofman＠redhat.com

1 week

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev June 2026