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(a)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(a)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(a)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(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)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