Hi Romain, That's interesting when the Java EE 7 spec is clear that it requires Java SE 7... But, maybe since Java Batch can also be used in an SE environment, they can change their requirement for SE. But, technically, they can't override the requirement for Java SE 7 in the EE environment.
It may not be a big deal for the API, but I wonder if this dual requirement will cause any issues for the implementation and integration with Java EE environments. I guess we'll find out... Kevin On Tue, Nov 26, 2013 at 4:01 AM, Romain Manni-Bucau <[email protected]>wrote: > Hi Mark, > > "the only issue I found is you built it against java 7 where the spec says > > "This specification applies to Java SE and Java EE environments. It > requires Java 6 or higher. " > > Not sure it is a blocker or not. > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2013/11/25 Mark Struberg <[email protected]>: > > Good evening! > > > > I'd like to call a VOTE on releasing the geronimo jbatch 1.0 API. > > > > The API is already used in Apache BatchEE and passes the JSR-352 JBatch > TCK. > > > > The staging repo is > > > https://repository.apache.org/content/repositories/orgapachegeronimo-005/ > > > > The source release is here > > > https://repository.apache.org/content/repositories/orgapachegeronimo-005/org/apache/geronimo/specs/geronimo-jbatch_1.0_spec/1.0/geronimo-jbatch_1.0_spec-1.0-source-release.zip > > > > The tag can be found here > > > https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jbatch_1.0_spec-1.0/ > > > > [+1] ship it > > [+0] meh, don't care > > [-1] nope, because ${reason} > > > > Here is my +1 > > > > LieGrue, > > strub > > > > >
