Is it possible for our other projects (like Hibernate) to start using
Jandex2 sooner rather than later, w/o banning our users from WildFly
9?
We're in an innovation paradox ;-)
Thanks,
Sanne
On 4 May 2015 at 15:07, Jason T. Greene <jason.greene(a)redhat.com> wrote:
Yes that's correct. We need to make some deployer changes to
prevent holding on to indexes.
Sent from my iPhone
> On May 4, 2015, at 6:25 AM, Jozef Hartinger <jharting(a)redhat.com> wrote:
>
> Congrats on the release!
>
> It seems that Jandex upgrade to 2.0 has not been done yet. Is my understanding
correct that it has been postponed till WF10?
>
>> On 05/01/2015 10:38 PM, Jason Greene wrote:
>> Hello Everyone,
>>
>> I am happy to announce the first candidate release of WildFly 9! WildFly 9 builds
off of WildFly 8’s Java EE7 support, and adds many new capabilities, including intelligent
load balancing, HTTP/2 support, a new offline CLI mode, graceful single node shutdown, and
a new Servlet-only distribution.
>>
>> For more details, check out the release notes:
>>
https://developer.jboss.org/wiki/WildFly900CR1ReleaseNotes
>>
>> As always, you can download it here:
>>
http://wildfly.org/downloads/
>>
>> --
>> 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
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev