On Wed, Feb 20, 2019 at 3:45 PM Wolfgang Knauf <wolfgang.knauf(a)gmx.de>
OK, after some digging around: the archetypes are generated based on
"Kitchensink" quickstart. So, actually there should be not much changes
to the archetype files itself, just a "rebuild". But currently, a "maven
install" for the archetype fails for me. More research needed...
Oops; I missed this post and responded to your first one! Thanks for
Am 19.02.19 um 22:12 schrieb Wolfgang Knauf:
> 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 ;-).
> Best regards
> wildfly-dev mailing list
wildfly-dev mailing list
Manager, Senior Principal Software Engineer