Use of the 'org.wildfly' groupId
by Brian Stansberry
Currently we have a number of different repos publishing artifacts using
the 'org.wildfly' groupId with no further namespacing.
Going forward I don't think we should allow any other new repos to do that.
It leads to administrative hassles, e.g. with setting things up in Nexus.
Best regards,
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
3 weeks, 1 day
Moving WildFly Elytron to Java 17
by Darran Lofthouse
Now that WildFly Core is built for Java 17 I would like to move WildFly
Elytron to Java 17 as well from our next releases for WildFly (2.7.x +).
Would this cause any issues for other projects that depend on WildFly
Elytron?
It should not affect Undertow as we use the Elytron Web project for
integration, maybe JBoss Remoting but also others with an Elytron
dependency so let me know if this would be an issue for your project.
--
Darran Lofthouse
Red Hat <https://www.redhat.com/>
darran.lofthouse(a)jboss.com
<https://www.redhat.com/>
3 months, 3 weeks
[proposal] Generate "javadoc-like" documentation for feature packs
by Jeff Mesnil
Hi,
I’ve created a proposal[1] to generate a documentation archive when a feature pack is created (similar to the javadoc archive that is generated when a Java jar is built by Maven)
I’m looking for a feature team to work on this proposal.
Jean-Francois and Emmanuel already provided some PoC around this idea so I nominated you as SMEs :)
But I’d need another outside perspective to fully form the team.
This RFE does not impact the runtime so stability level is not directly applicable but I aim to do something equivalent to the quality expected by the “community” stability level.
Best regards,
Jeff
[1] https://github.com/wildfly/wildfly-proposals/pull/739
--
Jeff Mesnil
Engineer @ Red Hat
http://jmesnil.net/
5 months
WildFly 38 schedule
by Brian Stansberry
Following are the planned dates for the WildFly 38 Beta and Final releases.
Please note that these are a week later than we'd originally discussed.
WildFly 38 Beta
PRs due -- Wed Sep 24
Tag and deploy -- Wed Oct 1
Publish release -- Thu Oct 2
WildFly 38 Final
PRs due -- Wed Oct 8
Tag and deploy -- Wed Oct 15
Publish release -- Thu Oct 16
Note that the PR deadline for things going into 38 Beta via WildFly Core
will be particularly strictly enforced this time, as the team producing the
Beta needs to get things done quickly.
As I mentioned before these are a week later than we initially thought.
Adapting project to the new JBoss Nexus environment, plus plenty of well
deserved vacation time for many, meant the original schedule was too tight,
so we'd rather better serve our users by taking a bit more time.
Best regards,
--
Brian Stansberry
WildFly Project Lead
He/Him/His
5 months, 1 week
Agenda for the upcoming WildFly community call
by Jean-Frederic Mesnil
Hi,
Next Thursday, we have our 2nd WildFly community call and I’m looking for topics.
I’ve started to fill the agenda at https://docs.google.com/document/d/1kjaMGFGtL3MPY58UCJMojLlTzl335DUm1L-P9...
As it coincides with the release of WildFly 38 Beta, it’d be a great opportunity to showcase new features coming to WildFly.
If you have a feature that lands in WildFly 38, can I ask you to add an item in the agenda. You can also present/demo it :)
More generally, I’m looking for topics for future meetings. This meeting is an opportunity to reach out to our users and present what we are doing and what is in our pipeline.
Don’t hesitate to add future topics to the “Meeting Suggestions” tab[1]
[1] https://docs.google.com/document/d/1kjaMGFGtL3MPY58UCJMojLlTzl335DUm1L-P9...
--
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
5 months, 1 week
