the archetypes at https://github.com/wildfly/wildfly-archetypes
(e.g. "wildfly-javaee7-webapp-ear-blank-archetype") are for WildFly 8,
and when updating the WildFly version in pom.xmls, a lot of further
changes is required, see https://issues.jboss.org/browse/WFLY-9703
(which is only part of the changes).
I am interested in creating new archetypes for WildFly 15. What do you
My plan is to name them e.g.
"wildfly15-javaee8-webapp-ear-blank-archetype" and to create a new
archetype version each time a new WildFly major version is released.
If you are OK with this, I will struggle with my first steps in Git, and
I probably will ask some more or less dumb questions about details ;-).
The following is very much work in progress and I expect it to evolve
greatly based on discussions and the practicality of implementing this
feature - however here are my initial thoughts in relation to adding
support for management model expression resolution backed by a credential
As I mention in the analysis we are actually missing documentation for the
credential store anyway so I will add that first under
https://issues.jboss.org/browse/WFLY-11101 before progressing to the next
stages of this feature.
Just an FYI that work has begun on producing the WildFly 17.0.0.Final
release. We're on track to publish the release to maven and
https://wildfly.org/downloads on Monday.
Earlier today James Perkins pushed the 17.0.0.Final tag to github, and the
master branch pom versions have moved on to 18.0.0.Beta1-SNAPSHOT. But
other aspects of the release, i.e. publishing the binaries and the final
boms and quickstarts will be completed Monday. So if you see the tag and
wonder what's up, that's what's up. ;) Doing all the bits of a release
usually takes more than a working day. This time it stretches over a
weekend so it's a bit more noticeable.