<div dir="ltr"><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">Excellent!</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">Thanks, Wolfgang and Eduardo!</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">Best regards,</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">Brian</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 14, 2019 at 2:29 PM Eduardo Martins <<a href="mailto:emartins@redhat.com">emartins@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Good news Wolfgang, I just released WildFly Archetypes 18.0.0.Final! <br>
<br>
Besides merging your PR I did a couple major changes:<br>
<br>
1. Cleaned up the repo of the old archetypes and setup a maven project aggregator [1] <br>
2. Moved all to WildFly 18.0.0.Final and… Jakarta EE! [2]<br>
<br>
All archetypes were deployed too, just try it out on your command line right now...<br>
<br>
$ mvn archetype:generate -DgroupId=<a href="http://my.project.org" rel="noreferrer" target="_blank">my.project.org</a> -DartifactId=sampleproject -Dversion=1.0-SNAPSHOT -DarchetypeGroupId=org.wildfly.archetype -DarchetypeArtifactId=wildfly-jakartaee-ear-archetype -DarchetypeVersion=18.0.0.Final<br>
<br>
or…<br>
<br>
$ mvn archetype:generate -DgroupId=<a href="http://my.project.org" rel="noreferrer" target="_blank">my.project.org</a> -DartifactId=sampleproject -Dversion=1.0-SNAPSHOT -DarchetypeGroupId=org.wildfly.archetype -DarchetypeArtifactId=wildfly-jakartaee-webapp-archetype -DarchetypeVersion=18.0.0.Final<br>
<br>
Feel free to have a look at the master branch now, it’s already set for WFLY 19 development, even if honestly I dunno yet how we going to maintain this project, but will certainly let you know once we have that figured out.<br>
<br>
So… huge huge thank you, for your contributions, and also for your patience :-) <br>
<br>
Best regards.<br>
<br>
—E<br>
<br>
[1] <a href="https://github.com/wildfly/wildfly-archetypes/commit/c960f01cf8d5ab3d115b7278859aa07ede449d65" rel="noreferrer" target="_blank">https://github.com/wildfly/wildfly-archetypes/commit/c960f01cf8d5ab3d115b7278859aa07ede449d65</a><br>
[2] <a href="https://github.com/wildfly/wildfly-archetypes/commit/8dc0e2fbacb51142b024c3de2b0560cc523f5ff8" rel="noreferrer" target="_blank">https://github.com/wildfly/wildfly-archetypes/commit/8dc0e2fbacb51142b024c3de2b0560cc523f5ff8</a><br>
<br>
> On 16 Sep 2019, at 09:25, Eduardo Martins <<a href="mailto:emartins@redhat.com" target="_blank">emartins@redhat.com</a>> wrote:<br>
> <br>
> Hi Wolfgang, fyi just got back from some time off, and should be able to look at this next week.<br>
> <br>
> —E<br>
> <br>
>> On 11 Sep 2019, at 20:18, Wolfgang Knauf <<a href="mailto:wolfgang.knauf@gmx.de" target="_blank">wolfgang.knauf@gmx.de</a>> wrote:<br>
>> <br>
>> Hi Eduardo,<br>
>> <br>
>> once again a reminder for<br>
>> <a href="https://github.com/wildfly/wildfly-archetypes/pull/5" rel="noreferrer" target="_blank">https://github.com/wildfly/wildfly-archetypes/pull/5</a> ;-).<br>
>> I updated the two archetypes to use WildFly 17.0.Final.<br>
>> <br>
>> Best regards<br>
>> <br>
>> Wolfgang<br>
>> <br>
>> Am 07.08.19 um 22:35 schrieb Wolfgang Knauf:<br>
>>> Hi Eduardo,<br>
>>> <br>
>>> wanted to ask for an update on this pull request.<br>
>>> <br>
>>> It is already outdated, as WildFly 17 is now final and all versions in<br>
>>> pom.xml should be updated...<br>
>>> <br>
>>> Best regards<br>
>>> <br>
>>> Wolfgang<br>
>>> <br>
>>> Am 16.06.19 um 14:12 schrieb Wolfgang Knauf:<br>
>>>> Hi Eduardo,<br>
>>>> <br>
>>>> i sent a pull request for this new archetype, without beans.xml.<br>
>>>> Depending on your findings, we can add it afterwards if necessary.<br>
>>>> <br>
>>>> But as far as I understand it, this file is optional now<br>
>>>> (<a href="https://blogs.oracle.com/theaquarium/default-cdi-enablement-in-java-ee-7" rel="noreferrer" target="_blank">https://blogs.oracle.com/theaquarium/default-cdi-enablement-in-java-ee-7</a>)<br>
>>>> - so this could be considered a bug...<br>
>>>> <br>
>>>> Best regards<br>
>>>> <br>
>>>> Wolfgang<br>
>>>> <br>
>>>> <br>
>>>> Am 12.06.19 um 22:37 schrieb Eduardo Martins:<br>
>>>>> Hi Wolfgang, when reviewing it seemed to me that in the *ear*<br>
>>>>> archetype the beans.xml was not needed. I can’t tell if that’s the<br>
>>>>> case for this new archetype without you submitting it for review, but<br>
>>>>> if it fails to deploy without it… ;-)<br>
>>>>> <br>
>>>>> —E<br>
>>>>> <br>
>>>>>> On 12 Jun 2019, at 20:57, Wolfgang Knauf <<a href="mailto:wolfgang.knauf@gmx.de" target="_blank">wolfgang.knauf@gmx.de</a>> wrote:<br>
>>>>>> <br>
>>>>>> Hi to all,<br>
>>>>>> <br>
>>>>>> just wanted to ask for an update: do you think that the error<br>
>>>>>> message is<br>
>>>>>> acceptable and I should create the archetype without "beans.xml" anyway<br>
>>>>>> (and add an info to the readme.txt file)?<br>
>>>>>> Or should I add a default "beans.xml" to the archetype to avoid it?<br>
>>>>>> Or is it worth a JIRA?<br>
>>>>>> <br>
>>>>>> Best regards<br>
>>>>>> <br>
>>>>>> Wolfgang<br>
>>>>>> <br>
>>>>>> Am 05.06.19 um 21:42 schrieb Wolfgang Knauf:<br>
>>>>>>> Hi Eduardo,<br>
>>>>>>> <br>
>>>>>>> while building a "wildfly-javaee-webapp-archetype", I think I found a<br>
>>>>>>> small WildFly issue: you remember that you pointed me to the fact that<br>
>>>>>>> "beans.xml" is optional?<br>
>>>>>>> But when creating a blank project from my new web archetype (which<br>
>>>>>>> defines a "faces-config.xml", but no "beans.xml"), the attached<br>
>>>>>>> error is<br>
>>>>>>> in the WildFly console. But it seems the app is deployed anyway.<br>
>>>>>>> <br>
>>>>>>> The error disappears if I add e.g. an annotated EJB, or if I add a<br>
>>>>>>> "beans.xml".<br>
>>>>>>> <br>
>>>>>>> Do you think this is a WildFly bug? Or should I add a default<br>
>>>>>>> "beans.xml" just to avoid this error?<br>
>>>>>>> <br>
>>>>>>> I did not test it with a blank project from the EAR archetype -<br>
>>>>>>> will do<br>
>>>>>>> this in the next few days.<br>
>>>>>>> <br>
>>>>>>> Best regards<br>
>>>>>>> <br>
>>>>>>> Wolfgang<br>
>>>>>>> <br>
>>>>>>> <br>
>>>>>>> Am 03.06.19 um 21:36 schrieb Wolfgang Knauf:<br>
>>>>>>>> Thanks for the deploy, Eduardo!<br>
>>>>>>>> <br>
>>>>>>>> If you consider it reasonable I will create an archetype for "web app<br>
>>>>>>>> only", similar to the old "wildfly-javaee7-webapp-archetype".<br>
>>>>>>>> But I will probably need a few weeks...<br>
>>>>>>>> <br>
>>>>>>>> What happens to the old archetype<br>
>>>>>>>> "wildfly-javaee7-webapp-ear-archetype"? It could be deleted, as it<br>
>>>>>>>> does not build anyway. It might be relevant only for research.<br>
>>>>>>>> <br>
>>>>>>>> Best regards<br>
>>>>>>>> <br>
>>>>>>>> Wolfgang<br>
>>>>>>>> <br>
>>>>>>>> <br>
>>>>>>>> <br>
>>>>>>>> Am 03.06.19 um 17:05 schrieb Brian Stansberry:<br>
>>>>>>>>> Excellent! Thank you so much Wolfgang!<br>
>>>>>>>>> <br>
>>>>>>>>> On Mon, Jun 3, 2019 at 9:52 AM Eduardo Martins <<a href="mailto:emartins@redhat.com" target="_blank">emartins@redhat.com</a><br>
>>>>>>>>> <mailto:<a href="mailto:emartins@redhat.com" target="_blank">emartins@redhat.com</a>>> wrote:<br>
>>>>>>>>> <br>
>>>>>>>>> Wolfgang: yours and mine PRs are merged, and when WFLY 17<br>
>>>>>>>>> Final is<br>
>>>>>>>>> out I will also deploy the archetype, thanks a lot for your<br>
>>>>>>>>> contribution! Yet now I have to ask, do you plan to submit<br>
>>>>>>>>> similar<br>
>>>>>>>>> for the other old javaee archetype? :-)<br>
>>>>>>>>> <br>
>>>>>>>>> Brian: yep it was just the JDK, I will deploy these too (no<br>
>>>>>>>>> planned<br>
>>>>>>>>> updates in such code tho)<br>
>>>>>>>>> <br>
>>>>>>>>> —E<br>
>>>>>>>>> <br>
>>>>>>>>>> On 16 May 2019, at 10:09, Eduardo Martins <<a href="mailto:emartins@redhat.com" target="_blank">emartins@redhat.com</a><br>
>>>>>>>>>> <mailto:<a href="mailto:emartins@redhat.com" target="_blank">emartins@redhat.com</a>>> wrote:<br>
>>>>>>>>>> <br>
>>>>>>>>>> Hmm ok, maybe it just failed build due to some specific<br>
>>>>>>>>>> like JDK<br>
>>>>>>>>>> 11, will recheck that.<br>
>>>>>>>>>> <br>
>>>>>>>>>> —E<br>
>>>>>>>>>> <br>
>>>>>>>>>>> On 16 May 2019, at 02:25, Brian Stansberry<br>
>>>>>>>>>>> <<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a><br>
>>>>>>>>>>> <mailto:<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a>>> wrote:<br>
>>>>>>>>>>> <br>
>>>>>>>>>>> These build for me.<br>
>>>>>>>>>>> <br>
>>>>>>>>>>> They're not as out of date as I'd thought either.<br>
>>>>>>>>>>> <br>
>>>>>>>>>>> On Fri, May 10, 2019 at 6:34 PM Eduardo Martins<br>
>>>>>>>>>>> <<a href="mailto:emartins@redhat.com" target="_blank">emartins@redhat.com</a> <mailto:<a href="mailto:emartins@redhat.com" target="_blank">emartins@redhat.com</a>>> wrote:<br>
>>>>>>>>>>> <br>
>>>>>>>>>>> If you think it’s not a small effort task then certainly<br>
>>>>>>>>>>> agree that’s not a blocker, I look at the archetypes<br>
>>>>>>>>>>> same way<br>
>>>>>>>>>>> as the quickstarts, an aggregation project, so we may<br>
>>>>>>>>>>> take<br>
>>>>>>>>>>> outdated/faulty ones out of build and release the<br>
>>>>>>>>>>> working+actual ones. We may give it a thought later if it<br>
>>>>>>>>>>> makes sense effort wise to update or drop the<br>
>>>>>>>>>>> subsystem ones,<br>
>>>>>>>>>>> no worries.<br>
>>>>>>>>>>> <br>
>>>>>>>>>>> —E<br>
>>>>>>>>>>> <br>
>>>>> <br>
>>>>> <br>
> <br>
<br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Brian Stansberry<div>Manager, Senior Principal Software Engineer</div><div>Red Hat</div></div></div>