OK, after some digging around: the archetypes are generated based on the
"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...

Wolfgang



Am 19.02.19 um 22:12 schrieb Wolfgang Knauf:
> Hi,
>
> 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
> think?
>
> 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
>
> Wolfgang
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev