Technically yes, then the issue is we need somebody with all perms to
release tomee (ping @David?).

*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*



2013/10/8 Alex The Rocker <alex.m3...@gmail.com>

> @Romain, not sure to understand the details, but do you mean you may have a
> way to release TomEE+ 1.6.0 official release without waiting for the
> (unknown) OpenJPA 2.3.0 release?
>
> Thanks,
> Alex
>
>
> On Tue, Oct 8, 2013 at 4:55 PM, Romain Manni-Bucau <rmannibu...@gmail.com
> >wrote:
>
> > I meant forking it for the release "as usual", not using a snapshot which
> > wouldn't be professional
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> > http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/10/8 Jean-Louis MONTEIRO <jeano...@gmail.com>
> >
> > > Possible, but I would only release TomEE itself not all modules to
> avoid
> > > depending on a snapshot.
> > > TomEE is different because if the snapshot is available during the
> build,
> > > which is obviously the case, we can embedded the JAR file in the zip
> > file.
> > >
> > > JLouis
> > >
> > >
> > > 2013/10/8 Romain Manni-Bucau <rmannibu...@gmail.com>
> > >
> > > > technically it is possible
> > > >
> > > > *Romain Manni-Bucau*
> > > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > > *Blog: **http://rmannibucau.wordpress.com/*<
> > > > http://rmannibucau.wordpress.com/>
> > > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > > *Github: https://github.com/rmannibucau*
> > > >
> > > >
> > > >
> > > > 2013/10/8 Alex The Rocker <alex.m3...@gmail.com>
> > > >
> > > > > Otherwise, can a TomEE 1.6.0 official release be make with a
> snapshot
> > > > > OpenJPA 2.3 ?
> > > > >
> > > > > I'm concerned if we have no visibility
> > > > >
> > > > > Thanks,
> > > > > Alex
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Oct 8, 2013 at 2:46 PM, Romain Manni-Bucau <
> > > > rmannibu...@gmail.com
> > > > > >wrote:
> > > > >
> > > > > > Would mean reverting some code in openejb + forking openwebbeans
> > and
> > > > > update
> > > > > > the code + accepting to not work in some cases in java 7...so I
> > don't
> > > > > think
> > > > > > so.
> > > > > >
> > > > > >
> > > > > > *Romain Manni-Bucau*
> > > > > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > > > > *Blog: **http://rmannibucau.wordpress.com/*<
> > > > > > http://rmannibucau.wordpress.com/>
> > > > > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > > > > *Github: https://github.com/rmannibucau*
> > > > > >
> > > > > >
> > > > > >
> > > > > > 2013/10/8 Alex The Rocker <alex.m3...@gmail.com>
> > > > > >
> > > > > > > From OpenJPA's web site:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> =============================================================================
> > > > > > > The 2.x releases <http://openjpa.apache.org/downloads.html>
> > (2.2.2
> > > > is
> > > > > > the
> > > > > > > latest) are a production ready, compliant implementation of the
> > > > JSR-317
> > > > > > > Java Persistence 2.0 <http://jcp.org/en/jsr/detail?id=317>
> > > > > > specification,
> > > > > > > which is backwards compatible to the JPA 1.0 specification and
> > > passes
> > > > > the
> > > > > > > Sun JPA 2.0 Technology Compatibility Kit.
> > > > > > >
> > > > > > > The upcoming 2.3 release is based off of the 2.2.x release
> stream
> > > and
> > > > > > will
> > > > > > > contain some additional features (TBD).
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> =============================================================================
> > > > > > >
> > > > > > > No way to know when OpenJPA 2.3 could be available.
> > > > > > >
> > > > > > > Can't we have a TomEE 1.6.0 release based on OpenJPA 2.2.2
> which
> > is
> > > > > > already
> > > > > > > TCK compliant, and leave OpenJPA 2.3 for a future TomEE
> release?
> > > > > > >
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Alex
> > > > > > >
> > > > > > >
> > > > > > > On Tue, Oct 8, 2013 at 2:21 PM, Romain Manni-Bucau <
> > > > > > rmannibu...@gmail.com
> > > > > > > >wrote:
> > > > > > >
> > > > > > > > @Alex: 2.3.0, there are working on it but want to address few
> > > > > blocking
> > > > > > > > issues before AFAIK
> > > > > > > >
> > > > > > > > *Romain Manni-Bucau*
> > > > > > > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > > > > > > *Blog: **http://rmannibucau.wordpress.com/*<
> > > > > > > > http://rmannibucau.wordpress.com/>
> > > > > > > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > > > > > > *Github: https://github.com/rmannibucau*
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > 2013/10/8 Alex The Rocker <alex.m3...@gmail.com>
> > > > > > > >
> > > > > > > > > @Romain: which OpenJPA release are you waiting to make
> TomEE
> > > > 1.6.0
> > > > > > > > > generally available, and what is this OpenJPA release's
> > > schedule?
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Alex
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Tue, Oct 8, 2013 at 11:01 AM, zmirc <m_chi...@yahoo.com
> >
> > > > wrote:
> > > > > > > > >
> > > > > > > > > > I would really want to know that, too.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > View this message in context:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://openejb.979440.n4.nabble.com/1-6-0-release-plans-tp4665437p4665447.html
> > > > > > > > > > Sent from the OpenEJB User mailing list archive at
> > > Nabble.com.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Jean-Louis
> > >
> >
>

Reply via email to