Arquillian 1.2 and Java version

[lordofthejars]

Probably Arquillan 1.2 will contain the code for Suite tests in Arquillian. I was thinking that if we could use the same big update to change the minimum version of Java from 5 to 7? I said this because if we upgrade to Java 7 we will be able to use java.util.concurrent package. This will be very helpful to implement parallel execution of incontainer tests.

WDYT?

[aslak]

Yea, that could be a good time to do that.

We just need to map out which Container Adapters we will ‘deprecate/unsupport’ moving forward as I’m sure there are some of the ones we currently have that require Java 5/6.

[lordofthejars]

Ok I am going to do this and give you the results here, and then decide what to do.

[bartoszmajsak]

Honestly, I would even opt for JDK 8

[miklosovic]

This would be awesome and it could help me with this issue tremendously

How to make Arquillian eventing thread safe?

As probably some of you know, mainly Aslak and Alex, I was extracting that Arquillian Cube runtime into Arquillian-less solution so I can manage lifecycle of containers manually by firing respective management events. The thing is that, when you look at it realistically, you can start containers which do not depend on any other container in parallel. Right now I am doing it sequentially hence I could potentially save some startup time. So the first naive approach was to do it like this: listO…

[gastaldi]

+1 to JDK 8 as the minimum version. There is no reason to upgrade to JDK 7 as it will be EOL’ed soon.

[lordofthejars]

Hope in near future we can give news about this