Release date for Jboss EAP 6.4.0 GA

[clatasa]

Hi - we're trying to figure out if we need to write a lot of code as opposed to leveraging the Java 8 lambda expressions.

I know there's been talk of somewhere toward the end of Q1 2015 but would really appreciate something more definitive.

Thanks!

[ctomc]

If problem is just weather you should use Java 8 features or not, you should just go with it.

As EAP 6.3.x works fine with Java 8, you also have EAP 6.4 beta already available and you can do your development on it.

and when .GA is out you can just move to that.

[clatasa]

Hey Tom - thanks for the response!

We did just as your suggesting but got a little scared with the following warning we saw:

18:36:17,431 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015852: Could not index class com/prosper/document/ws/impl/DownloadCSVEndpointImpl.class at /C:/java/jboss-eap-6.3/standalone/deployments/core-document.war/WEB-INF/classes: java.lang.IllegalStateException: Unknown tag! pos=32 poolCount = 155

       at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:606) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2]

       at org.jboss.jandex.Indexer.index(Indexer.java:640) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2]

       at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:100) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

       at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

       at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

       at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]

       at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]

       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]

       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]

       at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]

[ctomc]

Can you share simple reproducer for this?

I think fix should be as simple as upgrading jandex library version.

any chance you could try downloading https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/jandex/1.2.3.Final/jandex-1.2.3.…

and putting it into JBOSS_HOME\modules\system\layers\base\org\jboss\jandex\main

and then update reference to the new file in module.xml

* edited to update link to 1.2.3 jandex instead of 2.x series

[ctomc]

also this should be fixed in 6.4 series, can you try with 6.4.Beta that you can get from http://www.jboss.org/products/eap/download/

[blackbeltdev]

Is there a release date set yet? I don't see any issues being tracked for awhile now -- unless I am looking in the wrong place .

[jaikiran]

Kirk Rasmussen wrote:

Is there a release date set yet?

See this discussion https://developer.jboss.org/thread/253611

[blackbeltdev]

Thanks!