For me the choices are more restricted and B and C are not options.

Version 2 and 5 are the most relevant options IMO for the project
consistency but 2 is almost not possible for openejb. 5 would be hardly
doable for the project "image" for tomee.

In one word i d keep it this way evzn if not perfect. The mvn part is not
the hurting one when releasing (we all know how to fix it in less than 10mn
with bash) so not sure we need to enhance it. Other parts are and the one
we should fix from my humble opinion.

Le 29 avr. 2015 12:25, "Jean-Louis Monteiro" <[email protected]> a
écrit :
>
> Hey Mark,
>
> I agree with the overall feeling and diagnostic.
> I have seen this topic many times raising the list without consensus or
> conclusion.
>
> I think we can start again doing pros/cons discussion but I'm not sure
it's
> gonna help more.
> We have had enough discussions I would say, so now is probably time to
open
> a [VOTE] thread and publish [RESULT].
>
> Back in 2011, we were already talking about this and we were kinda afraid
> to announce a month after the TomEE 1.0.0, we would jump to TomEE 5, 6 or
> whatever.
> The jump was to big and would have probably been bad for the project.
>
> 4 years after and with a couple of releases and more maturity, it's
> probably no more an issue.
> I must admit that I also love the idea of having something bound to Java
EE
> (aka Option B).
>
> Jean-Louis
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Wed, Apr 29, 2015 at 9:14 AM, Mark Struberg <[email protected]> wrote:
>
> > the more correct approach would be to FINALLY finish the version
> > discussion.
> >
> >
> > It kind of breaks many things that we do not have a single version but
2.
> > openejb-4.7.2 + tomee-1.7.
> > * User always break their dependencies as they have to maintain
different
> > versions all over their poms.
> > * We cannot easily release as there is no autoVersionSubModules for that
> > case.
> > * Things like that now happen as you need to manually pimp some other
poms
> > to make it fit together.
> >
> > This is really a bit schizophrenic in my opinion.
> >
> > I already vetted for using the same version number on both parts. We
> > cannot go below 4.7, so this leaves 3 options
> >
> > A.) Keep the headache we have with 2 different versions
> > B.) Use 7.x for the EE7 approach (what currently is in trunk aka
TomEE-2)
> > C.) Use 8.x to reflect it is base don Tomcat8
> >
> > I’d personally go for B.
> > What are the pros and cons?
> >
> > LieGrue,
> > strub
> >
> >
> >
> > > Am 28.04.2015 um 17:45 schrieb Romain Manni-Bucau <
[email protected]
> > >:
> > >
> > > yes, think it is the kind of things we have to do in the release
branch
> > >
> > >
> > > 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>
> > >
> > > 2015-04-28 17:39 GMT+02:00 Jonathan Gallimore <
[email protected]
> > >:
> > >
> > >> Will revert that as soon as I can. Happy to try not pushing that
commit
> > if
> > >> I have to try again.
> > >>
> > >> Jon
> > >>
> > >> On Tue, Apr 28, 2015 at 8:36 AM, Romain Manni-Bucau <
> > [email protected]
> > >>>
> > >> wrote:
> > >>
> > >>> why does it hit our repo? it breaks projects depending on us (like
> > >>> deltaspike)
> > >>>
> > >>> 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>
> > >>>
> > >>> ---------- Forwarded message ----------
> > >>> From: <[email protected]>
> > >>> Date: 2015-04-28 17:33 GMT+02:00
> > >>> Subject: tomee git commit: Updating variables for release
> > >>> To: [email protected]
> > >>>
> > >>>
> > >>> Repository: tomee
> > >>> Updated Branches:
> > >>>  refs/heads/tomee-1.7.x 37d66623e -> 88910204c
> > >>>
> > >>>
> > >>> Updating variables for release
> > >>>
> > >>>
> > >>> Project: http://git-wip-us.apache.org/repos/asf/tomee/repo
> > >>> Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/88910204
> > >>> Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/88910204
> > >>> Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/88910204
> > >>>
> > >>> Branch: refs/heads/tomee-1.7.x
> > >>> Commit: 88910204c6e93e6ab39cda542075a0074ae05f95
> > >>> Parents: 37d6662
> > >>> Author: Jonathan Gallimore <[email protected]>
> > >>> Authored: Tue Apr 28 15:32:59 2015 +0000
> > >>> Committer: Jonathan Gallimore <[email protected]>
> > >>> Committed: Tue Apr 28 15:32:59 2015 +0000
> > >>>
> > >>>
----------------------------------------------------------------------
> > >>> pom.xml | 4 ++--
> > >>> 1 file changed, 2 insertions(+), 2 deletions(-)
> > >>>
----------------------------------------------------------------------
> > >>>
> > >>>
> > >>> http://git-wip-us.apache.org/repos/asf/tomee/blob/88910204/pom.xml
> > >>>
----------------------------------------------------------------------
> > >>> diff --git a/pom.xml b/pom.xml
> > >>> index 012e22f..83a1501 100644
> > >>> --- a/pom.xml
> > >>> +++ b/pom.xml
> > >>> @@ -97,8 +97,8 @@
> > >>>
> > >>
<test.complexity.coverage.minimun>0</test.complexity.coverage.minimun>
> > >>>     <test.branch.coverage.minimun>0</test.branch.coverage.minimun>
> > >>>     <test.coverage.skip>false</test.coverage.skip>
> > >>> -    <openejb.version>4.7.2-SNAPSHOT</openejb.version>
> > >>> -    <tomee.version>1.7.2-SNAPSHOT</tomee.version>
> > >>> +    <openejb.version>4.7.2</openejb.version>
> > >>> +    <tomee.version>1.7.2</tomee.version>
> > >>>
> > >>>     <openjpa.version>2.4.0</openjpa.version>
> > >>>
> > >>>
> > <org.apache.openwebbeans.version>1.2.7</org.apache.openwebbeans.version>
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> Jonathan Gallimore
> > >> http://twitter.com/jongallimore
> > >> http://www.tomitribe.com
> > >>
> >
> >

Reply via email to