1.6 to be the last release to support Java 1.6?

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

1.6 to be the last release to support Java 1.6?

John D. Ament
Hey guys,

I've brought this topic up before without much positive response.  I figure
I'll bring it up again.

I'd like to propose that DeltaSpike 1.6 be the last minor release to
support Java 1.6.  I suspect that most users are already using Java 7 or
higher.  None of our builds in CI (builds.apache.org) currently run on 1.6
either, so while we can say from a syntax standpoint we're 1.6 compliant
I'm not sure we can say from a JDK Library standpoint we don't rely on
anything from Java 7.

We're one of the few projects that probably still supports Java 6 as a
mainline development, so I was hoping we could just cut 1.6 as 1.6
compliant, if we need to cut patch releases of 1.6 to apply patches, but
with DeltaSpike 1.7 and on, focus on Java 7 and up.

John
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

Thomas Andraschko-2
basically +1
Most of our customers are using 1.7 since this year.

I just wonder whats the benefit for us?
I think there are no language features which would improve our code base.

2016-03-25 3:25 GMT+01:00 John D. Ament <[hidden email]>:

> Hey guys,
>
> I've brought this topic up before without much positive response.  I figure
> I'll bring it up again.
>
> I'd like to propose that DeltaSpike 1.6 be the last minor release to
> support Java 1.6.  I suspect that most users are already using Java 7 or
> higher.  None of our builds in CI (builds.apache.org) currently run on 1.6
> either, so while we can say from a syntax standpoint we're 1.6 compliant
> I'm not sure we can say from a JDK Library standpoint we don't rely on
> anything from Java 7.
>
> We're one of the few projects that probably still supports Java 6 as a
> mainline development, so I was hoping we could just cut 1.6 as 1.6
> compliant, if we need to cut patch releases of 1.6 to apply patches, but
> with DeltaSpike 1.7 and on, focus on Java 7 and up.
>
> John
>
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

Gerhard Petracek
Administrator
i agree with thomas

regards,
gerhard



2016-03-25 9:23 GMT+01:00 Thomas Andraschko <[hidden email]>:

> basically +1
> Most of our customers are using 1.7 since this year.
>
> I just wonder whats the benefit for us?
> I think there are no language features which would improve our code base.
>
> 2016-03-25 3:25 GMT+01:00 John D. Ament <[hidden email]>:
>
> > Hey guys,
> >
> > I've brought this topic up before without much positive response.  I
> figure
> > I'll bring it up again.
> >
> > I'd like to propose that DeltaSpike 1.6 be the last minor release to
> > support Java 1.6.  I suspect that most users are already using Java 7 or
> > higher.  None of our builds in CI (builds.apache.org) currently run on
> 1.6
> > either, so while we can say from a syntax standpoint we're 1.6 compliant
> > I'm not sure we can say from a JDK Library standpoint we don't rely on
> > anything from Java 7.
> >
> > We're one of the few projects that probably still supports Java 6 as a
> > mainline development, so I was hoping we could just cut 1.6 as 1.6
> > compliant, if we need to cut patch releases of 1.6 to apply patches, but
> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
> >
> > John
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

Romain Manni-Bucau
+0

j6 is EOL so shouldn't really be used anymore and didnt use it since
months but excepted multi catch feature j7 will not help us a lot I
think  - that's for dev side. For CI side I think it can make sense to
get rid of the j6 constraint but I don't know if that's really a
constraint for us.

Romain Manni-Bucau
@rmannibucau |  Blog | Github | LinkedIn | Tomitriber


2016-03-25 9:35 GMT+01:00 Gerhard Petracek <[hidden email]>:

> i agree with thomas
>
> regards,
> gerhard
>
>
>
> 2016-03-25 9:23 GMT+01:00 Thomas Andraschko <[hidden email]>:
>
>> basically +1
>> Most of our customers are using 1.7 since this year.
>>
>> I just wonder whats the benefit for us?
>> I think there are no language features which would improve our code base.
>>
>> 2016-03-25 3:25 GMT+01:00 John D. Ament <[hidden email]>:
>>
>> > Hey guys,
>> >
>> > I've brought this topic up before without much positive response.  I
>> figure
>> > I'll bring it up again.
>> >
>> > I'd like to propose that DeltaSpike 1.6 be the last minor release to
>> > support Java 1.6.  I suspect that most users are already using Java 7 or
>> > higher.  None of our builds in CI (builds.apache.org) currently run on
>> 1.6
>> > either, so while we can say from a syntax standpoint we're 1.6 compliant
>> > I'm not sure we can say from a JDK Library standpoint we don't rely on
>> > anything from Java 7.
>> >
>> > We're one of the few projects that probably still supports Java 6 as a
>> > mainline development, so I was hoping we could just cut 1.6 as 1.6
>> > compliant, if we need to cut patch releases of 1.6 to apply patches, but
>> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
>> >
>> > John
>> >
>>
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

John D. Ament
In reply to this post by Thomas Andraschko-2
To me, dropping support for Java 6 doesn't mean rewriting the code base to
only be compliant with Java 7 and up.

It does allow for some new stuff in our codebase, if we want to go back and
clean it up:

- try-with-resources
- automatic type inference on generics.

But those are just clean ups, no real new functionality.

John

On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
[hidden email]> wrote:

> basically +1
> Most of our customers are using 1.7 since this year.
>
> I just wonder whats the benefit for us?
> I think there are no language features which would improve our code base.
>
> 2016-03-25 3:25 GMT+01:00 John D. Ament <[hidden email]>:
>
> > Hey guys,
> >
> > I've brought this topic up before without much positive response.  I
> figure
> > I'll bring it up again.
> >
> > I'd like to propose that DeltaSpike 1.6 be the last minor release to
> > support Java 1.6.  I suspect that most users are already using Java 7 or
> > higher.  None of our builds in CI (builds.apache.org) currently run on
> 1.6
> > either, so while we can say from a syntax standpoint we're 1.6 compliant
> > I'm not sure we can say from a JDK Library standpoint we don't rely on
> > anything from Java 7.
> >
> > We're one of the few projects that probably still supports Java 6 as a
> > mainline development, so I was hoping we could just cut 1.6 as 1.6
> > compliant, if we need to cut patch releases of 1.6 to apply patches, but
> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
> >
> > John
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

John D. Ament
BTW, if we do agree to drop Java 6, do we create a 1.6 maintenance branch
or just leave the tag, and if need be cut a bug fix release then?

John

On Fri, Mar 25, 2016 at 8:06 AM John D. Ament <[hidden email]> wrote:

> To me, dropping support for Java 6 doesn't mean rewriting the code base to
> only be compliant with Java 7 and up.
>
> It does allow for some new stuff in our codebase, if we want to go back
> and clean it up:
>
> - try-with-resources
> - automatic type inference on generics.
>
> But those are just clean ups, no real new functionality.
>
> John
>
>
> On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
> [hidden email]> wrote:
>
>> basically +1
>> Most of our customers are using 1.7 since this year.
>>
>> I just wonder whats the benefit for us?
>> I think there are no language features which would improve our code base.
>>
>> 2016-03-25 3:25 GMT+01:00 John D. Ament <[hidden email]>:
>>
>> > Hey guys,
>> >
>> > I've brought this topic up before without much positive response.  I
>> figure
>> > I'll bring it up again.
>> >
>> > I'd like to propose that DeltaSpike 1.6 be the last minor release to
>> > support Java 1.6.  I suspect that most users are already using Java 7 or
>> > higher.  None of our builds in CI (builds.apache.org) currently run on
>> 1.6
>> > either, so while we can say from a syntax standpoint we're 1.6 compliant
>> > I'm not sure we can say from a JDK Library standpoint we don't rely on
>> > anything from Java 7.
>> >
>> > We're one of the few projects that probably still supports Java 6 as a
>> > mainline development, so I was hoping we could just cut 1.6 as 1.6
>> > compliant, if we need to cut patch releases of 1.6 to apply patches, but
>> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
>> >
>> > John
>> >
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

Harald Wellmann
+1

2016-03-25 13:09 GMT+01:00 John D. Ament <[hidden email]>:

> BTW, if we do agree to drop Java 6, do we create a 1.6 maintenance branch
> or just leave the tag, and if need be cut a bug fix release then?
>
> John
>
> On Fri, Mar 25, 2016 at 8:06 AM John D. Ament <[hidden email]>
> wrote:
>
> > To me, dropping support for Java 6 doesn't mean rewriting the code base
> to
> > only be compliant with Java 7 and up.
> >
> > It does allow for some new stuff in our codebase, if we want to go back
> > and clean it up:
> >
> > - try-with-resources
> > - automatic type inference on generics.
> >
> > But those are just clean ups, no real new functionality.
> >
> > John
> >
> >
> > On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
> > [hidden email]> wrote:
> >
> >> basically +1
> >> Most of our customers are using 1.7 since this year.
> >>
> >> I just wonder whats the benefit for us?
> >> I think there are no language features which would improve our code
> base.
> >>
> >> 2016-03-25 3:25 GMT+01:00 John D. Ament <[hidden email]>:
> >>
> >> > Hey guys,
> >> >
> >> > I've brought this topic up before without much positive response.  I
> >> figure
> >> > I'll bring it up again.
> >> >
> >> > I'd like to propose that DeltaSpike 1.6 be the last minor release to
> >> > support Java 1.6.  I suspect that most users are already using Java 7
> or
> >> > higher.  None of our builds in CI (builds.apache.org) currently run
> on
> >> 1.6
> >> > either, so while we can say from a syntax standpoint we're 1.6
> compliant
> >> > I'm not sure we can say from a JDK Library standpoint we don't rely on
> >> > anything from Java 7.
> >> >
> >> > We're one of the few projects that probably still supports Java 6 as a
> >> > mainline development, so I was hoping we could just cut 1.6 as 1.6
> >> > compliant, if we need to cut patch releases of 1.6 to apply patches,
> but
> >> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
> >> >
> >> > John
> >> >
> >>
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

John D. Ament
All,

Here's the announcement I'm going to post to the site.  Let me know if you
have any comments on the change.

== End of Support Announcement - Java 6


The Apache DeltaSpike team has decided to begin dropping support for

Java 6.  The next release, 1.6.0 is currently planned to be the last

minor release to support Java 6.  Patch fixes on 1.6.x will continue

to support it, but our next minor release (1.7.0) will require

Java 7 at a minimum.



On Fri, Mar 25, 2016 at 8:17 AM Harald Wellmann <[hidden email]>
wrote:

> +1
>
> 2016-03-25 13:09 GMT+01:00 John D. Ament <[hidden email]>:
>
> > BTW, if we do agree to drop Java 6, do we create a 1.6 maintenance branch
> > or just leave the tag, and if need be cut a bug fix release then?
> >
> > John
> >
> > On Fri, Mar 25, 2016 at 8:06 AM John D. Ament <[hidden email]>
> > wrote:
> >
> > > To me, dropping support for Java 6 doesn't mean rewriting the code base
> > to
> > > only be compliant with Java 7 and up.
> > >
> > > It does allow for some new stuff in our codebase, if we want to go back
> > > and clean it up:
> > >
> > > - try-with-resources
> > > - automatic type inference on generics.
> > >
> > > But those are just clean ups, no real new functionality.
> > >
> > > John
> > >
> > >
> > > On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
> > > [hidden email]> wrote:
> > >
> > >> basically +1
> > >> Most of our customers are using 1.7 since this year.
> > >>
> > >> I just wonder whats the benefit for us?
> > >> I think there are no language features which would improve our code
> > base.
> > >>
> > >> 2016-03-25 3:25 GMT+01:00 John D. Ament <[hidden email]>:
> > >>
> > >> > Hey guys,
> > >> >
> > >> > I've brought this topic up before without much positive response.  I
> > >> figure
> > >> > I'll bring it up again.
> > >> >
> > >> > I'd like to propose that DeltaSpike 1.6 be the last minor release to
> > >> > support Java 1.6.  I suspect that most users are already using Java
> 7
> > or
> > >> > higher.  None of our builds in CI (builds.apache.org) currently run
> > on
> > >> 1.6
> > >> > either, so while we can say from a syntax standpoint we're 1.6
> > compliant
> > >> > I'm not sure we can say from a JDK Library standpoint we don't rely
> on
> > >> > anything from Java 7.
> > >> >
> > >> > We're one of the few projects that probably still supports Java 6
> as a
> > >> > mainline development, so I was hoping we could just cut 1.6 as 1.6
> > >> > compliant, if we need to cut patch releases of 1.6 to apply patches,
> > but
> > >> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
> > >> >
> > >> > John
> > >> >
> > >>
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

Daniel Cunha
+1 :)

On Sat, Mar 26, 2016 at 10:34 AM, John D. Ament <[hidden email]>
wrote:

> All,
>
> Here's the announcement I'm going to post to the site.  Let me know if you
> have any comments on the change.
>
> == End of Support Announcement - Java 6
>
>
> The Apache DeltaSpike team has decided to begin dropping support for
>
> Java 6.  The next release, 1.6.0 is currently planned to be the last
>
> minor release to support Java 6.  Patch fixes on 1.6.x will continue
>
> to support it, but our next minor release (1.7.0) will require
>
> Java 7 at a minimum.
>
>
>
> On Fri, Mar 25, 2016 at 8:17 AM Harald Wellmann <[hidden email]>
> wrote:
>
> > +1
> >
> > 2016-03-25 13:09 GMT+01:00 John D. Ament <[hidden email]>:
> >
> > > BTW, if we do agree to drop Java 6, do we create a 1.6 maintenance
> branch
> > > or just leave the tag, and if need be cut a bug fix release then?
> > >
> > > John
> > >
> > > On Fri, Mar 25, 2016 at 8:06 AM John D. Ament <[hidden email]>
> > > wrote:
> > >
> > > > To me, dropping support for Java 6 doesn't mean rewriting the code
> base
> > > to
> > > > only be compliant with Java 7 and up.
> > > >
> > > > It does allow for some new stuff in our codebase, if we want to go
> back
> > > > and clean it up:
> > > >
> > > > - try-with-resources
> > > > - automatic type inference on generics.
> > > >
> > > > But those are just clean ups, no real new functionality.
> > > >
> > > > John
> > > >
> > > >
> > > > On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
> > > > [hidden email]> wrote:
> > > >
> > > >> basically +1
> > > >> Most of our customers are using 1.7 since this year.
> > > >>
> > > >> I just wonder whats the benefit for us?
> > > >> I think there are no language features which would improve our code
> > > base.
> > > >>
> > > >> 2016-03-25 3:25 GMT+01:00 John D. Ament <[hidden email]>:
> > > >>
> > > >> > Hey guys,
> > > >> >
> > > >> > I've brought this topic up before without much positive
> response.  I
> > > >> figure
> > > >> > I'll bring it up again.
> > > >> >
> > > >> > I'd like to propose that DeltaSpike 1.6 be the last minor release
> to
> > > >> > support Java 1.6.  I suspect that most users are already using
> Java
> > 7
> > > or
> > > >> > higher.  None of our builds in CI (builds.apache.org) currently
> run
> > > on
> > > >> 1.6
> > > >> > either, so while we can say from a syntax standpoint we're 1.6
> > > compliant
> > > >> > I'm not sure we can say from a JDK Library standpoint we don't
> rely
> > on
> > > >> > anything from Java 7.
> > > >> >
> > > >> > We're one of the few projects that probably still supports Java 6
> > as a
> > > >> > mainline development, so I was hoping we could just cut 1.6 as 1.6
> > > >> > compliant, if we need to cut patch releases of 1.6 to apply
> patches,
> > > but
> > > >> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
> > > >> >
> > > >> > John
> > > >> >
> > > >>
> > > >
> > >
> >
>



--
Daniel Cunha
https://twitter.com/dvlc_
http://www.tomitribe.com
http://www.tomitribe.io
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

Christian Kaltepoth
+1

2016-03-26 16:50 GMT+01:00 Daniel Cunha <[hidden email]>:

> +1 :)
>
> On Sat, Mar 26, 2016 at 10:34 AM, John D. Ament <[hidden email]>
> wrote:
>
> > All,
> >
> > Here's the announcement I'm going to post to the site.  Let me know if
> you
> > have any comments on the change.
> >
> > == End of Support Announcement - Java 6
> >
> >
> > The Apache DeltaSpike team has decided to begin dropping support for
> >
> > Java 6.  The next release, 1.6.0 is currently planned to be the last
> >
> > minor release to support Java 6.  Patch fixes on 1.6.x will continue
> >
> > to support it, but our next minor release (1.7.0) will require
> >
> > Java 7 at a minimum.
> >
> >
> >
> > On Fri, Mar 25, 2016 at 8:17 AM Harald Wellmann <[hidden email]>
> > wrote:
> >
> > > +1
> > >
> > > 2016-03-25 13:09 GMT+01:00 John D. Ament <[hidden email]>:
> > >
> > > > BTW, if we do agree to drop Java 6, do we create a 1.6 maintenance
> > branch
> > > > or just leave the tag, and if need be cut a bug fix release then?
> > > >
> > > > John
> > > >
> > > > On Fri, Mar 25, 2016 at 8:06 AM John D. Ament <[hidden email]
> >
> > > > wrote:
> > > >
> > > > > To me, dropping support for Java 6 doesn't mean rewriting the code
> > base
> > > > to
> > > > > only be compliant with Java 7 and up.
> > > > >
> > > > > It does allow for some new stuff in our codebase, if we want to go
> > back
> > > > > and clean it up:
> > > > >
> > > > > - try-with-resources
> > > > > - automatic type inference on generics.
> > > > >
> > > > > But those are just clean ups, no real new functionality.
> > > > >
> > > > > John
> > > > >
> > > > >
> > > > > On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
> > > > > [hidden email]> wrote:
> > > > >
> > > > >> basically +1
> > > > >> Most of our customers are using 1.7 since this year.
> > > > >>
> > > > >> I just wonder whats the benefit for us?
> > > > >> I think there are no language features which would improve our
> code
> > > > base.
> > > > >>
> > > > >> 2016-03-25 3:25 GMT+01:00 John D. Ament <[hidden email]>:
> > > > >>
> > > > >> > Hey guys,
> > > > >> >
> > > > >> > I've brought this topic up before without much positive
> > response.  I
> > > > >> figure
> > > > >> > I'll bring it up again.
> > > > >> >
> > > > >> > I'd like to propose that DeltaSpike 1.6 be the last minor
> release
> > to
> > > > >> > support Java 1.6.  I suspect that most users are already using
> > Java
> > > 7
> > > > or
> > > > >> > higher.  None of our builds in CI (builds.apache.org) currently
> > run
> > > > on
> > > > >> 1.6
> > > > >> > either, so while we can say from a syntax standpoint we're 1.6
> > > > compliant
> > > > >> > I'm not sure we can say from a JDK Library standpoint we don't
> > rely
> > > on
> > > > >> > anything from Java 7.
> > > > >> >
> > > > >> > We're one of the few projects that probably still supports Java
> 6
> > > as a
> > > > >> > mainline development, so I was hoping we could just cut 1.6 as
> 1.6
> > > > >> > compliant, if we need to cut patch releases of 1.6 to apply
> > patches,
> > > > but
> > > > >> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
> > > > >> >
> > > > >> > John
> > > > >> >
> > > > >>
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Daniel Cunha
> https://twitter.com/dvlc_
> http://www.tomitribe.com
> http://www.tomitribe.io
>



--
Christian Kaltepoth
Blog: http://blog.kaltepoth.de/
Twitter: http://twitter.com/chkal
GitHub: https://github.com/chkal
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

Harald Wellmann
+1

2016-03-26 17:49 GMT+01:00 Christian Kaltepoth <[hidden email]>:

> +1
>
> 2016-03-26 16:50 GMT+01:00 Daniel Cunha <[hidden email]>:
>
> > +1 :)
> >
> > On Sat, Mar 26, 2016 at 10:34 AM, John D. Ament <[hidden email]>
> > wrote:
> >
> > > All,
> > >
> > > Here's the announcement I'm going to post to the site.  Let me know if
> > you
> > > have any comments on the change.
> > >
> > > == End of Support Announcement - Java 6
> > >
> > >
> > > The Apache DeltaSpike team has decided to begin dropping support for
> > >
> > > Java 6.  The next release, 1.6.0 is currently planned to be the last
> > >
> > > minor release to support Java 6.  Patch fixes on 1.6.x will continue
> > >
> > > to support it, but our next minor release (1.7.0) will require
> > >
> > > Java 7 at a minimum.
> > >
> > >
> > >
> > > On Fri, Mar 25, 2016 at 8:17 AM Harald Wellmann <
> [hidden email]>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > 2016-03-25 13:09 GMT+01:00 John D. Ament <[hidden email]>:
> > > >
> > > > > BTW, if we do agree to drop Java 6, do we create a 1.6 maintenance
> > > branch
> > > > > or just leave the tag, and if need be cut a bug fix release then?
> > > > >
> > > > > John
> > > > >
> > > > > On Fri, Mar 25, 2016 at 8:06 AM John D. Ament <
> [hidden email]
> > >
> > > > > wrote:
> > > > >
> > > > > > To me, dropping support for Java 6 doesn't mean rewriting the
> code
> > > base
> > > > > to
> > > > > > only be compliant with Java 7 and up.
> > > > > >
> > > > > > It does allow for some new stuff in our codebase, if we want to
> go
> > > back
> > > > > > and clean it up:
> > > > > >
> > > > > > - try-with-resources
> > > > > > - automatic type inference on generics.
> > > > > >
> > > > > > But those are just clean ups, no real new functionality.
> > > > > >
> > > > > > John
> > > > > >
> > > > > >
> > > > > > On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
> > > > > > [hidden email]> wrote:
> > > > > >
> > > > > >> basically +1
> > > > > >> Most of our customers are using 1.7 since this year.
> > > > > >>
> > > > > >> I just wonder whats the benefit for us?
> > > > > >> I think there are no language features which would improve our
> > code
> > > > > base.
> > > > > >>
> > > > > >> 2016-03-25 3:25 GMT+01:00 John D. Ament <[hidden email]
> >:
> > > > > >>
> > > > > >> > Hey guys,
> > > > > >> >
> > > > > >> > I've brought this topic up before without much positive
> > > response.  I
> > > > > >> figure
> > > > > >> > I'll bring it up again.
> > > > > >> >
> > > > > >> > I'd like to propose that DeltaSpike 1.6 be the last minor
> > release
> > > to
> > > > > >> > support Java 1.6.  I suspect that most users are already using
> > > Java
> > > > 7
> > > > > or
> > > > > >> > higher.  None of our builds in CI (builds.apache.org)
> currently
> > > run
> > > > > on
> > > > > >> 1.6
> > > > > >> > either, so while we can say from a syntax standpoint we're 1.6
> > > > > compliant
> > > > > >> > I'm not sure we can say from a JDK Library standpoint we don't
> > > rely
> > > > on
> > > > > >> > anything from Java 7.
> > > > > >> >
> > > > > >> > We're one of the few projects that probably still supports
> Java
> > 6
> > > > as a
> > > > > >> > mainline development, so I was hoping we could just cut 1.6 as
> > 1.6
> > > > > >> > compliant, if we need to cut patch releases of 1.6 to apply
> > > patches,
> > > > > but
> > > > > >> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
> > > > > >> >
> > > > > >> > John
> > > > > >> >
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Daniel Cunha
> > https://twitter.com/dvlc_
> > http://www.tomitribe.com
> > http://www.tomitribe.io
> >
>
>
>
> --
> Christian Kaltepoth
> Blog: http://blog.kaltepoth.de/
> Twitter: http://twitter.com/chkal
> GitHub: https://github.com/chkal
>
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

Jason Porter
+1

On Sat, Mar 26, 2016 at 11:36 AM, Harald Wellmann <[hidden email]>
wrote:

> +1
>
> 2016-03-26 17:49 GMT+01:00 Christian Kaltepoth <[hidden email]>:
>
> > +1
> >
> > 2016-03-26 16:50 GMT+01:00 Daniel Cunha <[hidden email]>:
> >
> > > +1 :)
> > >
> > > On Sat, Mar 26, 2016 at 10:34 AM, John D. Ament <[hidden email]
> >
> > > wrote:
> > >
> > > > All,
> > > >
> > > > Here's the announcement I'm going to post to the site.  Let me know
> if
> > > you
> > > > have any comments on the change.
> > > >
> > > > == End of Support Announcement - Java 6
> > > >
> > > >
> > > > The Apache DeltaSpike team has decided to begin dropping support for
> > > >
> > > > Java 6.  The next release, 1.6.0 is currently planned to be the last
> > > >
> > > > minor release to support Java 6.  Patch fixes on 1.6.x will continue
> > > >
> > > > to support it, but our next minor release (1.7.0) will require
> > > >
> > > > Java 7 at a minimum.
> > > >
> > > >
> > > >
> > > > On Fri, Mar 25, 2016 at 8:17 AM Harald Wellmann <
> > [hidden email]>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > 2016-03-25 13:09 GMT+01:00 John D. Ament <[hidden email]>:
> > > > >
> > > > > > BTW, if we do agree to drop Java 6, do we create a 1.6
> maintenance
> > > > branch
> > > > > > or just leave the tag, and if need be cut a bug fix release then?
> > > > > >
> > > > > > John
> > > > > >
> > > > > > On Fri, Mar 25, 2016 at 8:06 AM John D. Ament <
> > [hidden email]
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > To me, dropping support for Java 6 doesn't mean rewriting the
> > code
> > > > base
> > > > > > to
> > > > > > > only be compliant with Java 7 and up.
> > > > > > >
> > > > > > > It does allow for some new stuff in our codebase, if we want to
> > go
> > > > back
> > > > > > > and clean it up:
> > > > > > >
> > > > > > > - try-with-resources
> > > > > > > - automatic type inference on generics.
> > > > > > >
> > > > > > > But those are just clean ups, no real new functionality.
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
> > > > > > > [hidden email]> wrote:
> > > > > > >
> > > > > > >> basically +1
> > > > > > >> Most of our customers are using 1.7 since this year.
> > > > > > >>
> > > > > > >> I just wonder whats the benefit for us?
> > > > > > >> I think there are no language features which would improve our
> > > code
> > > > > > base.
> > > > > > >>
> > > > > > >> 2016-03-25 3:25 GMT+01:00 John D. Ament <
> [hidden email]
> > >:
> > > > > > >>
> > > > > > >> > Hey guys,
> > > > > > >> >
> > > > > > >> > I've brought this topic up before without much positive
> > > > response.  I
> > > > > > >> figure
> > > > > > >> > I'll bring it up again.
> > > > > > >> >
> > > > > > >> > I'd like to propose that DeltaSpike 1.6 be the last minor
> > > release
> > > > to
> > > > > > >> > support Java 1.6.  I suspect that most users are already
> using
> > > > Java
> > > > > 7
> > > > > > or
> > > > > > >> > higher.  None of our builds in CI (builds.apache.org)
> > currently
> > > > run
> > > > > > on
> > > > > > >> 1.6
> > > > > > >> > either, so while we can say from a syntax standpoint we're
> 1.6
> > > > > > compliant
> > > > > > >> > I'm not sure we can say from a JDK Library standpoint we
> don't
> > > > rely
> > > > > on
> > > > > > >> > anything from Java 7.
> > > > > > >> >
> > > > > > >> > We're one of the few projects that probably still supports
> > Java
> > > 6
> > > > > as a
> > > > > > >> > mainline development, so I was hoping we could just cut 1.6
> as
> > > 1.6
> > > > > > >> > compliant, if we need to cut patch releases of 1.6 to apply
> > > > patches,
> > > > > > but
> > > > > > >> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
> > > > > > >> >
> > > > > > >> > John
> > > > > > >> >
> > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Daniel Cunha
> > > https://twitter.com/dvlc_
> > > http://www.tomitribe.com
> > > http://www.tomitribe.io
> > >
> >
> >
> >
> > --
> > Christian Kaltepoth
> > Blog: http://blog.kaltepoth.de/
> > Twitter: http://twitter.com/chkal
> > GitHub: https://github.com/chkal
> >
>



--
Jason Porter
http://en.gravatar.com/lightguardjp
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

Marcelo Souza Vieira
+1

2016-03-28 12:39 GMT-03:00 Jason Porter <[hidden email]>:

> +1
>
> On Sat, Mar 26, 2016 at 11:36 AM, Harald Wellmann <[hidden email]>
> wrote:
>
> > +1
> >
> > 2016-03-26 17:49 GMT+01:00 Christian Kaltepoth <[hidden email]>:
> >
> > > +1
> > >
> > > 2016-03-26 16:50 GMT+01:00 Daniel Cunha <[hidden email]>:
> > >
> > > > +1 :)
> > > >
> > > > On Sat, Mar 26, 2016 at 10:34 AM, John D. Ament <
> [hidden email]
> > >
> > > > wrote:
> > > >
> > > > > All,
> > > > >
> > > > > Here's the announcement I'm going to post to the site.  Let me know
> > if
> > > > you
> > > > > have any comments on the change.
> > > > >
> > > > > == End of Support Announcement - Java 6
> > > > >
> > > > >
> > > > > The Apache DeltaSpike team has decided to begin dropping support
> for
> > > > >
> > > > > Java 6.  The next release, 1.6.0 is currently planned to be the
> last
> > > > >
> > > > > minor release to support Java 6.  Patch fixes on 1.6.x will
> continue
> > > > >
> > > > > to support it, but our next minor release (1.7.0) will require
> > > > >
> > > > > Java 7 at a minimum.
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Mar 25, 2016 at 8:17 AM Harald Wellmann <
> > > [hidden email]>
> > > > > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > 2016-03-25 13:09 GMT+01:00 John D. Ament <[hidden email]
> >:
> > > > > >
> > > > > > > BTW, if we do agree to drop Java 6, do we create a 1.6
> > maintenance
> > > > > branch
> > > > > > > or just leave the tag, and if need be cut a bug fix release
> then?
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > On Fri, Mar 25, 2016 at 8:06 AM John D. Ament <
> > > [hidden email]
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > To me, dropping support for Java 6 doesn't mean rewriting the
> > > code
> > > > > base
> > > > > > > to
> > > > > > > > only be compliant with Java 7 and up.
> > > > > > > >
> > > > > > > > It does allow for some new stuff in our codebase, if we want
> to
> > > go
> > > > > back
> > > > > > > > and clean it up:
> > > > > > > >
> > > > > > > > - try-with-resources
> > > > > > > > - automatic type inference on generics.
> > > > > > > >
> > > > > > > > But those are just clean ups, no real new functionality.
> > > > > > > >
> > > > > > > > John
> > > > > > > >
> > > > > > > >
> > > > > > > > On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
> > > > > > > > [hidden email]> wrote:
> > > > > > > >
> > > > > > > >> basically +1
> > > > > > > >> Most of our customers are using 1.7 since this year.
> > > > > > > >>
> > > > > > > >> I just wonder whats the benefit for us?
> > > > > > > >> I think there are no language features which would improve
> our
> > > > code
> > > > > > > base.
> > > > > > > >>
> > > > > > > >> 2016-03-25 3:25 GMT+01:00 John D. Ament <
> > [hidden email]
> > > >:
> > > > > > > >>
> > > > > > > >> > Hey guys,
> > > > > > > >> >
> > > > > > > >> > I've brought this topic up before without much positive
> > > > > response.  I
> > > > > > > >> figure
> > > > > > > >> > I'll bring it up again.
> > > > > > > >> >
> > > > > > > >> > I'd like to propose that DeltaSpike 1.6 be the last minor
> > > > release
> > > > > to
> > > > > > > >> > support Java 1.6.  I suspect that most users are already
> > using
> > > > > Java
> > > > > > 7
> > > > > > > or
> > > > > > > >> > higher.  None of our builds in CI (builds.apache.org)
> > > currently
> > > > > run
> > > > > > > on
> > > > > > > >> 1.6
> > > > > > > >> > either, so while we can say from a syntax standpoint we're
> > 1.6
> > > > > > > compliant
> > > > > > > >> > I'm not sure we can say from a JDK Library standpoint we
> > don't
> > > > > rely
> > > > > > on
> > > > > > > >> > anything from Java 7.
> > > > > > > >> >
> > > > > > > >> > We're one of the few projects that probably still supports
> > > Java
> > > > 6
> > > > > > as a
> > > > > > > >> > mainline development, so I was hoping we could just cut
> 1.6
> > as
> > > > 1.6
> > > > > > > >> > compliant, if we need to cut patch releases of 1.6 to
> apply
> > > > > patches,
> > > > > > > but
> > > > > > > >> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
> > > > > > > >> >
> > > > > > > >> > John
> > > > > > > >> >
> > > > > > > >>
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Daniel Cunha
> > > > https://twitter.com/dvlc_
> > > > http://www.tomitribe.com
> > > > http://www.tomitribe.io
> > > >
> > >
> > >
> > >
> > > --
> > > Christian Kaltepoth
> > > Blog: http://blog.kaltepoth.de/
> > > Twitter: http://twitter.com/chkal
> > > GitHub: https://github.com/chkal
> > >
> >
>
>
>
> --
> Jason Porter
> http://en.gravatar.com/lightguardjp
>
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

Rudy De Busscher
+1

On 28 March 2016 at 18:30, Marcelo Souza Vieira <[hidden email]>
wrote:

> +1
>
> 2016-03-28 12:39 GMT-03:00 Jason Porter <[hidden email]>:
>
> > +1
> >
> > On Sat, Mar 26, 2016 at 11:36 AM, Harald Wellmann <
> [hidden email]>
> > wrote:
> >
> > > +1
> > >
> > > 2016-03-26 17:49 GMT+01:00 Christian Kaltepoth <[hidden email]
> >:
> > >
> > > > +1
> > > >
> > > > 2016-03-26 16:50 GMT+01:00 Daniel Cunha <[hidden email]>:
> > > >
> > > > > +1 :)
> > > > >
> > > > > On Sat, Mar 26, 2016 at 10:34 AM, John D. Ament <
> > [hidden email]
> > > >
> > > > > wrote:
> > > > >
> > > > > > All,
> > > > > >
> > > > > > Here's the announcement I'm going to post to the site.  Let me
> know
> > > if
> > > > > you
> > > > > > have any comments on the change.
> > > > > >
> > > > > > == End of Support Announcement - Java 6
> > > > > >
> > > > > >
> > > > > > The Apache DeltaSpike team has decided to begin dropping support
> > for
> > > > > >
> > > > > > Java 6.  The next release, 1.6.0 is currently planned to be the
> > last
> > > > > >
> > > > > > minor release to support Java 6.  Patch fixes on 1.6.x will
> > continue
> > > > > >
> > > > > > to support it, but our next minor release (1.7.0) will require
> > > > > >
> > > > > > Java 7 at a minimum.
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, Mar 25, 2016 at 8:17 AM Harald Wellmann <
> > > > [hidden email]>
> > > > > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > 2016-03-25 13:09 GMT+01:00 John D. Ament <
> [hidden email]
> > >:
> > > > > > >
> > > > > > > > BTW, if we do agree to drop Java 6, do we create a 1.6
> > > maintenance
> > > > > > branch
> > > > > > > > or just leave the tag, and if need be cut a bug fix release
> > then?
> > > > > > > >
> > > > > > > > John
> > > > > > > >
> > > > > > > > On Fri, Mar 25, 2016 at 8:06 AM John D. Ament <
> > > > [hidden email]
> > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > To me, dropping support for Java 6 doesn't mean rewriting
> the
> > > > code
> > > > > > base
> > > > > > > > to
> > > > > > > > > only be compliant with Java 7 and up.
> > > > > > > > >
> > > > > > > > > It does allow for some new stuff in our codebase, if we
> want
> > to
> > > > go
> > > > > > back
> > > > > > > > > and clean it up:
> > > > > > > > >
> > > > > > > > > - try-with-resources
> > > > > > > > > - automatic type inference on generics.
> > > > > > > > >
> > > > > > > > > But those are just clean ups, no real new functionality.
> > > > > > > > >
> > > > > > > > > John
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
> > > > > > > > > [hidden email]> wrote:
> > > > > > > > >
> > > > > > > > >> basically +1
> > > > > > > > >> Most of our customers are using 1.7 since this year.
> > > > > > > > >>
> > > > > > > > >> I just wonder whats the benefit for us?
> > > > > > > > >> I think there are no language features which would improve
> > our
> > > > > code
> > > > > > > > base.
> > > > > > > > >>
> > > > > > > > >> 2016-03-25 3:25 GMT+01:00 John D. Ament <
> > > [hidden email]
> > > > >:
> > > > > > > > >>
> > > > > > > > >> > Hey guys,
> > > > > > > > >> >
> > > > > > > > >> > I've brought this topic up before without much positive
> > > > > > response.  I
> > > > > > > > >> figure
> > > > > > > > >> > I'll bring it up again.
> > > > > > > > >> >
> > > > > > > > >> > I'd like to propose that DeltaSpike 1.6 be the last
> minor
> > > > > release
> > > > > > to
> > > > > > > > >> > support Java 1.6.  I suspect that most users are already
> > > using
> > > > > > Java
> > > > > > > 7
> > > > > > > > or
> > > > > > > > >> > higher.  None of our builds in CI (builds.apache.org)
> > > > currently
> > > > > > run
> > > > > > > > on
> > > > > > > > >> 1.6
> > > > > > > > >> > either, so while we can say from a syntax standpoint
> we're
> > > 1.6
> > > > > > > > compliant
> > > > > > > > >> > I'm not sure we can say from a JDK Library standpoint we
> > > don't
> > > > > > rely
> > > > > > > on
> > > > > > > > >> > anything from Java 7.
> > > > > > > > >> >
> > > > > > > > >> > We're one of the few projects that probably still
> supports
> > > > Java
> > > > > 6
> > > > > > > as a
> > > > > > > > >> > mainline development, so I was hoping we could just cut
> > 1.6
> > > as
> > > > > 1.6
> > > > > > > > >> > compliant, if we need to cut patch releases of 1.6 to
> > apply
> > > > > > patches,
> > > > > > > > but
> > > > > > > > >> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
> > > > > > > > >> >
> > > > > > > > >> > John
> > > > > > > > >> >
> > > > > > > > >>
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Daniel Cunha
> > > > > https://twitter.com/dvlc_
> > > > > http://www.tomitribe.com
> > > > > http://www.tomitribe.io
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Christian Kaltepoth
> > > > Blog: http://blog.kaltepoth.de/
> > > > Twitter: http://twitter.com/chkal
> > > > GitHub: https://github.com/chkal
> > > >
> > >
> >
> >
> >
> > --
> > Jason Porter
> > http://en.gravatar.com/lightguardjp
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: 1.6 to be the last release to support Java 1.6?

Mark Struberg-3
In reply to this post by Jason Porter
+1

LieGrue,
strub

> Am 28.03.2016 um 17:39 schrieb Jason Porter <[hidden email]>:
>
> +1
>
> On Sat, Mar 26, 2016 at 11:36 AM, Harald Wellmann <[hidden email]>
> wrote:
>
>> +1
>>
>> 2016-03-26 17:49 GMT+01:00 Christian Kaltepoth <[hidden email]>:
>>
>>> +1
>>>
>>> 2016-03-26 16:50 GMT+01:00 Daniel Cunha <[hidden email]>:
>>>
>>>> +1 :)
>>>>
>>>> On Sat, Mar 26, 2016 at 10:34 AM, John D. Ament <[hidden email]
>>>
>>>> wrote:
>>>>
>>>>> All,
>>>>>
>>>>> Here's the announcement I'm going to post to the site.  Let me know
>> if
>>>> you
>>>>> have any comments on the change.
>>>>>
>>>>> == End of Support Announcement - Java 6
>>>>>
>>>>>
>>>>> The Apache DeltaSpike team has decided to begin dropping support for
>>>>>
>>>>> Java 6.  The next release, 1.6.0 is currently planned to be the last
>>>>>
>>>>> minor release to support Java 6.  Patch fixes on 1.6.x will continue
>>>>>
>>>>> to support it, but our next minor release (1.7.0) will require
>>>>>
>>>>> Java 7 at a minimum.
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Mar 25, 2016 at 8:17 AM Harald Wellmann <
>>> [hidden email]>
>>>>> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> 2016-03-25 13:09 GMT+01:00 John D. Ament <[hidden email]>:
>>>>>>
>>>>>>> BTW, if we do agree to drop Java 6, do we create a 1.6
>> maintenance
>>>>> branch
>>>>>>> or just leave the tag, and if need be cut a bug fix release then?
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> On Fri, Mar 25, 2016 at 8:06 AM John D. Ament <
>>> [hidden email]
>>>>>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> To me, dropping support for Java 6 doesn't mean rewriting the
>>> code
>>>>> base
>>>>>>> to
>>>>>>>> only be compliant with Java 7 and up.
>>>>>>>>
>>>>>>>> It does allow for some new stuff in our codebase, if we want to
>>> go
>>>>> back
>>>>>>>> and clean it up:
>>>>>>>>
>>>>>>>> - try-with-resources
>>>>>>>> - automatic type inference on generics.
>>>>>>>>
>>>>>>>> But those are just clean ups, no real new functionality.
>>>>>>>>
>>>>>>>> John
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
>>>>>>>> [hidden email]> wrote:
>>>>>>>>
>>>>>>>>> basically +1
>>>>>>>>> Most of our customers are using 1.7 since this year.
>>>>>>>>>
>>>>>>>>> I just wonder whats the benefit for us?
>>>>>>>>> I think there are no language features which would improve our
>>>> code
>>>>>>> base.
>>>>>>>>>
>>>>>>>>> 2016-03-25 3:25 GMT+01:00 John D. Ament <
>> [hidden email]
>>>> :
>>>>>>>>>
>>>>>>>>>> Hey guys,
>>>>>>>>>>
>>>>>>>>>> I've brought this topic up before without much positive
>>>>> response.  I
>>>>>>>>> figure
>>>>>>>>>> I'll bring it up again.
>>>>>>>>>>
>>>>>>>>>> I'd like to propose that DeltaSpike 1.6 be the last minor
>>>> release
>>>>> to
>>>>>>>>>> support Java 1.6.  I suspect that most users are already
>> using
>>>>> Java
>>>>>> 7
>>>>>>> or
>>>>>>>>>> higher.  None of our builds in CI (builds.apache.org)
>>> currently
>>>>> run
>>>>>>> on
>>>>>>>>> 1.6
>>>>>>>>>> either, so while we can say from a syntax standpoint we're
>> 1.6
>>>>>>> compliant
>>>>>>>>>> I'm not sure we can say from a JDK Library standpoint we
>> don't
>>>>> rely
>>>>>> on
>>>>>>>>>> anything from Java 7.
>>>>>>>>>>
>>>>>>>>>> We're one of the few projects that probably still supports
>>> Java
>>>> 6
>>>>>> as a
>>>>>>>>>> mainline development, so I was hoping we could just cut 1.6
>> as
>>>> 1.6
>>>>>>>>>> compliant, if we need to cut patch releases of 1.6 to apply
>>>>> patches,
>>>>>>> but
>>>>>>>>>> with DeltaSpike 1.7 and on, focus on Java 7 and up.
>>>>>>>>>>
>>>>>>>>>> John
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Daniel Cunha
>>>> https://twitter.com/dvlc_
>>>> http://www.tomitribe.com
>>>> http://www.tomitribe.io
>>>>
>>>
>>>
>>>
>>> --
>>> Christian Kaltepoth
>>> Blog: http://blog.kaltepoth.de/
>>> Twitter: http://twitter.com/chkal
>>> GitHub: https://github.com/chkal
>>>
>>
>
>
>
> --
> Jason Porter
> http://en.gravatar.com/lightguardjp

Reply | Threaded
Open this post in threaded view
|

[RESULT] 1.6 to be the last release to support Java 1.6?

John D. Ament
In reply to this post by John D. Ament
Hey guys, thanks for those who considered this change.

I'm considering the vote as passed, with +1's from Thomas Andraschko,
Harald Wellmann, Daniel Cunha, Christian Kaltepoth, Jason Porter, Marcelo
Souza Vieira, Rudy De Busscher and Mark Struberg

A +0 was received by Romain Manni-Bucau
An unclear vote from Gerhard Petracek (e.g. no +1/+0/-0/-1)

I've published the news to our website.  Once we wrap up 1.6.0 I'll start a
discussion around how/when to move master over to 1.7.

John

On Thu, Mar 24, 2016 at 10:25 PM John D. Ament <[hidden email]>
wrote:

> Hey guys,
>
> I've brought this topic up before without much positive response.  I
> figure I'll bring it up again.
>
> I'd like to propose that DeltaSpike 1.6 be the last minor release to
> support Java 1.6.  I suspect that most users are already using Java 7 or
> higher.  None of our builds in CI (builds.apache.org) currently run on
> 1.6 either, so while we can say from a syntax standpoint we're 1.6
> compliant I'm not sure we can say from a JDK Library standpoint we don't
> rely on anything from Java 7.
>
> We're one of the few projects that probably still supports Java 6 as a
> mainline development, so I was hoping we could just cut 1.6 as 1.6
> compliant, if we need to cut patch releases of 1.6 to apply patches, but
> with DeltaSpike 1.7 and on, focus on Java 7 and up.
>
> John
>