geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Sutter <kwsut...@gmail.com>
Subject Re: [VOTE] release geronimo-jbatch_1.0-1.0
Date Tue, 26 Nov 2013 15:41:08 GMT
Hi Romain,
>From a runtime perspective, which in turn would require the build...

>From an EE Container perspective (EE.2.4.1):
"This specification requires that containers provide a Java Compatibleā„¢
runtime environment, as defined by the Java Platform, Standard Edition, v7
specification (Java SE)."

Also, in section EE.6.1.1:
"The containers provide all application components with at least the Java
Platform, Standard Edition, v7 (Java SE) APIs."
"In particular, the applet execution environment must be Java SE 7
compatible."

And, then in the EE.8.3.x sections for the various classloading
requirements across the containers:
"All Java SE 7 API classes."

And, finally in the Additional Requirements section (EE.B.1.1):
"Java EE 7 requires Java SE 7."

I know there are items in the JPA stack that require Java 7.  I just
assumed that Java 7 would be the minimum until I saw your post about the
Java Batch API...

Kevin


On Tue, Nov 26, 2013 at 8:49 AM, Romain Manni-Bucau
<rmannibucau@gmail.com>wrote:

> Hi Kevin,
>
> java 7 requires Java 7 as runtime or build version? Basically I see
> nothing in javaee 7 which could prevent to build against j6 almost the
> whole stack.
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2013/11/26 Kevin Sutter <kwsutter@gmail.com>:
> > 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 <
> rmannibucau@gmail.com>
> > 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 <struberg@yahoo.de>:
> >> > 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
> >> >
> >> >
> >
> >
>

Mime
View raw message