[wildfly-dev] Wildfly Quickstarts

[Pete Muir]

Sorry, what I am saying is that all of them should work (as Eduardo has mostly done now, AIUI), but that we shouldn’t update them to show new Java EE 7 concepts. They remain showing the Java EE 6 programming model. New ones are built to show off the EE7 programming model.

On 5 Feb 2014, at 20:21, Jason Greene <jason.greene at redhat.com> wrote:

> Thats fine to drop a bunch of these, but IMO a great deal of them are still valid, helloworld, hibernate, all of the EJB & CDI ones for example (especially remote EJB and security). We are very close to releasing final which is why I was suggesting the priority is to just get what we have updated and tested, and drop stuff thats not relevant or not worth fixing.
> 
> On Feb 5, 2014, at 3:08 AM, Pete Muir <pmuir at redhat.com> wrote:
> 
>> It would be much better to add new ones to show of Java EE 7 IMO. This allows us a much clearer separation. Also some of “common” ones are now getting a bit old. I can work with Eduardo to establish 5-10 new EE7 quickstarts to specifically show off new concepts.
>> 
>> WDYT?
>> 
>> On 31 Jan 2014, at 20:48, Jason Greene <jason.greene at redhat.com> wrote:
>> 
>>> They will likely evolve outside of the fork we created which is fine. I think our priority should be ensuring these are ported and run as is. Then after that I would suggest just updating the most common ones to use EE7 APIs.
>>> 
>>> 
>>> On Jan 29, 2014, at 8:31 AM, Eduardo Martins <emartins at redhat.com> wrote:
>>> 
>>>> Those are the ones I’m working with, but afaik the JDF EAP ones are the same.
>>>> 
>>>> —E
>>>> 
>>>> On 28 Jan 2014, at 22:38, Tomaž Cerar <tomaz.cerar at gmail.com> wrote:
>>>> 
>>>>> Aren't we updating quick starts here https://github.com/wildfly/quickstart ?
>>>>> I thought that jdf ones ware mostly for EAP...
>>>>> 
>>>>> --
>>>>> tomaz
>>>>> 
>>>>> 
>>>>> On Tue, Jan 28, 2014 at 2:06 PM, Eduardo Martins <emartins at redhat.com> wrote:
>>>>> I have been updating Wildfly Quickstarts, for now mostly reworking Maven POMs to use the updated dependencies, but it’s a long way to go, there are a lot of quickstarts, and no way all of these will be ready for primetime when WFLY 8 is out. So I was thinking in changing my strategy, and define a list with quickstarts of highest priority to be ready very soon.
>>>>> 
>>>>> The quickstarts list can be seen at http://www.jboss.org/jdf/quickstarts/get-started/
>>>>> 
>>>>> May a person related to each Java EE spec/technology go through that list and help my build the priority list? My guess is that first priority is to have the ones that show off Java EE and Wildfly 8 features only, leaving the ones that show integration with other JBoss projects for a second release, but still this will be a big list so I definitely need help.
>>>>> 
>>>>> Also, we will need new Batch quickstart(s).
>>>>> 
>>>>> Thanks in advance.
>>>>> 
>>>>> —E
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> wildfly-dev mailing list
>>>>> wildfly-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>> 
>>>> 
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> wildfly-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> 
>>> --
>>> Jason T. Greene
>>> WildFly Lead / JBoss EAP Platform Architect
>>> JBoss, a division of Red Hat
>>> 
>>> 
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> 
> 
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>