Re: [wildfly-dev] Alpha1 RELEASE DELAY (Hopefully tomorrow)
It's on my list I will double check that it works. We actually left the native port on
for this reason. For Beta I would like to switch to using an http upgrade config if we can
coordinate that with you.
On May 16, 2013, at 12:39 PM, Max Andersen <manderse(a)redhat.com> wrote:
Just to check - have you had time to test in JBoss tools if it still
works as an 7.1 server ?
Or can point to a binary build I can try it on?
/max (sent from my phone)
On 16/05/2013, at 19.31, Jason Greene <jason.greene(a)redhat.com> wrote:
> Hello Everyone,
>
> While we are very close to releasing, we found some problems after updating the quick
starts to be compatible with the release.
>
> (e.g.)
> https://issues.jboss.org/browse/WFLY-1355
> https://issues.jboss.org/browse/WFLY-1356
>
> While it's just an alpha release, we want to make sure that its still easy to
experiment with, and broken quick starts make that a much harder thing to achieve.
>
> I apologize for the delay, and I am hopeful we will be able tag tomorrow. However, we
might need a component update (e.g. Weld), and if that happens it could push the release
over the weekend.
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> 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