I have a PR open (https://github.com/wildfly/wildfly-core/pull/4636) that
hides properties that were long ago marked as deprecated. To be clear, the
properties themselves are not deprecated, but direct access has been. There
are getters and (where appropriate) setters that should be used instead.
Most of WildFly full has already been updated to use the methods for
accessing the properties (with a few stragglers addressed at
https://github.com/wildfly/wildfly/pull/14378). If you have a subsystem not
in the wildfly repo or any project that depends on WildFly Core that uses
AbstractAttributeDefinitionBuilder or any of its children, it would be
prudent to verify your usage to ensure you are not using the now-hidden
If you have questions or concerns, please comment on the PR.
Principal Software Engineer
Red Hat JBoss EAP
I propose we not produce an equivalent to
https://docs.wildfly.org/23/JavaEE_Tutorial.html for WF 24. So basically we
drop the relevant adoc pages from the WildFly docs maven module.
It's titled as being about Java EE 7, but WF 24 will be a Jakarta EE 8
server. A big chunk of what's in there is TODOs. We could retitle the doc,
but I'm not sure if what's there is up to date.
I've heard some discussions of how we should revamp our developer guides,
and I agree. I think a good first step is drop this one and start over. It
has some REST and webservices content that might still be useful; if so it
can be ported into a new document.
Step 3 throws an error for me:
jboss@sb2000:/home/jboss/WildFly-Core-master/wildfly-core git branch -m
jboss@sb2000:/home/jboss/WildFly-Core-master/wildfly-core git fetch origin
remote: Enumerating objects: 326, done.
remote: Counting objects: 100% (326/326), done.
remote: Compressing objects: 100% (189/189), done.
remote: Total 326 (delta 168), reused 286 (delta 131), pack-reused 0
Receiving objects: 100% (326/326), 64.65 KiB | 23.00 KiB/s, done.
Resolving deltas: 100% (168/168), completed with 41 local objects.
* [new branch] 15.x -> origin/15.x
jboss@sb2000:/home/jboss/WildFly-Core-master/wildfly-core git branch -u
error: the requested upstream branch 'origin/main' does not exist
hint: If you are planning on basing your work on an upstream
hint: branch that already exists at the remote, you may need to
hint: run "git fetch" to retrieve it.
hint: If you are planning to push out a new local branch that
hint: will track its remote counterpart, you may want to use
hint: "git push -u" to set the upstream config as you push.
jboss@sb2000:/home/jboss/WildFly-Core-master/wildfly-core git status
On branch main
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
no changes added to commit (use "git add" and/or "git commit -a")
Am 15.06.2021 um 09:44 schrieb Jean-Frederic Mesnil:
> The renaming of “master" to “main” branch for wildfly-core is over.
> If you go to https://github.com/wildfly/wildfly-core, you should have
> a notification to update your local environment. This includes running
> the following commands:
> git branch -m master main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
> If you have opened PR against wildfly/wildfly-core, you have nothing
> to do, the change is automatic.
> The CI has been updated and I verified the PR jobs runs fine (from
> I tried to do a thorough change in all the WildFly Core jobs on
> https://ci.wildfly.org/project/WildFlyCore?mode=builds and most of the
> jobs are fine too.
> Best regards,
> Jeff Mesnil
> Principal Software Engineer
> Red Hat
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
We have now released WildFly Core 16.0.0.Final for the upcoming release of WildFly 24 and will start development of WildFly Core 17.
We’ll take the opportunity to be early in the development cycle to change the default branch for wildfly/wildfly-core project from “master" to “main".
GitHub has some instructions that should help with the move: https://github.com/github/renaming. It should work transparently at the project level and each contributor will just need to update their local environment.
We also need to update all the CI scripts we are using to test WildFly Core.
Once the switch is done, I’ll send another mail to inform each contributor with the steps to update their local environment.
Principal Software Engineer
Previously we have worked to eliminate all mandatory module dependencies on
the org.jboss.as.security module - this means that this module is not only
provisioned by Galleon if we are provisioning a layer which includes the
The next target we need to tackle is the org.picketbox module, this step
will involve some work within each of the affected components. We need to
reach the point that all other module dependencies on this one are also
optional so it is only provisioned when the legacy security subsystem is
At the top level this is being tracked under:
For the individual subsystems I have split out a set of tasks so they can
be tackled individually:
- Messaging - https://issues.redhat.com/browse/WFLY-14752
- IIOP - https://issues.redhat.com/browse/WFLY-13679
- Web Services - https://issues.redhat.com/browse/WFLY-14841
- JCA - https://issues.redhat.com/browse/WFLY-14842
- EJB3 - https://issues.redhat.com/browse/WFLY-14843
- Application Client - https://issues.redhat.com/browse/WFLY-14844
- security-api / security-integration -
I have left these unassigned by default so we can see when they have been
Some of these may be more complicated than others so the most urgent task
is to identify where we think we are going to run into problems so we can
define a solution.
Some solutions could include:
- Moving utility code to WildFly Elytron or some other common project.
- Forking utility code to a private implementation in the project that
- For anything affecting deployments using capabilities to check if legacy
security is present.
- Any optional use of legacy security should be disabled from Java 13 and
- Other solutions to be developed.
This specific task is not about changing the default configuration to move
on from legacy security. Once this step is complete we will be ready to
start adjusting the default configuration to eliminate legacy security.