You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by David Blevins <da...@gmail.com> on 2016/05/02 02:07:16 UTC
Re: 7.0.0 release vote
In terms of statements of compliance, which of these Java EE 7 samples will currently run successfully?
- https://github.com/javaee-samples/javaee7-samples <https://github.com/javaee-samples/javaee7-samples>
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
> On Apr 28, 2016, at 6:19 AM, ross.cohen <ro...@gmail.com> wrote:
>
> Actually, it looks like a 7.0 release means different things to different
> people. Romain, you took everyone's approval of the idea of a 7.0.0 release
> to be an approval of your particular version of a 7.0.0 release, which it
> clearly was not. Looks to me like a finer-grained vote is needed to figure
> out exactly what people want as part of 7.0.0 release.
>
> Personally, I think David is correct in saying that a release without some
> kind of positive JEE 7 compatibility statement is a serious mistake. I know
> the TCK is out of the question right now, but that simply means you need to
> invent an alternative compatibility statement: "Apache-Certified Compliant
> to Web Profile Specifications" (or some such).
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: 7.0.0 release vote
Posted by Romain Manni-Bucau <rm...@gmail.com>.
did the same and got an enthousistic moment, didnt last :(
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
2016-05-02 14:31 GMT+02:00 Andy Gumbrecht <ag...@tomitribe.com>:
> Yep, misleading use of the word 'OR' on this page -
> http://hibernate.org/community/license/ - "Hibernate projects are licensed
> under either the LGPL 2.1 or the ASL 2.0"
>
> On 2 May 2016 at 14:05, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> > 2016-05-02 14:00 GMT+02:00 Andy Gumbrecht <ag...@tomitribe.com>:
> >
> > > I still feel we are due another Milestone release until TomEE is a
> little
> > > closer to the mark. There needs to be a really strong statement as to
> > what
> > > is available and what is not. There has already been some negative
> > feedback
> > > from power users that expected more, and were disappointed to find
> > missing
> > > features they expected to find merely based on the 7.x label - Wrongly
> > > thinking that TomEE EE7 support was complete (Because we haven't really
> > > told them).
> > >
> > >
> > Fully agree that's why it has been stated tomee 7 != javaee 7. We also
> got
> > very negative feedback and worse than negative feedbacks -> blockers to
> not
> > have a version without "M". You are free to do a milestone if you want
> and
> > even a 8.0.0 when we get certified. In the meantime I see only harmful
> > reasons to block all people waiting on a not milestone (including
> vendors).
> >
> > Said otherwise: I try to push the concrete path vs the philosophical one.
> >
> >
> > > Would there be a problem distributing the latest Hibernate (ASL) with
> > > TomEE? - Even if some features would need unwrapping and documenting.
> > >
> > >
> > it is still mentionned being lgpl 2.1 on their website. validator is asl
> > AFAIK cause of JCP but orm is not. Did you find another source?
> >
> >
> > > Andy.
> > >
> > > On 2 May 2016 at 13:48, Roberto Cortez <ra...@yahoo.com.invalid>
> > > wrote:
> > >
> > > > Some JAX-RS tests are using JPA 2.1 features which is not supported
> > yet.
> > > > From: John D. Ament <jo...@apache.org>
> > > > To: dev@tomee.apache.org
> > > > Sent: Monday, May 2, 2016 12:11 PM
> > > > Subject: Re: 7.0.0 release vote
> > > >
> > > > On Mon, May 2, 2016 at 2:44 AM Romain Manni-Bucau <
> > rmannibucau@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Not portable test, jpa on not jpa tests etc. We pass really more
> > tests
> > > > > AFAIK.
> > > >
> > > >
> > > > Could you elaborate on that a little? What is not portable? If you
> > want
> > > to
> > > > raise issues in our ticket system please feel free:
> > > > https://github.com/javaee-samples/javaee7-samples/issues
> > > >
> > > > Or if you want to just say them, I can put them into github.
> > > >
> > > >
> > > >
> > > > > Le 2 mai 2016 05:48, "David Blevins" <da...@gmail.com> a
> > > écrit :
> > > > >
> > > > > > No worries on the many posts. Thank you for the Java EE 7
> samples
> > > > > checkup
> > > > > > :)
> > > > > >
> > > > > > It appears we fail 35% of the JAX-RS 2.0 tests. Do we know what
> is
> > > > > > preventing us from passing those tests?
> > > > > >
> > > > > >
> > > > > > --
> > > > > > David Blevins
> > > > > > http://twitter.com/dblevins
> > > > > > http://www.tomitribe.com
> > > > > >
> > > > > > > On May 1, 2016, at 6:42 PM, John D. Ament <
> johndament@apache.org
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > Sorry for so many posts :-)
> > > > > > >
> > > > > > > TomEE Plus 7.0.0-M3 passes 238/338 tests in the suite.
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > On Sun, May 1, 2016 at 9:30 PM John D. Ament <
> > > johndament@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > >> I ended up changing the version and updating the code. I ran
> > the
> > > > > tests,
> > > > > > >> you can see the output in this gist:
> > > > > > >>
> > > https://gist.github.com/johnament/2443e79836605a913159b14295681536
> > > > > > >>
> > > > > > >> TomEE Plus fails at about 100 tests.
> > > > > > >>
> > > > > > >> John
> > > > > > >>
> > > > > > >>
> > > > > > >> On Sun, May 1, 2016 at 8:10 PM John D. Ament <
> > > johndament@apache.org
> > > > >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >>> If it helps any, I can push up the latest TomEE version to
> the
> > > > TomEE
> > > > > > >>> profile:
> > > > > > >>>
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
> > > > > > >>>
> > > > > > >>> John
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> On Sun, May 1, 2016 at 8:07 PM David Blevins <
> > > > > david.blevins@gmail.com>
> > > > > > >>> wrote:
> > > > > > >>>
> > > > > > >>>> In terms of statements of compliance, which of these Java
> EE 7
> > > > > samples
> > > > > > >>>> will currently run successfully?
> > > > > > >>>>
> > > > > > >>>> - https://github.com/javaee-samples/javaee7-samples <
> > > > > > >>>> https://github.com/javaee-samples/javaee7-samples>
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>> --
> > > > > > >>>> David Blevins
> > > > > > >>>> http://twitter.com/dblevins
> > > > > > >>>> http://www.tomitribe.com
> > > > > > >>>>
> > > > > > >>>>> On Apr 28, 2016, at 6:19 AM, ross.cohen <
> > > ross.cohen.rc@gmail.com
> > > > >
> > > > > > >>>> wrote:
> > > > > > >>>>>
> > > > > > >>>>> Actually, it looks like a 7.0 release means different
> things
> > to
> > > > > > >>>> different
> > > > > > >>>>> people. Romain, you took everyone's approval of the idea
> of
> > a
> > > > > 7.0.0
> > > > > > >>>> release
> > > > > > >>>>> to be an approval of your particular version of a 7.0.0
> > > release,
> > > > > > which
> > > > > > >>>> it
> > > > > > >>>>> clearly was not. Looks to me like a finer-grained vote is
> > > needed
> > > > > to
> > > > > > >>>> figure
> > > > > > >>>>> out exactly what people want as part of 7.0.0 release.
> > > > > > >>>>>
> > > > > > >>>>> Personally, I think David is correct in saying that a
> release
> > > > > without
> > > > > > >>>> some
> > > > > > >>>>> kind of positive JEE 7 compatibility statement is a serious
> > > > > mistake.
> > > > > > >>>> I know
> > > > > > >>>>> the TCK is out of the question right now, but that simply
> > means
> > > > you
> > > > > > >>>> need to
> > > > > > >>>>> invent an alternative compatibility statement:
> > > "Apache-Certified
> > > > > > >>>> Compliant
> > > > > > >>>>> to Web Profile Specifications" (or some such).
> > > > > > >>>>>
> > > > > > >>>>>
> > > > > > >>>>>
> > > > > > >>>>> --
> > > > > > >>>>> View this message in context:
> > > > > > >>>>
> > > > > >
> > > > >
> > > >
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
> > > > > > >>>>> Sent from the TomEE Dev mailing list archive at Nabble.com.
> > > > > > >>>>
> > > > > > >>>>
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Andy Gumbrecht
> > > https://twitter.com/AndyGeeDe
> > > http://www.tomitribe.com
> > >
> >
>
>
>
> --
> Andy Gumbrecht
> https://twitter.com/AndyGeeDe
> http://www.tomitribe.com
>
Re: 7.0.0 release vote
Posted by "John D. Ament" <jo...@apache.org>.
I'm not sure if you're interpretting it as hibernate ORM is AL or not, but
ORM is LGPL. OGM and search are also LGPL. Bean validation is pretty much
the only ALv2 component.
On Mon, May 2, 2016 at 8:31 AM Andy Gumbrecht <ag...@tomitribe.com>
wrote:
> Yep, misleading use of the word 'OR' on this page -
> http://hibernate.org/community/license/ - "Hibernate projects are licensed
> under either the LGPL 2.1 or the ASL 2.0"
>
> On 2 May 2016 at 14:05, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> > 2016-05-02 14:00 GMT+02:00 Andy Gumbrecht <ag...@tomitribe.com>:
> >
> > > I still feel we are due another Milestone release until TomEE is a
> little
> > > closer to the mark. There needs to be a really strong statement as to
> > what
> > > is available and what is not. There has already been some negative
> > feedback
> > > from power users that expected more, and were disappointed to find
> > missing
> > > features they expected to find merely based on the 7.x label - Wrongly
> > > thinking that TomEE EE7 support was complete (Because we haven't really
> > > told them).
> > >
> > >
> > Fully agree that's why it has been stated tomee 7 != javaee 7. We also
> got
> > very negative feedback and worse than negative feedbacks -> blockers to
> not
> > have a version without "M". You are free to do a milestone if you want
> and
> > even a 8.0.0 when we get certified. In the meantime I see only harmful
> > reasons to block all people waiting on a not milestone (including
> vendors).
> >
> > Said otherwise: I try to push the concrete path vs the philosophical one.
> >
> >
> > > Would there be a problem distributing the latest Hibernate (ASL) with
> > > TomEE? - Even if some features would need unwrapping and documenting.
> > >
> > >
> > it is still mentionned being lgpl 2.1 on their website. validator is asl
> > AFAIK cause of JCP but orm is not. Did you find another source?
> >
> >
> > > Andy.
> > >
> > > On 2 May 2016 at 13:48, Roberto Cortez <ra...@yahoo.com.invalid>
> > > wrote:
> > >
> > > > Some JAX-RS tests are using JPA 2.1 features which is not supported
> > yet.
> > > > From: John D. Ament <jo...@apache.org>
> > > > To: dev@tomee.apache.org
> > > > Sent: Monday, May 2, 2016 12:11 PM
> > > > Subject: Re: 7.0.0 release vote
> > > >
> > > > On Mon, May 2, 2016 at 2:44 AM Romain Manni-Bucau <
> > rmannibucau@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Not portable test, jpa on not jpa tests etc. We pass really more
> > tests
> > > > > AFAIK.
> > > >
> > > >
> > > > Could you elaborate on that a little? What is not portable? If you
> > want
> > > to
> > > > raise issues in our ticket system please feel free:
> > > > https://github.com/javaee-samples/javaee7-samples/issues
> > > >
> > > > Or if you want to just say them, I can put them into github.
> > > >
> > > >
> > > >
> > > > > Le 2 mai 2016 05:48, "David Blevins" <da...@gmail.com> a
> > > écrit :
> > > > >
> > > > > > No worries on the many posts. Thank you for the Java EE 7
> samples
> > > > > checkup
> > > > > > :)
> > > > > >
> > > > > > It appears we fail 35% of the JAX-RS 2.0 tests. Do we know what
> is
> > > > > > preventing us from passing those tests?
> > > > > >
> > > > > >
> > > > > > --
> > > > > > David Blevins
> > > > > > http://twitter.com/dblevins
> > > > > > http://www.tomitribe.com
> > > > > >
> > > > > > > On May 1, 2016, at 6:42 PM, John D. Ament <
> johndament@apache.org
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > Sorry for so many posts :-)
> > > > > > >
> > > > > > > TomEE Plus 7.0.0-M3 passes 238/338 tests in the suite.
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > On Sun, May 1, 2016 at 9:30 PM John D. Ament <
> > > johndament@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > >> I ended up changing the version and updating the code. I ran
> > the
> > > > > tests,
> > > > > > >> you can see the output in this gist:
> > > > > > >>
> > > https://gist.github.com/johnament/2443e79836605a913159b14295681536
> > > > > > >>
> > > > > > >> TomEE Plus fails at about 100 tests.
> > > > > > >>
> > > > > > >> John
> > > > > > >>
> > > > > > >>
> > > > > > >> On Sun, May 1, 2016 at 8:10 PM John D. Ament <
> > > johndament@apache.org
> > > > >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >>> If it helps any, I can push up the latest TomEE version to
> the
> > > > TomEE
> > > > > > >>> profile:
> > > > > > >>>
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
> > > > > > >>>
> > > > > > >>> John
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> On Sun, May 1, 2016 at 8:07 PM David Blevins <
> > > > > david.blevins@gmail.com>
> > > > > > >>> wrote:
> > > > > > >>>
> > > > > > >>>> In terms of statements of compliance, which of these Java
> EE 7
> > > > > samples
> > > > > > >>>> will currently run successfully?
> > > > > > >>>>
> > > > > > >>>> - https://github.com/javaee-samples/javaee7-samples <
> > > > > > >>>> https://github.com/javaee-samples/javaee7-samples>
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>> --
> > > > > > >>>> David Blevins
> > > > > > >>>> http://twitter.com/dblevins
> > > > > > >>>> http://www.tomitribe.com
> > > > > > >>>>
> > > > > > >>>>> On Apr 28, 2016, at 6:19 AM, ross.cohen <
> > > ross.cohen.rc@gmail.com
> > > > >
> > > > > > >>>> wrote:
> > > > > > >>>>>
> > > > > > >>>>> Actually, it looks like a 7.0 release means different
> things
> > to
> > > > > > >>>> different
> > > > > > >>>>> people. Romain, you took everyone's approval of the idea
> of
> > a
> > > > > 7.0.0
> > > > > > >>>> release
> > > > > > >>>>> to be an approval of your particular version of a 7.0.0
> > > release,
> > > > > > which
> > > > > > >>>> it
> > > > > > >>>>> clearly was not. Looks to me like a finer-grained vote is
> > > needed
> > > > > to
> > > > > > >>>> figure
> > > > > > >>>>> out exactly what people want as part of 7.0.0 release.
> > > > > > >>>>>
> > > > > > >>>>> Personally, I think David is correct in saying that a
> release
> > > > > without
> > > > > > >>>> some
> > > > > > >>>>> kind of positive JEE 7 compatibility statement is a serious
> > > > > mistake.
> > > > > > >>>> I know
> > > > > > >>>>> the TCK is out of the question right now, but that simply
> > means
> > > > you
> > > > > > >>>> need to
> > > > > > >>>>> invent an alternative compatibility statement:
> > > "Apache-Certified
> > > > > > >>>> Compliant
> > > > > > >>>>> to Web Profile Specifications" (or some such).
> > > > > > >>>>>
> > > > > > >>>>>
> > > > > > >>>>>
> > > > > > >>>>> --
> > > > > > >>>>> View this message in context:
> > > > > > >>>>
> > > > > >
> > > > >
> > > >
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
> > > > > > >>>>> Sent from the TomEE Dev mailing list archive at Nabble.com.
> > > > > > >>>>
> > > > > > >>>>
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Andy Gumbrecht
> > > https://twitter.com/AndyGeeDe
> > > http://www.tomitribe.com
> > >
> >
>
>
>
> --
> Andy Gumbrecht
> https://twitter.com/AndyGeeDe
> http://www.tomitribe.com
>
Re: 7.0.0 release vote
Posted by Andy Gumbrecht <ag...@tomitribe.com>.
Yep, misleading use of the word 'OR' on this page -
http://hibernate.org/community/license/ - "Hibernate projects are licensed
under either the LGPL 2.1 or the ASL 2.0"
On 2 May 2016 at 14:05, Romain Manni-Bucau <rm...@gmail.com> wrote:
> 2016-05-02 14:00 GMT+02:00 Andy Gumbrecht <ag...@tomitribe.com>:
>
> > I still feel we are due another Milestone release until TomEE is a little
> > closer to the mark. There needs to be a really strong statement as to
> what
> > is available and what is not. There has already been some negative
> feedback
> > from power users that expected more, and were disappointed to find
> missing
> > features they expected to find merely based on the 7.x label - Wrongly
> > thinking that TomEE EE7 support was complete (Because we haven't really
> > told them).
> >
> >
> Fully agree that's why it has been stated tomee 7 != javaee 7. We also got
> very negative feedback and worse than negative feedbacks -> blockers to not
> have a version without "M". You are free to do a milestone if you want and
> even a 8.0.0 when we get certified. In the meantime I see only harmful
> reasons to block all people waiting on a not milestone (including vendors).
>
> Said otherwise: I try to push the concrete path vs the philosophical one.
>
>
> > Would there be a problem distributing the latest Hibernate (ASL) with
> > TomEE? - Even if some features would need unwrapping and documenting.
> >
> >
> it is still mentionned being lgpl 2.1 on their website. validator is asl
> AFAIK cause of JCP but orm is not. Did you find another source?
>
>
> > Andy.
> >
> > On 2 May 2016 at 13:48, Roberto Cortez <ra...@yahoo.com.invalid>
> > wrote:
> >
> > > Some JAX-RS tests are using JPA 2.1 features which is not supported
> yet.
> > > From: John D. Ament <jo...@apache.org>
> > > To: dev@tomee.apache.org
> > > Sent: Monday, May 2, 2016 12:11 PM
> > > Subject: Re: 7.0.0 release vote
> > >
> > > On Mon, May 2, 2016 at 2:44 AM Romain Manni-Bucau <
> rmannibucau@gmail.com
> > >
> > > wrote:
> > >
> > > > Not portable test, jpa on not jpa tests etc. We pass really more
> tests
> > > > AFAIK.
> > >
> > >
> > > Could you elaborate on that a little? What is not portable? If you
> want
> > to
> > > raise issues in our ticket system please feel free:
> > > https://github.com/javaee-samples/javaee7-samples/issues
> > >
> > > Or if you want to just say them, I can put them into github.
> > >
> > >
> > >
> > > > Le 2 mai 2016 05:48, "David Blevins" <da...@gmail.com> a
> > écrit :
> > > >
> > > > > No worries on the many posts. Thank you for the Java EE 7 samples
> > > > checkup
> > > > > :)
> > > > >
> > > > > It appears we fail 35% of the JAX-RS 2.0 tests. Do we know what is
> > > > > preventing us from passing those tests?
> > > > >
> > > > >
> > > > > --
> > > > > David Blevins
> > > > > http://twitter.com/dblevins
> > > > > http://www.tomitribe.com
> > > > >
> > > > > > On May 1, 2016, at 6:42 PM, John D. Ament <johndament@apache.org
> >
> > > > wrote:
> > > > > >
> > > > > > Sorry for so many posts :-)
> > > > > >
> > > > > > TomEE Plus 7.0.0-M3 passes 238/338 tests in the suite.
> > > > > >
> > > > > > John
> > > > > >
> > > > > > On Sun, May 1, 2016 at 9:30 PM John D. Ament <
> > johndament@apache.org>
> > > > > wrote:
> > > > > >
> > > > > >> I ended up changing the version and updating the code. I ran
> the
> > > > tests,
> > > > > >> you can see the output in this gist:
> > > > > >>
> > https://gist.github.com/johnament/2443e79836605a913159b14295681536
> > > > > >>
> > > > > >> TomEE Plus fails at about 100 tests.
> > > > > >>
> > > > > >> John
> > > > > >>
> > > > > >>
> > > > > >> On Sun, May 1, 2016 at 8:10 PM John D. Ament <
> > johndament@apache.org
> > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >>> If it helps any, I can push up the latest TomEE version to the
> > > TomEE
> > > > > >>> profile:
> > > > > >>>
> > > > >
> > > >
> > >
> >
> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
> > > > > >>>
> > > > > >>> John
> > > > > >>>
> > > > > >>>
> > > > > >>> On Sun, May 1, 2016 at 8:07 PM David Blevins <
> > > > david.blevins@gmail.com>
> > > > > >>> wrote:
> > > > > >>>
> > > > > >>>> In terms of statements of compliance, which of these Java EE 7
> > > > samples
> > > > > >>>> will currently run successfully?
> > > > > >>>>
> > > > > >>>> - https://github.com/javaee-samples/javaee7-samples <
> > > > > >>>> https://github.com/javaee-samples/javaee7-samples>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> --
> > > > > >>>> David Blevins
> > > > > >>>> http://twitter.com/dblevins
> > > > > >>>> http://www.tomitribe.com
> > > > > >>>>
> > > > > >>>>> On Apr 28, 2016, at 6:19 AM, ross.cohen <
> > ross.cohen.rc@gmail.com
> > > >
> > > > > >>>> wrote:
> > > > > >>>>>
> > > > > >>>>> Actually, it looks like a 7.0 release means different things
> to
> > > > > >>>> different
> > > > > >>>>> people. Romain, you took everyone's approval of the idea of
> a
> > > > 7.0.0
> > > > > >>>> release
> > > > > >>>>> to be an approval of your particular version of a 7.0.0
> > release,
> > > > > which
> > > > > >>>> it
> > > > > >>>>> clearly was not. Looks to me like a finer-grained vote is
> > needed
> > > > to
> > > > > >>>> figure
> > > > > >>>>> out exactly what people want as part of 7.0.0 release.
> > > > > >>>>>
> > > > > >>>>> Personally, I think David is correct in saying that a release
> > > > without
> > > > > >>>> some
> > > > > >>>>> kind of positive JEE 7 compatibility statement is a serious
> > > > mistake.
> > > > > >>>> I know
> > > > > >>>>> the TCK is out of the question right now, but that simply
> means
> > > you
> > > > > >>>> need to
> > > > > >>>>> invent an alternative compatibility statement:
> > "Apache-Certified
> > > > > >>>> Compliant
> > > > > >>>>> to Web Profile Specifications" (or some such).
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>> --
> > > > > >>>>> View this message in context:
> > > > > >>>>
> > > > >
> > > >
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
> > > > > >>>>> Sent from the TomEE Dev mailing list archive at Nabble.com.
> > > > > >>>>
> > > > > >>>>
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
> > --
> > Andy Gumbrecht
> > https://twitter.com/AndyGeeDe
> > http://www.tomitribe.com
> >
>
--
Andy Gumbrecht
https://twitter.com/AndyGeeDe
http://www.tomitribe.com
Re: 7.0.0 release vote
Posted by Romain Manni-Bucau <rm...@gmail.com>.
@David: we needed a version >= 5 (think I voted for 5) just to not break
auto-tools like maven version comparison etc. Then I guess users desired
ee=tomee but when you pointed out this confusion to me I made it clear in a
thread.
@all: now we had milestones 7.x we need for the same reason a 7.0.0 or a >
7.x so 2, 3, 4, 5 and 6 are no more options.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
2016-05-03 7:53 GMT+02:00 Eduard Ketler <ed...@gmail.com>:
> Hi all, from a Customers or User perspective i totally agree with using
> version 2.x and wait with 7.x for the EE compliance. Thats pretty straight
> forward David. That would not confusing me.
>
> Eduard
>
> Matej <gm...@gmail.com> schrieb am Di., 3. Mai 2016 um 07:08:
>
> > Hi all. Not developer. But I also think jumping to 7.x for no reason will
> > only confuse everyone. If ee7 will not be provided like 98 - 99 %
> > compliant. Then it would really be better to maybe just go 2.x route. I
> > think already now people that choose Tomee, dont really care about being
> > 100% compliant. But still would be nice to not confuse people. Br matej
> > 3. maj 2016 05.43 je oseba "David Blevins" <da...@gmail.com>
> > napisala:
> >
> > >
> > > > On May 2, 2016, at 5:05 AM, Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > > wrote:
> > > >
> > > > Fully agree that's why it has been stated tomee 7 != javaee 7.
> > >
> > > My memory of that vote was we intentionally aligned the TomEE version
> > > number specifically to align to the Java EE version number and further
> > that
> > > it would not be changed even if major change in the server occurred,
> > > stating “7.1” and “7.2” would be clear enough to communicate breaking
> > > upgrades.
> > >
> > > I voted -1 on that one, but the above was my understanding of what was
> > > decided.
> > >
> > > I’d be glad to hear it is not, but I would question why we didn’t just
> > > stick with 2.x if we weren’t intending to communicate “this implements
> > Java
> > > EE 7”.
> > >
> > >
> > > -David
> > >
> > >
> >
>
Re: 7.0.0 release vote
Posted by Eduard Ketler <ed...@gmail.com>.
Hi all, from a Customers or User perspective i totally agree with using
version 2.x and wait with 7.x for the EE compliance. Thats pretty straight
forward David. That would not confusing me.
Eduard
Matej <gm...@gmail.com> schrieb am Di., 3. Mai 2016 um 07:08:
> Hi all. Not developer. But I also think jumping to 7.x for no reason will
> only confuse everyone. If ee7 will not be provided like 98 - 99 %
> compliant. Then it would really be better to maybe just go 2.x route. I
> think already now people that choose Tomee, dont really care about being
> 100% compliant. But still would be nice to not confuse people. Br matej
> 3. maj 2016 05.43 je oseba "David Blevins" <da...@gmail.com>
> napisala:
>
> >
> > > On May 2, 2016, at 5:05 AM, Romain Manni-Bucau <rm...@gmail.com>
> > wrote:
> > >
> > > Fully agree that's why it has been stated tomee 7 != javaee 7.
> >
> > My memory of that vote was we intentionally aligned the TomEE version
> > number specifically to align to the Java EE version number and further
> that
> > it would not be changed even if major change in the server occurred,
> > stating “7.1” and “7.2” would be clear enough to communicate breaking
> > upgrades.
> >
> > I voted -1 on that one, but the above was my understanding of what was
> > decided.
> >
> > I’d be glad to hear it is not, but I would question why we didn’t just
> > stick with 2.x if we weren’t intending to communicate “this implements
> Java
> > EE 7”.
> >
> >
> > -David
> >
> >
>
Re: 7.0.0 release vote
Posted by Matej <gm...@gmail.com>.
Hi all. Not developer. But I also think jumping to 7.x for no reason will
only confuse everyone. If ee7 will not be provided like 98 - 99 %
compliant. Then it would really be better to maybe just go 2.x route. I
think already now people that choose Tomee, dont really care about being
100% compliant. But still would be nice to not confuse people. Br matej
3. maj 2016 05.43 je oseba "David Blevins" <da...@gmail.com>
napisala:
>
> > On May 2, 2016, at 5:05 AM, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
> >
> > Fully agree that's why it has been stated tomee 7 != javaee 7.
>
> My memory of that vote was we intentionally aligned the TomEE version
> number specifically to align to the Java EE version number and further that
> it would not be changed even if major change in the server occurred,
> stating “7.1” and “7.2” would be clear enough to communicate breaking
> upgrades.
>
> I voted -1 on that one, but the above was my understanding of what was
> decided.
>
> I’d be glad to hear it is not, but I would question why we didn’t just
> stick with 2.x if we weren’t intending to communicate “this implements Java
> EE 7”.
>
>
> -David
>
>
Re: 7.0.0 release vote
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Being 95% compliant or 2% compliant depends on what: spec, tck, goal,
usability etc...
Numbers mean nothing, user feedback does and is rather good for now.
Le 5 mai 2016 17:04, "ross.cohen" <ro...@gmail.com> a écrit :
> Romain Manni-Bucau wrote
> > Le 4 mai 2016 23:28, "ross.cohen" <
>
> > ross.cohen.rc@
>
> > > a écrit :
> >>
> >> Romain Manni-Bucau wrote
> >> > 2016-05-04 14:54 GMT+02:00 ross.cohen <
> >>
> >> > ross.cohen.rc@
> >>
> >> > >:
> >> >
> >> >> David Blevins-2 wrote
> >> >> >> On May 2, 2016, at 5:05 AM, Romain Manni-Bucau <
> >> >
> >> >>
> >> >> That is also my recollection of the question.
> >> >>
> >> >> But whether or not it was the case, it is certainly the case that any
> >> >> user
> >> >> downloading Tomee 7.x will do so under the impression that it is JEE
> 7
> >> >> compliant. This is reason enough to either wait, or continue under
> >> the
> >> >> current numbering scheme.
> >> >>
> >> >>
> >> >>
> >> > Well both lead to the same: tomee is not adapted. Question is then:
> >> when
> >> > do
> >> > we stop waiting for something likely not coming?
> >>
> >> I don't really care about the TCK. Everyone would like it if Oracle
> >> would
> >> play nice
> >> and released a TCK for us, but it's not going to happen. However,
> >> compliance with
> >> the specs is a different matter. At what point are we compliant with
> the
> >> specs?
> >> Good question. David says the rest api passes only 75% of the published
> >> examples. To me, that is non-compliant. If it were 95%, I'd be
> willing
> > to
> >> call us
> >> compliant. Exactly where is the line? I'm not sure, but it can't be
> > much
> >> below 95%.
> >> If users find that the software frequently contradicts the spec, they
> >> will
> >> become
> >> frustrated and angry.
> >
> > Examples are not spec compliant too or abuse of vendor behavior. Also a
> > serious amount of users just need what is in tomee now. I tend to prefer
> > to
> > move forward with active people than waiting passive ones move - we lost
> 2
> > years with such a behavior.
> >
> > What you mentionned is also true for 100% certified servers so with
> > experience I think ignoring it is fine while we fix fast.
>
> If it is truly the case that Tomee is 95%+ compliant, then releasing 7.0
> seems reasonable. As you point out, no implementation is 100% compliant.
>
> Cheers.
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284p4678364.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>
Re: 7.0.0 release vote
Posted by David Blevins <da...@gmail.com>.
> On May 5, 2016, at 7:26 AM, ross.cohen <ro...@gmail.com> wrote:
>>
>> Examples are not spec compliant too or abuse of vendor behavior. Also a
>> serious amount of users just need what is in tomee now. I tend to prefer
>> to
>> move forward with active people than waiting passive ones move - we lost 2
>> years with such a behavior.
>>
>> What you mentionned is also true for 100% certified servers so with
>> experience I think ignoring it is fine while we fix fast.
>
> If it is truly the case that Tomee is 95%+ compliant, then releasing 7.0
> seems reasonable. As you point out, no implementation is 100% compliant.
To my observation we have stones unturned. Vendor-specific or not the Java EE 7 examples project are 1) what people are using to learn and 2) run (mostly) fine against compliant Glassfish and Wildfly.
You can see the green and red thumbs up on this page for the full list:
- http://javaee.support/ <http://javaee.support/>
We currently fail 10 out of 28 tests for JAX-RS. Failed tests include JAX-RS 2.0 Client, JSON-P support, JAX-RS Security Declarative, Bean Validation integration, and Async Server support.
Ideally, we’d take some time and pic through them one-by-one and figure out exactly why they don’t pass and make sure everyone is aware and ok with those reasons.
The only technical reason I’ve heard is due to JPA. Seems we could run those tests against Plume and see how we do.
-David
Re: 7.0.0 release vote
Posted by "ross.cohen" <ro...@gmail.com>.
Romain Manni-Bucau wrote
> Le 4 mai 2016 23:28, "ross.cohen" <
> ross.cohen.rc@
> > a écrit :
>>
>> Romain Manni-Bucau wrote
>> > 2016-05-04 14:54 GMT+02:00 ross.cohen <
>>
>> > ross.cohen.rc@
>>
>> > >:
>> >
>> >> David Blevins-2 wrote
>> >> >> On May 2, 2016, at 5:05 AM, Romain Manni-Bucau <
>> >
>> >>
>> >> That is also my recollection of the question.
>> >>
>> >> But whether or not it was the case, it is certainly the case that any
>> >> user
>> >> downloading Tomee 7.x will do so under the impression that it is JEE 7
>> >> compliant. This is reason enough to either wait, or continue under
>> the
>> >> current numbering scheme.
>> >>
>> >>
>> >>
>> > Well both lead to the same: tomee is not adapted. Question is then:
>> when
>> > do
>> > we stop waiting for something likely not coming?
>>
>> I don't really care about the TCK. Everyone would like it if Oracle
>> would
>> play nice
>> and released a TCK for us, but it's not going to happen. However,
>> compliance with
>> the specs is a different matter. At what point are we compliant with the
>> specs?
>> Good question. David says the rest api passes only 75% of the published
>> examples. To me, that is non-compliant. If it were 95%, I'd be willing
> to
>> call us
>> compliant. Exactly where is the line? I'm not sure, but it can't be
> much
>> below 95%.
>> If users find that the software frequently contradicts the spec, they
>> will
>> become
>> frustrated and angry.
>
> Examples are not spec compliant too or abuse of vendor behavior. Also a
> serious amount of users just need what is in tomee now. I tend to prefer
> to
> move forward with active people than waiting passive ones move - we lost 2
> years with such a behavior.
>
> What you mentionned is also true for 100% certified servers so with
> experience I think ignoring it is fine while we fix fast.
If it is truly the case that Tomee is 95%+ compliant, then releasing 7.0
seems reasonable. As you point out, no implementation is 100% compliant.
Cheers.
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284p4678364.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: 7.0.0 release vote
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Le 4 mai 2016 23:28, "ross.cohen" <ro...@gmail.com> a écrit :
>
> Romain Manni-Bucau wrote
> > 2016-05-04 14:54 GMT+02:00 ross.cohen <
>
> > ross.cohen.rc@
>
> > >:
> >
> >> David Blevins-2 wrote
> >> >> On May 2, 2016, at 5:05 AM, Romain Manni-Bucau <
> >
> >>
> >> That is also my recollection of the question.
> >>
> >> But whether or not it was the case, it is certainly the case that any
> >> user
> >> downloading Tomee 7.x will do so under the impression that it is JEE 7
> >> compliant. This is reason enough to either wait, or continue under the
> >> current numbering scheme.
> >>
> >>
> >>
> > Well both lead to the same: tomee is not adapted. Question is then: when
> > do
> > we stop waiting for something likely not coming?
>
> I don't really care about the TCK. Everyone would like it if Oracle would
> play nice
> and released a TCK for us, but it's not going to happen. However,
> compliance with
> the specs is a different matter. At what point are we compliant with the
> specs?
> Good question. David says the rest api passes only 75% of the published
> examples. To me, that is non-compliant. If it were 95%, I'd be willing
to
> call us
> compliant. Exactly where is the line? I'm not sure, but it can't be
much
> below 95%.
> If users find that the software frequently contradicts the spec, they will
> become
> frustrated and angry.
>
Examples are not spec compliant too or abuse of vendor behavior. Also a
serious amount of users just need what is in tomee now. I tend to prefer to
move forward with active people than waiting passive ones move - we lost 2
years with such a behavior.
What you mentionned is also true for 100% certified servers so with
experience I think ignoring it is fine while we fix fast.
Anyway as said vote passed even if some people were not happy. Ill start a
vote next week and let see what happen.
> Cheers
>
>
>
>
>
> --
> View this message in context:
http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284p4678361.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: 7.0.0 release vote
Posted by "ross.cohen" <ro...@gmail.com>.
Romain Manni-Bucau wrote
> 2016-05-04 14:54 GMT+02:00 ross.cohen <
> ross.cohen.rc@
> >:
>
>> David Blevins-2 wrote
>> >> On May 2, 2016, at 5:05 AM, Romain Manni-Bucau <
>
>>
>> That is also my recollection of the question.
>>
>> But whether or not it was the case, it is certainly the case that any
>> user
>> downloading Tomee 7.x will do so under the impression that it is JEE 7
>> compliant. This is reason enough to either wait, or continue under the
>> current numbering scheme.
>>
>>
>>
> Well both lead to the same: tomee is not adapted. Question is then: when
> do
> we stop waiting for something likely not coming?
I don't really care about the TCK. Everyone would like it if Oracle would
play nice
and released a TCK for us, but it's not going to happen. However,
compliance with
the specs is a different matter. At what point are we compliant with the
specs?
Good question. David says the rest api passes only 75% of the published
examples. To me, that is non-compliant. If it were 95%, I'd be willing to
call us
compliant. Exactly where is the line? I'm not sure, but it can't be much
below 95%.
If users find that the software frequently contradicts the spec, they will
become
frustrated and angry.
Cheers
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284p4678361.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: 7.0.0 release vote
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2016-05-04 14:54 GMT+02:00 ross.cohen <ro...@gmail.com>:
> David Blevins-2 wrote
> >> On May 2, 2016, at 5:05 AM, Romain Manni-Bucau <
>
> > rmannibucau@
>
> > > wrote:
> >>
> >> Fully agree that's why it has been stated tomee 7 != javaee 7.
> >
> > My memory of that vote was we intentionally aligned the TomEE version
> > number specifically to align to the Java EE version number and further
> > that it would not be changed even if major change in the server occurred,
> > stating “7.1” and “7.2” would be clear enough to communicate breaking
> > upgrades.
> >
> > I voted -1 on that one, but the above was my understanding of what was
> > decided.
> >
> > I’d be glad to hear it is not, but I would question why we didn’t just
> > stick with 2.x if we weren’t intending to communicate “this implements
> > Java EE 7”.
>
> That is also my recollection of the question.
>
> But whether or not it was the case, it is certainly the case that any user
> downloading Tomee 7.x will do so under the impression that it is JEE 7
> compliant. This is reason enough to either wait, or continue under the
> current numbering scheme.
>
>
>
Well both lead to the same: tomee is not adapted. Question is then: when do
we stop waiting for something likely not coming?
>
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284p4678347.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>
Re: 7.0.0 release vote
Posted by "ross.cohen" <ro...@gmail.com>.
David Blevins-2 wrote
>> On May 2, 2016, at 5:05 AM, Romain Manni-Bucau <
> rmannibucau@
> > wrote:
>>
>> Fully agree that's why it has been stated tomee 7 != javaee 7.
>
> My memory of that vote was we intentionally aligned the TomEE version
> number specifically to align to the Java EE version number and further
> that it would not be changed even if major change in the server occurred,
> stating “7.1” and “7.2” would be clear enough to communicate breaking
> upgrades.
>
> I voted -1 on that one, but the above was my understanding of what was
> decided.
>
> I’d be glad to hear it is not, but I would question why we didn’t just
> stick with 2.x if we weren’t intending to communicate “this implements
> Java EE 7”.
That is also my recollection of the question.
But whether or not it was the case, it is certainly the case that any user
downloading Tomee 7.x will do so under the impression that it is JEE 7
compliant. This is reason enough to either wait, or continue under the
current numbering scheme.
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284p4678347.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: 7.0.0 release vote
Posted by David Blevins <da...@gmail.com>.
> On May 2, 2016, at 5:05 AM, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> Fully agree that's why it has been stated tomee 7 != javaee 7.
My memory of that vote was we intentionally aligned the TomEE version number specifically to align to the Java EE version number and further that it would not be changed even if major change in the server occurred, stating “7.1” and “7.2” would be clear enough to communicate breaking upgrades.
I voted -1 on that one, but the above was my understanding of what was decided.
I’d be glad to hear it is not, but I would question why we didn’t just stick with 2.x if we weren’t intending to communicate “this implements Java EE 7”.
-David
Re: 7.0.0 release vote
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2016-05-02 14:00 GMT+02:00 Andy Gumbrecht <ag...@tomitribe.com>:
> I still feel we are due another Milestone release until TomEE is a little
> closer to the mark. There needs to be a really strong statement as to what
> is available and what is not. There has already been some negative feedback
> from power users that expected more, and were disappointed to find missing
> features they expected to find merely based on the 7.x label - Wrongly
> thinking that TomEE EE7 support was complete (Because we haven't really
> told them).
>
>
Fully agree that's why it has been stated tomee 7 != javaee 7. We also got
very negative feedback and worse than negative feedbacks -> blockers to not
have a version without "M". You are free to do a milestone if you want and
even a 8.0.0 when we get certified. In the meantime I see only harmful
reasons to block all people waiting on a not milestone (including vendors).
Said otherwise: I try to push the concrete path vs the philosophical one.
> Would there be a problem distributing the latest Hibernate (ASL) with
> TomEE? - Even if some features would need unwrapping and documenting.
>
>
it is still mentionned being lgpl 2.1 on their website. validator is asl
AFAIK cause of JCP but orm is not. Did you find another source?
> Andy.
>
> On 2 May 2016 at 13:48, Roberto Cortez <ra...@yahoo.com.invalid>
> wrote:
>
> > Some JAX-RS tests are using JPA 2.1 features which is not supported yet.
> > From: John D. Ament <jo...@apache.org>
> > To: dev@tomee.apache.org
> > Sent: Monday, May 2, 2016 12:11 PM
> > Subject: Re: 7.0.0 release vote
> >
> > On Mon, May 2, 2016 at 2:44 AM Romain Manni-Bucau <rmannibucau@gmail.com
> >
> > wrote:
> >
> > > Not portable test, jpa on not jpa tests etc. We pass really more tests
> > > AFAIK.
> >
> >
> > Could you elaborate on that a little? What is not portable? If you want
> to
> > raise issues in our ticket system please feel free:
> > https://github.com/javaee-samples/javaee7-samples/issues
> >
> > Or if you want to just say them, I can put them into github.
> >
> >
> >
> > > Le 2 mai 2016 05:48, "David Blevins" <da...@gmail.com> a
> écrit :
> > >
> > > > No worries on the many posts. Thank you for the Java EE 7 samples
> > > checkup
> > > > :)
> > > >
> > > > It appears we fail 35% of the JAX-RS 2.0 tests. Do we know what is
> > > > preventing us from passing those tests?
> > > >
> > > >
> > > > --
> > > > David Blevins
> > > > http://twitter.com/dblevins
> > > > http://www.tomitribe.com
> > > >
> > > > > On May 1, 2016, at 6:42 PM, John D. Ament <jo...@apache.org>
> > > wrote:
> > > > >
> > > > > Sorry for so many posts :-)
> > > > >
> > > > > TomEE Plus 7.0.0-M3 passes 238/338 tests in the suite.
> > > > >
> > > > > John
> > > > >
> > > > > On Sun, May 1, 2016 at 9:30 PM John D. Ament <
> johndament@apache.org>
> > > > wrote:
> > > > >
> > > > >> I ended up changing the version and updating the code. I ran the
> > > tests,
> > > > >> you can see the output in this gist:
> > > > >>
> https://gist.github.com/johnament/2443e79836605a913159b14295681536
> > > > >>
> > > > >> TomEE Plus fails at about 100 tests.
> > > > >>
> > > > >> John
> > > > >>
> > > > >>
> > > > >> On Sun, May 1, 2016 at 8:10 PM John D. Ament <
> johndament@apache.org
> > >
> > > > >> wrote:
> > > > >>
> > > > >>> If it helps any, I can push up the latest TomEE version to the
> > TomEE
> > > > >>> profile:
> > > > >>>
> > > >
> > >
> >
> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
> > > > >>>
> > > > >>> John
> > > > >>>
> > > > >>>
> > > > >>> On Sun, May 1, 2016 at 8:07 PM David Blevins <
> > > david.blevins@gmail.com>
> > > > >>> wrote:
> > > > >>>
> > > > >>>> In terms of statements of compliance, which of these Java EE 7
> > > samples
> > > > >>>> will currently run successfully?
> > > > >>>>
> > > > >>>> - https://github.com/javaee-samples/javaee7-samples <
> > > > >>>> https://github.com/javaee-samples/javaee7-samples>
> > > > >>>>
> > > > >>>>
> > > > >>>> --
> > > > >>>> David Blevins
> > > > >>>> http://twitter.com/dblevins
> > > > >>>> http://www.tomitribe.com
> > > > >>>>
> > > > >>>>> On Apr 28, 2016, at 6:19 AM, ross.cohen <
> ross.cohen.rc@gmail.com
> > >
> > > > >>>> wrote:
> > > > >>>>>
> > > > >>>>> Actually, it looks like a 7.0 release means different things to
> > > > >>>> different
> > > > >>>>> people. Romain, you took everyone's approval of the idea of a
> > > 7.0.0
> > > > >>>> release
> > > > >>>>> to be an approval of your particular version of a 7.0.0
> release,
> > > > which
> > > > >>>> it
> > > > >>>>> clearly was not. Looks to me like a finer-grained vote is
> needed
> > > to
> > > > >>>> figure
> > > > >>>>> out exactly what people want as part of 7.0.0 release.
> > > > >>>>>
> > > > >>>>> Personally, I think David is correct in saying that a release
> > > without
> > > > >>>> some
> > > > >>>>> kind of positive JEE 7 compatibility statement is a serious
> > > mistake.
> > > > >>>> I know
> > > > >>>>> the TCK is out of the question right now, but that simply means
> > you
> > > > >>>> need to
> > > > >>>>> invent an alternative compatibility statement:
> "Apache-Certified
> > > > >>>> Compliant
> > > > >>>>> to Web Profile Specifications" (or some such).
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> --
> > > > >>>>> View this message in context:
> > > > >>>>
> > > >
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
> > > > >>>>> Sent from the TomEE Dev mailing list archive at Nabble.com.
> > > > >>>>
> > > > >>>>
> > > >
> > > >
> > >
> >
> >
> >
>
>
>
> --
> Andy Gumbrecht
> https://twitter.com/AndyGeeDe
> http://www.tomitribe.com
>
Re: 7.0.0 release vote
Posted by Andy Gumbrecht <ag...@tomitribe.com>.
I still feel we are due another Milestone release until TomEE is a little
closer to the mark. There needs to be a really strong statement as to what
is available and what is not. There has already been some negative feedback
from power users that expected more, and were disappointed to find missing
features they expected to find merely based on the 7.x label - Wrongly
thinking that TomEE EE7 support was complete (Because we haven't really
told them).
Would there be a problem distributing the latest Hibernate (ASL) with
TomEE? - Even if some features would need unwrapping and documenting.
Andy.
On 2 May 2016 at 13:48, Roberto Cortez <ra...@yahoo.com.invalid> wrote:
> Some JAX-RS tests are using JPA 2.1 features which is not supported yet.
> From: John D. Ament <jo...@apache.org>
> To: dev@tomee.apache.org
> Sent: Monday, May 2, 2016 12:11 PM
> Subject: Re: 7.0.0 release vote
>
> On Mon, May 2, 2016 at 2:44 AM Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
> > Not portable test, jpa on not jpa tests etc. We pass really more tests
> > AFAIK.
>
>
> Could you elaborate on that a little? What is not portable? If you want to
> raise issues in our ticket system please feel free:
> https://github.com/javaee-samples/javaee7-samples/issues
>
> Or if you want to just say them, I can put them into github.
>
>
>
> > Le 2 mai 2016 05:48, "David Blevins" <da...@gmail.com> a écrit :
> >
> > > No worries on the many posts. Thank you for the Java EE 7 samples
> > checkup
> > > :)
> > >
> > > It appears we fail 35% of the JAX-RS 2.0 tests. Do we know what is
> > > preventing us from passing those tests?
> > >
> > >
> > > --
> > > David Blevins
> > > http://twitter.com/dblevins
> > > http://www.tomitribe.com
> > >
> > > > On May 1, 2016, at 6:42 PM, John D. Ament <jo...@apache.org>
> > wrote:
> > > >
> > > > Sorry for so many posts :-)
> > > >
> > > > TomEE Plus 7.0.0-M3 passes 238/338 tests in the suite.
> > > >
> > > > John
> > > >
> > > > On Sun, May 1, 2016 at 9:30 PM John D. Ament <jo...@apache.org>
> > > wrote:
> > > >
> > > >> I ended up changing the version and updating the code. I ran the
> > tests,
> > > >> you can see the output in this gist:
> > > >> https://gist.github.com/johnament/2443e79836605a913159b14295681536
> > > >>
> > > >> TomEE Plus fails at about 100 tests.
> > > >>
> > > >> John
> > > >>
> > > >>
> > > >> On Sun, May 1, 2016 at 8:10 PM John D. Ament <johndament@apache.org
> >
> > > >> wrote:
> > > >>
> > > >>> If it helps any, I can push up the latest TomEE version to the
> TomEE
> > > >>> profile:
> > > >>>
> > >
> >
> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
> > > >>>
> > > >>> John
> > > >>>
> > > >>>
> > > >>> On Sun, May 1, 2016 at 8:07 PM David Blevins <
> > david.blevins@gmail.com>
> > > >>> wrote:
> > > >>>
> > > >>>> In terms of statements of compliance, which of these Java EE 7
> > samples
> > > >>>> will currently run successfully?
> > > >>>>
> > > >>>> - https://github.com/javaee-samples/javaee7-samples <
> > > >>>> https://github.com/javaee-samples/javaee7-samples>
> > > >>>>
> > > >>>>
> > > >>>> --
> > > >>>> David Blevins
> > > >>>> http://twitter.com/dblevins
> > > >>>> http://www.tomitribe.com
> > > >>>>
> > > >>>>> On Apr 28, 2016, at 6:19 AM, ross.cohen <ross.cohen.rc@gmail.com
> >
> > > >>>> wrote:
> > > >>>>>
> > > >>>>> Actually, it looks like a 7.0 release means different things to
> > > >>>> different
> > > >>>>> people. Romain, you took everyone's approval of the idea of a
> > 7.0.0
> > > >>>> release
> > > >>>>> to be an approval of your particular version of a 7.0.0 release,
> > > which
> > > >>>> it
> > > >>>>> clearly was not. Looks to me like a finer-grained vote is needed
> > to
> > > >>>> figure
> > > >>>>> out exactly what people want as part of 7.0.0 release.
> > > >>>>>
> > > >>>>> Personally, I think David is correct in saying that a release
> > without
> > > >>>> some
> > > >>>>> kind of positive JEE 7 compatibility statement is a serious
> > mistake.
> > > >>>> I know
> > > >>>>> the TCK is out of the question right now, but that simply means
> you
> > > >>>> need to
> > > >>>>> invent an alternative compatibility statement: "Apache-Certified
> > > >>>> Compliant
> > > >>>>> to Web Profile Specifications" (or some such).
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> --
> > > >>>>> View this message in context:
> > > >>>>
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
> > > >>>>> Sent from the TomEE Dev mailing list archive at Nabble.com.
> > > >>>>
> > > >>>>
> > >
> > >
> >
>
>
>
--
Andy Gumbrecht
https://twitter.com/AndyGeeDe
http://www.tomitribe.com
Re: 7.0.0 release vote
Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
Some JAX-RS tests are using JPA 2.1 features which is not supported yet.
From: John D. Ament <jo...@apache.org>
To: dev@tomee.apache.org
Sent: Monday, May 2, 2016 12:11 PM
Subject: Re: 7.0.0 release vote
On Mon, May 2, 2016 at 2:44 AM Romain Manni-Bucau <rm...@gmail.com>
wrote:
> Not portable test, jpa on not jpa tests etc. We pass really more tests
> AFAIK.
Could you elaborate on that a little? What is not portable? If you want to
raise issues in our ticket system please feel free:
https://github.com/javaee-samples/javaee7-samples/issues
Or if you want to just say them, I can put them into github.
> Le 2 mai 2016 05:48, "David Blevins" <da...@gmail.com> a écrit :
>
> > No worries on the many posts. Thank you for the Java EE 7 samples
> checkup
> > :)
> >
> > It appears we fail 35% of the JAX-RS 2.0 tests. Do we know what is
> > preventing us from passing those tests?
> >
> >
> > --
> > David Blevins
> > http://twitter.com/dblevins
> > http://www.tomitribe.com
> >
> > > On May 1, 2016, at 6:42 PM, John D. Ament <jo...@apache.org>
> wrote:
> > >
> > > Sorry for so many posts :-)
> > >
> > > TomEE Plus 7.0.0-M3 passes 238/338 tests in the suite.
> > >
> > > John
> > >
> > > On Sun, May 1, 2016 at 9:30 PM John D. Ament <jo...@apache.org>
> > wrote:
> > >
> > >> I ended up changing the version and updating the code. I ran the
> tests,
> > >> you can see the output in this gist:
> > >> https://gist.github.com/johnament/2443e79836605a913159b14295681536
> > >>
> > >> TomEE Plus fails at about 100 tests.
> > >>
> > >> John
> > >>
> > >>
> > >> On Sun, May 1, 2016 at 8:10 PM John D. Ament <jo...@apache.org>
> > >> wrote:
> > >>
> > >>> If it helps any, I can push up the latest TomEE version to the TomEE
> > >>> profile:
> > >>>
> >
> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
> > >>>
> > >>> John
> > >>>
> > >>>
> > >>> On Sun, May 1, 2016 at 8:07 PM David Blevins <
> david.blevins@gmail.com>
> > >>> wrote:
> > >>>
> > >>>> In terms of statements of compliance, which of these Java EE 7
> samples
> > >>>> will currently run successfully?
> > >>>>
> > >>>> - https://github.com/javaee-samples/javaee7-samples <
> > >>>> https://github.com/javaee-samples/javaee7-samples>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> David Blevins
> > >>>> http://twitter.com/dblevins
> > >>>> http://www.tomitribe.com
> > >>>>
> > >>>>> On Apr 28, 2016, at 6:19 AM, ross.cohen <ro...@gmail.com>
> > >>>> wrote:
> > >>>>>
> > >>>>> Actually, it looks like a 7.0 release means different things to
> > >>>> different
> > >>>>> people. Romain, you took everyone's approval of the idea of a
> 7.0.0
> > >>>> release
> > >>>>> to be an approval of your particular version of a 7.0.0 release,
> > which
> > >>>> it
> > >>>>> clearly was not. Looks to me like a finer-grained vote is needed
> to
> > >>>> figure
> > >>>>> out exactly what people want as part of 7.0.0 release.
> > >>>>>
> > >>>>> Personally, I think David is correct in saying that a release
> without
> > >>>> some
> > >>>>> kind of positive JEE 7 compatibility statement is a serious
> mistake.
> > >>>> I know
> > >>>>> the TCK is out of the question right now, but that simply means you
> > >>>> need to
> > >>>>> invent an alternative compatibility statement: "Apache-Certified
> > >>>> Compliant
> > >>>>> to Web Profile Specifications" (or some such).
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> View this message in context:
> > >>>>
> >
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
> > >>>>> Sent from the TomEE Dev mailing list archive at Nabble.com.
> > >>>>
> > >>>>
> >
> >
>
Re: 7.0.0 release vote
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Fixed several in my fork - guess it has been merged but there was too much
issues to fix them all alone. The build output shows what it is generally -
excepted when the tests are not passing at all like angular example was.
Le 2 mai 2016 13:11, "John D. Ament" <jo...@apache.org> a écrit :
> On Mon, May 2, 2016 at 2:44 AM Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
> > Not portable test, jpa on not jpa tests etc. We pass really more tests
> > AFAIK.
>
>
> Could you elaborate on that a little? What is not portable? If you want to
> raise issues in our ticket system please feel free:
> https://github.com/javaee-samples/javaee7-samples/issues
>
> Or if you want to just say them, I can put them into github.
>
>
>
> > Le 2 mai 2016 05:48, "David Blevins" <da...@gmail.com> a écrit :
> >
> > > No worries on the many posts. Thank you for the Java EE 7 samples
> > checkup
> > > :)
> > >
> > > It appears we fail 35% of the JAX-RS 2.0 tests. Do we know what is
> > > preventing us from passing those tests?
> > >
> > >
> > > --
> > > David Blevins
> > > http://twitter.com/dblevins
> > > http://www.tomitribe.com
> > >
> > > > On May 1, 2016, at 6:42 PM, John D. Ament <jo...@apache.org>
> > wrote:
> > > >
> > > > Sorry for so many posts :-)
> > > >
> > > > TomEE Plus 7.0.0-M3 passes 238/338 tests in the suite.
> > > >
> > > > John
> > > >
> > > > On Sun, May 1, 2016 at 9:30 PM John D. Ament <jo...@apache.org>
> > > wrote:
> > > >
> > > >> I ended up changing the version and updating the code. I ran the
> > tests,
> > > >> you can see the output in this gist:
> > > >> https://gist.github.com/johnament/2443e79836605a913159b14295681536
> > > >>
> > > >> TomEE Plus fails at about 100 tests.
> > > >>
> > > >> John
> > > >>
> > > >>
> > > >> On Sun, May 1, 2016 at 8:10 PM John D. Ament <johndament@apache.org
> >
> > > >> wrote:
> > > >>
> > > >>> If it helps any, I can push up the latest TomEE version to the
> TomEE
> > > >>> profile:
> > > >>>
> > >
> >
> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
> > > >>>
> > > >>> John
> > > >>>
> > > >>>
> > > >>> On Sun, May 1, 2016 at 8:07 PM David Blevins <
> > david.blevins@gmail.com>
> > > >>> wrote:
> > > >>>
> > > >>>> In terms of statements of compliance, which of these Java EE 7
> > samples
> > > >>>> will currently run successfully?
> > > >>>>
> > > >>>> - https://github.com/javaee-samples/javaee7-samples <
> > > >>>> https://github.com/javaee-samples/javaee7-samples>
> > > >>>>
> > > >>>>
> > > >>>> --
> > > >>>> David Blevins
> > > >>>> http://twitter.com/dblevins
> > > >>>> http://www.tomitribe.com
> > > >>>>
> > > >>>>> On Apr 28, 2016, at 6:19 AM, ross.cohen <ross.cohen.rc@gmail.com
> >
> > > >>>> wrote:
> > > >>>>>
> > > >>>>> Actually, it looks like a 7.0 release means different things to
> > > >>>> different
> > > >>>>> people. Romain, you took everyone's approval of the idea of a
> > 7.0.0
> > > >>>> release
> > > >>>>> to be an approval of your particular version of a 7.0.0 release,
> > > which
> > > >>>> it
> > > >>>>> clearly was not. Looks to me like a finer-grained vote is
> needed
> > to
> > > >>>> figure
> > > >>>>> out exactly what people want as part of 7.0.0 release.
> > > >>>>>
> > > >>>>> Personally, I think David is correct in saying that a release
> > without
> > > >>>> some
> > > >>>>> kind of positive JEE 7 compatibility statement is a serious
> > mistake.
> > > >>>> I know
> > > >>>>> the TCK is out of the question right now, but that simply means
> you
> > > >>>> need to
> > > >>>>> invent an alternative compatibility statement: "Apache-Certified
> > > >>>> Compliant
> > > >>>>> to Web Profile Specifications" (or some such).
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> --
> > > >>>>> View this message in context:
> > > >>>>
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
> > > >>>>> Sent from the TomEE Dev mailing list archive at Nabble.com.
> > > >>>>
> > > >>>>
> > >
> > >
> >
>
Re: 7.0.0 release vote
Posted by "John D. Ament" <jo...@apache.org>.
On Mon, May 2, 2016 at 2:44 AM Romain Manni-Bucau <rm...@gmail.com>
wrote:
> Not portable test, jpa on not jpa tests etc. We pass really more tests
> AFAIK.
Could you elaborate on that a little? What is not portable? If you want to
raise issues in our ticket system please feel free:
https://github.com/javaee-samples/javaee7-samples/issues
Or if you want to just say them, I can put them into github.
> Le 2 mai 2016 05:48, "David Blevins" <da...@gmail.com> a écrit :
>
> > No worries on the many posts. Thank you for the Java EE 7 samples
> checkup
> > :)
> >
> > It appears we fail 35% of the JAX-RS 2.0 tests. Do we know what is
> > preventing us from passing those tests?
> >
> >
> > --
> > David Blevins
> > http://twitter.com/dblevins
> > http://www.tomitribe.com
> >
> > > On May 1, 2016, at 6:42 PM, John D. Ament <jo...@apache.org>
> wrote:
> > >
> > > Sorry for so many posts :-)
> > >
> > > TomEE Plus 7.0.0-M3 passes 238/338 tests in the suite.
> > >
> > > John
> > >
> > > On Sun, May 1, 2016 at 9:30 PM John D. Ament <jo...@apache.org>
> > wrote:
> > >
> > >> I ended up changing the version and updating the code. I ran the
> tests,
> > >> you can see the output in this gist:
> > >> https://gist.github.com/johnament/2443e79836605a913159b14295681536
> > >>
> > >> TomEE Plus fails at about 100 tests.
> > >>
> > >> John
> > >>
> > >>
> > >> On Sun, May 1, 2016 at 8:10 PM John D. Ament <jo...@apache.org>
> > >> wrote:
> > >>
> > >>> If it helps any, I can push up the latest TomEE version to the TomEE
> > >>> profile:
> > >>>
> >
> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
> > >>>
> > >>> John
> > >>>
> > >>>
> > >>> On Sun, May 1, 2016 at 8:07 PM David Blevins <
> david.blevins@gmail.com>
> > >>> wrote:
> > >>>
> > >>>> In terms of statements of compliance, which of these Java EE 7
> samples
> > >>>> will currently run successfully?
> > >>>>
> > >>>> - https://github.com/javaee-samples/javaee7-samples <
> > >>>> https://github.com/javaee-samples/javaee7-samples>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> David Blevins
> > >>>> http://twitter.com/dblevins
> > >>>> http://www.tomitribe.com
> > >>>>
> > >>>>> On Apr 28, 2016, at 6:19 AM, ross.cohen <ro...@gmail.com>
> > >>>> wrote:
> > >>>>>
> > >>>>> Actually, it looks like a 7.0 release means different things to
> > >>>> different
> > >>>>> people. Romain, you took everyone's approval of the idea of a
> 7.0.0
> > >>>> release
> > >>>>> to be an approval of your particular version of a 7.0.0 release,
> > which
> > >>>> it
> > >>>>> clearly was not. Looks to me like a finer-grained vote is needed
> to
> > >>>> figure
> > >>>>> out exactly what people want as part of 7.0.0 release.
> > >>>>>
> > >>>>> Personally, I think David is correct in saying that a release
> without
> > >>>> some
> > >>>>> kind of positive JEE 7 compatibility statement is a serious
> mistake.
> > >>>> I know
> > >>>>> the TCK is out of the question right now, but that simply means you
> > >>>> need to
> > >>>>> invent an alternative compatibility statement: "Apache-Certified
> > >>>> Compliant
> > >>>>> to Web Profile Specifications" (or some such).
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> View this message in context:
> > >>>>
> >
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
> > >>>>> Sent from the TomEE Dev mailing list archive at Nabble.com.
> > >>>>
> > >>>>
> >
> >
>
Re: 7.0.0 release vote
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Not portable test, jpa on not jpa tests etc. We pass really more tests
AFAIK.
Le 2 mai 2016 05:48, "David Blevins" <da...@gmail.com> a écrit :
> No worries on the many posts. Thank you for the Java EE 7 samples checkup
> :)
>
> It appears we fail 35% of the JAX-RS 2.0 tests. Do we know what is
> preventing us from passing those tests?
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
> > On May 1, 2016, at 6:42 PM, John D. Ament <jo...@apache.org> wrote:
> >
> > Sorry for so many posts :-)
> >
> > TomEE Plus 7.0.0-M3 passes 238/338 tests in the suite.
> >
> > John
> >
> > On Sun, May 1, 2016 at 9:30 PM John D. Ament <jo...@apache.org>
> wrote:
> >
> >> I ended up changing the version and updating the code. I ran the tests,
> >> you can see the output in this gist:
> >> https://gist.github.com/johnament/2443e79836605a913159b14295681536
> >>
> >> TomEE Plus fails at about 100 tests.
> >>
> >> John
> >>
> >>
> >> On Sun, May 1, 2016 at 8:10 PM John D. Ament <jo...@apache.org>
> >> wrote:
> >>
> >>> If it helps any, I can push up the latest TomEE version to the TomEE
> >>> profile:
> >>>
> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
> >>>
> >>> John
> >>>
> >>>
> >>> On Sun, May 1, 2016 at 8:07 PM David Blevins <da...@gmail.com>
> >>> wrote:
> >>>
> >>>> In terms of statements of compliance, which of these Java EE 7 samples
> >>>> will currently run successfully?
> >>>>
> >>>> - https://github.com/javaee-samples/javaee7-samples <
> >>>> https://github.com/javaee-samples/javaee7-samples>
> >>>>
> >>>>
> >>>> --
> >>>> David Blevins
> >>>> http://twitter.com/dblevins
> >>>> http://www.tomitribe.com
> >>>>
> >>>>> On Apr 28, 2016, at 6:19 AM, ross.cohen <ro...@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>> Actually, it looks like a 7.0 release means different things to
> >>>> different
> >>>>> people. Romain, you took everyone's approval of the idea of a 7.0.0
> >>>> release
> >>>>> to be an approval of your particular version of a 7.0.0 release,
> which
> >>>> it
> >>>>> clearly was not. Looks to me like a finer-grained vote is needed to
> >>>> figure
> >>>>> out exactly what people want as part of 7.0.0 release.
> >>>>>
> >>>>> Personally, I think David is correct in saying that a release without
> >>>> some
> >>>>> kind of positive JEE 7 compatibility statement is a serious mistake.
> >>>> I know
> >>>>> the TCK is out of the question right now, but that simply means you
> >>>> need to
> >>>>> invent an alternative compatibility statement: "Apache-Certified
> >>>> Compliant
> >>>>> to Web Profile Specifications" (or some such).
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> View this message in context:
> >>>>
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
> >>>>> Sent from the TomEE Dev mailing list archive at Nabble.com.
> >>>>
> >>>>
>
>
Re: 7.0.0 release vote
Posted by David Blevins <da...@gmail.com>.
No worries on the many posts. Thank you for the Java EE 7 samples checkup :)
It appears we fail 35% of the JAX-RS 2.0 tests. Do we know what is preventing us from passing those tests?
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
> On May 1, 2016, at 6:42 PM, John D. Ament <jo...@apache.org> wrote:
>
> Sorry for so many posts :-)
>
> TomEE Plus 7.0.0-M3 passes 238/338 tests in the suite.
>
> John
>
> On Sun, May 1, 2016 at 9:30 PM John D. Ament <jo...@apache.org> wrote:
>
>> I ended up changing the version and updating the code. I ran the tests,
>> you can see the output in this gist:
>> https://gist.github.com/johnament/2443e79836605a913159b14295681536
>>
>> TomEE Plus fails at about 100 tests.
>>
>> John
>>
>>
>> On Sun, May 1, 2016 at 8:10 PM John D. Ament <jo...@apache.org>
>> wrote:
>>
>>> If it helps any, I can push up the latest TomEE version to the TomEE
>>> profile:
>>> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
>>>
>>> John
>>>
>>>
>>> On Sun, May 1, 2016 at 8:07 PM David Blevins <da...@gmail.com>
>>> wrote:
>>>
>>>> In terms of statements of compliance, which of these Java EE 7 samples
>>>> will currently run successfully?
>>>>
>>>> - https://github.com/javaee-samples/javaee7-samples <
>>>> https://github.com/javaee-samples/javaee7-samples>
>>>>
>>>>
>>>> --
>>>> David Blevins
>>>> http://twitter.com/dblevins
>>>> http://www.tomitribe.com
>>>>
>>>>> On Apr 28, 2016, at 6:19 AM, ross.cohen <ro...@gmail.com>
>>>> wrote:
>>>>>
>>>>> Actually, it looks like a 7.0 release means different things to
>>>> different
>>>>> people. Romain, you took everyone's approval of the idea of a 7.0.0
>>>> release
>>>>> to be an approval of your particular version of a 7.0.0 release, which
>>>> it
>>>>> clearly was not. Looks to me like a finer-grained vote is needed to
>>>> figure
>>>>> out exactly what people want as part of 7.0.0 release.
>>>>>
>>>>> Personally, I think David is correct in saying that a release without
>>>> some
>>>>> kind of positive JEE 7 compatibility statement is a serious mistake.
>>>> I know
>>>>> the TCK is out of the question right now, but that simply means you
>>>> need to
>>>>> invent an alternative compatibility statement: "Apache-Certified
>>>> Compliant
>>>>> to Web Profile Specifications" (or some such).
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
>>>>> Sent from the TomEE Dev mailing list archive at Nabble.com.
>>>>
>>>>
Re: 7.0.0 release vote
Posted by "John D. Ament" <jo...@apache.org>.
Sorry for so many posts :-)
TomEE Plus 7.0.0-M3 passes 238/338 tests in the suite.
John
On Sun, May 1, 2016 at 9:30 PM John D. Ament <jo...@apache.org> wrote:
> I ended up changing the version and updating the code. I ran the tests,
> you can see the output in this gist:
> https://gist.github.com/johnament/2443e79836605a913159b14295681536
>
> TomEE Plus fails at about 100 tests.
>
> John
>
>
> On Sun, May 1, 2016 at 8:10 PM John D. Ament <jo...@apache.org>
> wrote:
>
>> If it helps any, I can push up the latest TomEE version to the TomEE
>> profile:
>> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
>>
>> John
>>
>>
>> On Sun, May 1, 2016 at 8:07 PM David Blevins <da...@gmail.com>
>> wrote:
>>
>>> In terms of statements of compliance, which of these Java EE 7 samples
>>> will currently run successfully?
>>>
>>> - https://github.com/javaee-samples/javaee7-samples <
>>> https://github.com/javaee-samples/javaee7-samples>
>>>
>>>
>>> --
>>> David Blevins
>>> http://twitter.com/dblevins
>>> http://www.tomitribe.com
>>>
>>> > On Apr 28, 2016, at 6:19 AM, ross.cohen <ro...@gmail.com>
>>> wrote:
>>> >
>>> > Actually, it looks like a 7.0 release means different things to
>>> different
>>> > people. Romain, you took everyone's approval of the idea of a 7.0.0
>>> release
>>> > to be an approval of your particular version of a 7.0.0 release, which
>>> it
>>> > clearly was not. Looks to me like a finer-grained vote is needed to
>>> figure
>>> > out exactly what people want as part of 7.0.0 release.
>>> >
>>> > Personally, I think David is correct in saying that a release without
>>> some
>>> > kind of positive JEE 7 compatibility statement is a serious mistake.
>>> I know
>>> > the TCK is out of the question right now, but that simply means you
>>> need to
>>> > invent an alternative compatibility statement: "Apache-Certified
>>> Compliant
>>> > to Web Profile Specifications" (or some such).
>>> >
>>> >
>>> >
>>> > --
>>> > View this message in context:
>>> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
>>> > Sent from the TomEE Dev mailing list archive at Nabble.com.
>>>
>>>
Re: 7.0.0 release vote
Posted by "John D. Ament" <jo...@apache.org>.
I ended up changing the version and updating the code. I ran the tests,
you can see the output in this gist:
https://gist.github.com/johnament/2443e79836605a913159b14295681536
TomEE Plus fails at about 100 tests.
John
On Sun, May 1, 2016 at 8:10 PM John D. Ament <jo...@apache.org> wrote:
> If it helps any, I can push up the latest TomEE version to the TomEE
> profile:
> https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
>
> John
>
>
> On Sun, May 1, 2016 at 8:07 PM David Blevins <da...@gmail.com>
> wrote:
>
>> In terms of statements of compliance, which of these Java EE 7 samples
>> will currently run successfully?
>>
>> - https://github.com/javaee-samples/javaee7-samples <
>> https://github.com/javaee-samples/javaee7-samples>
>>
>>
>> --
>> David Blevins
>> http://twitter.com/dblevins
>> http://www.tomitribe.com
>>
>> > On Apr 28, 2016, at 6:19 AM, ross.cohen <ro...@gmail.com>
>> wrote:
>> >
>> > Actually, it looks like a 7.0 release means different things to
>> different
>> > people. Romain, you took everyone's approval of the idea of a 7.0.0
>> release
>> > to be an approval of your particular version of a 7.0.0 release, which
>> it
>> > clearly was not. Looks to me like a finer-grained vote is needed to
>> figure
>> > out exactly what people want as part of 7.0.0 release.
>> >
>> > Personally, I think David is correct in saying that a release without
>> some
>> > kind of positive JEE 7 compatibility statement is a serious mistake. I
>> know
>> > the TCK is out of the question right now, but that simply means you
>> need to
>> > invent an alternative compatibility statement: "Apache-Certified
>> Compliant
>> > to Web Profile Specifications" (or some such).
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
>> > Sent from the TomEE Dev mailing list archive at Nabble.com.
>>
>>
Re: 7.0.0 release vote
Posted by "John D. Ament" <jo...@apache.org>.
If it helps any, I can push up the latest TomEE version to the TomEE
profile:
https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L690
John
On Sun, May 1, 2016 at 8:07 PM David Blevins <da...@gmail.com>
wrote:
> In terms of statements of compliance, which of these Java EE 7 samples
> will currently run successfully?
>
> - https://github.com/javaee-samples/javaee7-samples <
> https://github.com/javaee-samples/javaee7-samples>
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
> > On Apr 28, 2016, at 6:19 AM, ross.cohen <ro...@gmail.com> wrote:
> >
> > Actually, it looks like a 7.0 release means different things to different
> > people. Romain, you took everyone's approval of the idea of a 7.0.0
> release
> > to be an approval of your particular version of a 7.0.0 release, which it
> > clearly was not. Looks to me like a finer-grained vote is needed to
> figure
> > out exactly what people want as part of 7.0.0 release.
> >
> > Personally, I think David is correct in saying that a release without
> some
> > kind of positive JEE 7 compatibility statement is a serious mistake. I
> know
> > the TCK is out of the question right now, but that simply means you need
> to
> > invent an alternative compatibility statement: "Apache-Certified
> Compliant
> > to Web Profile Specifications" (or some such).
> >
> >
> >
> > --
> > View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/7-0-0-release-vote-tp4678284.html
> > Sent from the TomEE Dev mailing list archive at Nabble.com.
>
>