You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by Andy Seaborne <an...@apache.org> on 2014/04/19 18:11:18 UTC

Re: Dropping Java 6 Support?

Rob,

Do you want to call a VOTE on this?

Then Jena 2.12.0?

	Andy

On 31/03/14 11:36, Andy Seaborne wrote:
> On 31/03/14 10:34, Rob Vesse wrote:
>> Hi All
>>
>> Andy raised an interesting point recently that historically the Jena
>> project
>> has only guaranteed to maintain compatibility with the 2 most recent
>> versions of Java.  As of the recent Java 8 release this means that
>> Java 6 is
>> technically now outside of the range of versions that we intend to
>> maintain
>> compatibility with.
>>
>> Dropping of Java 6 support is not going to happen overnight so this
>> email is
>> intended to serve as advance notice that this will happen at some
>> point in
>> the future and to request feedback on this.  Note that it is likely
>> that in
>> the short term code will remain Java 6 compatible and so a workaround
>> after
>> Java 6 support is dropped will be to build from source yourself
>>
>> Are there people out there who are currently reliant on Java 6 and cannot
>> move to Java 7/8 for whatever reason?  If so what sort of timescale would
>> you consider reasonable for dropping Java 6 support?
>>
>> Thanks for your feedback,
>>
>> Rob
>
> This whole version thing is a bit of wobbly tower of choices from the
> top down.
>
> Fuseki2 requires Java7 because the version of Jetty (v9) it uses for the
> standalone server requires Java7 (which in turn is because the version
> of the servletAPI is "Servlet 3.0+").
>
> As it is Java7, there is use of "Files" and "Path" which are quite useful.
>
> It does not oblige the Jena libraries to be Java7.
>
>      Andy
>


Re: Dropping Java 6 Support?

Posted by Tim Harsch <ha...@yahoo.com>.
correction: building from source, with Java 6.   I'm guessing byte code compatibility of the different versions is the same.


On , Tim Harsch <ha...@yahoo.com> wrote:
 

>Rob, 
>
>> and so a workaround after Java 6 support is dropped will be to build from source yourself.
>
>
> I don't think that once support is dropped, you can build from source for long.  If Jena project makes use of a new language feature, or library included in Java 7 or Java 8, running Jena with Java 6 will no longer be an option.  True also, if any of its dependencies do the same.
>
>
>
>On Saturday, April 19, 2014 9:11 AM, Andy Seaborne <an...@apache.org> wrote:
> 
>Rob,
>>
>>Do you want to call a VOTE on this?
>>
>>Then Jena 2.12.0?
>>
>>    Andy
>>
>>
>>On 31/03/14 11:36, Andy Seaborne wrote:
>>> On 31/03/14 10:34, Rob Vesse wrote:
>>>> Hi All
>>>>
>>>> Andy raised an interesting point recently that historically the Jena
>>>> project
>>>> has only guaranteed to maintain compatibility with the 2 most recent
>>>>
 versions of Java.  As of the recent Java 8 release this means that
>>>> Java 6 is
>>>> technically now outside of the range of versions that we intend to
>>>> maintain
>>>> compatibility with.
>>>>
>>>> Dropping of Java 6 support is not going to happen overnight so this
>>>> email is
>>>> intended to serve as advance notice that this will happen at some
>>>> point in
>>>> the future and to request feedback on this.  Note that it is likely
>>>> that in
>>>> the short term code will remain Java 6
 compatible and so a workaround
>>>> after
>>>> Java 6 support is dropped will be to build from source yourself
>>>>
>>>> Are there people out there who are currently reliant on Java 6 and cannot
>>>> move to Java 7/8 for whatever reason?  If so what sort of timescale would
>>>> you consider reasonable for dropping Java 6 support?
>>>>
>>>> Thanks for your feedback,
>>>>
>>>> Rob
>>>
>>> This whole version thing is a bit of wobbly tower of choices from the
>>> top down.
>>>
>>> Fuseki2 requires Java7 because the version of Jetty (v9) it uses for the
>>> standalone server requires Java7 (which in turn is because the version
>>> of the servletAPI is "Servlet 3.0+").
>>>
>>> As it is Java7, there is use of "Files" and "Path" which are quite useful.
>>>
>>> It does not oblige the Jena libraries to be Java7.
>>>
>>>      Andy
>>>
>>
>>
>>
>>
>
>

Re: Dropping Java 6 Support?

Posted by Tim Harsch <ha...@yahoo.com>.
Rob, 

> and so a workaround after Java 6 support is dropped will be to build from source yourself.

 I don't think that once support is dropped, you can build from source for long.  If Jena project makes use of a new language feature, or library included in Java 7 or Java 8, running Jena with Java 6 will no longer be an option.  True also, if any of its dependencies do the same.


On Saturday, April 19, 2014 9:11 AM, Andy Seaborne <an...@apache.org> wrote:
 
Rob,
>
>Do you want to call a VOTE on this?
>
>Then Jena 2.12.0?
>
>    Andy
>
>
>On 31/03/14 11:36, Andy Seaborne wrote:
>> On 31/03/14 10:34, Rob Vesse wrote:
>>> Hi All
>>>
>>> Andy raised an interesting point recently that historically the Jena
>>> project
>>> has only guaranteed to maintain compatibility with the 2 most recent
>>> versions of Java.  As of the recent Java 8 release this means that
>>> Java 6 is
>>> technically now outside of the range of versions that we intend to
>>> maintain
>>> compatibility with.
>>>
>>> Dropping of Java 6 support is not going to happen overnight so this
>>> email is
>>> intended to serve as advance notice that this will happen at some
>>> point in
>>> the future and to request feedback on this.  Note that it is likely
>>> that in
>>> the short term code will remain Java 6 compatible and so a workaround
>>> after
>>> Java 6 support is dropped will be to build from source yourself
>>>
>>> Are there people out there who are currently reliant on Java 6 and cannot
>>> move to Java 7/8 for whatever reason?  If so what sort of timescale would
>>> you consider reasonable for dropping Java 6 support?
>>>
>>> Thanks for your feedback,
>>>
>>> Rob
>>
>> This whole version thing is a bit of wobbly tower of choices from the
>> top down.
>>
>> Fuseki2 requires Java7 because the version of Jetty (v9) it uses for the
>> standalone server requires Java7 (which in turn is because the version
>> of the servletAPI is "Servlet 3.0+").
>>
>> As it is Java7, there is use of "Files" and "Path" which are quite useful.
>>
>> It does not oblige the Jena libraries to be Java7.
>>
>>      Andy
>>
>
>
>
>

Re: Dropping Java 6 Support?

Posted by Andy Seaborne <an...@apache.org>.
(flipped to dev@)

Good plan.

	Andy


On 28/04/14 18:52, Rob Vesse wrote:
> Yes I can call a vote, what I will likely propose is that we do one more
> release that is Java 6 and then drop Java 6 support for subsequent releases
>
> Rob
>
> On 19/04/2014 09:11, "Andy Seaborne" <an...@apache.org> wrote:
>
>> Rob,
>>
>> Do you want to call a VOTE on this?
>>
>> Then Jena 2.12.0?
>>
>> 	Andy


Re: Dropping Java 6 Support?

Posted by Rob Vesse <rv...@dotnetrdf.org>.
Yes that makes sense, I'll call a vote

Rob

On 29/04/2014 07:14, "Claude Warren" <cl...@xenei.com> wrote:

>Sounds good to me
>
>
>On Mon, Apr 28, 2014 at 7:06 PM, Andy Seaborne <an...@apache.org> wrote:
>
>> (flipped to dev@)
>>
>>
>> On 28/04/14 14:08, Claude Warren wrote:
>>
>>> Should we change version numbers when Java 6 is dropped?
>>>
>>
>> Would
>>
>> 2.11.2 (last Java6)
>> then
>> 2.12.0 (Java7).
>>
>> work?
>>
>>         Andy
>>
>
>
>
>-- 
>I like: Like Like - The likeliest place on the
>web<http://like-like.xenei.com>
>LinkedIn: http://www.linkedin.com/in/claudewarren





Re: Dropping Java 6 Support?

Posted by Claude Warren <cl...@xenei.com>.
Sounds good to me


On Mon, Apr 28, 2014 at 7:06 PM, Andy Seaborne <an...@apache.org> wrote:

> (flipped to dev@)
>
>
> On 28/04/14 14:08, Claude Warren wrote:
>
>> Should we change version numbers when Java 6 is dropped?
>>
>
> Would
>
> 2.11.2 (last Java6)
> then
> 2.12.0 (Java7).
>
> work?
>
>         Andy
>



-- 
I like: Like Like - The likeliest place on the web<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: Dropping Java 6 Support?

Posted by Andy Seaborne <an...@apache.org>.
(flipped to dev@)

On 28/04/14 14:08, Claude Warren wrote:
> Should we change version numbers when Java 6 is dropped?

Would

2.11.2 (last Java6)
then
2.12.0 (Java7).

work?

	Andy

Re: Dropping Java 6 Support?

Posted by Claude Warren <cl...@xenei.com>.
Should we change version numbers when Java 6 is dropped?


On Mon, Apr 28, 2014 at 6:52 PM, Rob Vesse <rv...@dotnetrdf.org> wrote:

> Yes I can call a vote, what I will likely propose is that we do one more
> release that is Java 6 and then drop Java 6 support for subsequent releases
>
> Rob
>
> On 19/04/2014 09:11, "Andy Seaborne" <an...@apache.org> wrote:
>
> >Rob,
> >
> >Do you want to call a VOTE on this?
> >
> >Then Jena 2.12.0?
> >
> >       Andy
> >
> >On 31/03/14 11:36, Andy Seaborne wrote:
> >> On 31/03/14 10:34, Rob Vesse wrote:
> >>> Hi All
> >>>
> >>> Andy raised an interesting point recently that historically the Jena
> >>> project
> >>> has only guaranteed to maintain compatibility with the 2 most recent
> >>> versions of Java.  As of the recent Java 8 release this means that
> >>> Java 6 is
> >>> technically now outside of the range of versions that we intend to
> >>> maintain
> >>> compatibility with.
> >>>
> >>> Dropping of Java 6 support is not going to happen overnight so this
> >>> email is
> >>> intended to serve as advance notice that this will happen at some
> >>> point in
> >>> the future and to request feedback on this.  Note that it is likely
> >>> that in
> >>> the short term code will remain Java 6 compatible and so a workaround
> >>> after
> >>> Java 6 support is dropped will be to build from source yourself
> >>>
> >>> Are there people out there who are currently reliant on Java 6 and
> >>>cannot
> >>> move to Java 7/8 for whatever reason?  If so what sort of timescale
> >>>would
> >>> you consider reasonable for dropping Java 6 support?
> >>>
> >>> Thanks for your feedback,
> >>>
> >>> Rob
> >>
> >> This whole version thing is a bit of wobbly tower of choices from the
> >> top down.
> >>
> >> Fuseki2 requires Java7 because the version of Jetty (v9) it uses for the
> >> standalone server requires Java7 (which in turn is because the version
> >> of the servletAPI is "Servlet 3.0+").
> >>
> >> As it is Java7, there is use of "Files" and "Path" which are quite
> >>useful.
> >>
> >> It does not oblige the Jena libraries to be Java7.
> >>
> >>      Andy
> >>
> >
>
>
>
>
>


-- 
I like: Like Like - The likeliest place on the web<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: Dropping Java 6 Support?

Posted by Rob Vesse <rv...@dotnetrdf.org>.
Yes I can call a vote, what I will likely propose is that we do one more
release that is Java 6 and then drop Java 6 support for subsequent releases

Rob

On 19/04/2014 09:11, "Andy Seaborne" <an...@apache.org> wrote:

>Rob,
>
>Do you want to call a VOTE on this?
>
>Then Jena 2.12.0?
>
>	Andy
>
>On 31/03/14 11:36, Andy Seaborne wrote:
>> On 31/03/14 10:34, Rob Vesse wrote:
>>> Hi All
>>>
>>> Andy raised an interesting point recently that historically the Jena
>>> project
>>> has only guaranteed to maintain compatibility with the 2 most recent
>>> versions of Java.  As of the recent Java 8 release this means that
>>> Java 6 is
>>> technically now outside of the range of versions that we intend to
>>> maintain
>>> compatibility with.
>>>
>>> Dropping of Java 6 support is not going to happen overnight so this
>>> email is
>>> intended to serve as advance notice that this will happen at some
>>> point in
>>> the future and to request feedback on this.  Note that it is likely
>>> that in
>>> the short term code will remain Java 6 compatible and so a workaround
>>> after
>>> Java 6 support is dropped will be to build from source yourself
>>>
>>> Are there people out there who are currently reliant on Java 6 and
>>>cannot
>>> move to Java 7/8 for whatever reason?  If so what sort of timescale
>>>would
>>> you consider reasonable for dropping Java 6 support?
>>>
>>> Thanks for your feedback,
>>>
>>> Rob
>>
>> This whole version thing is a bit of wobbly tower of choices from the
>> top down.
>>
>> Fuseki2 requires Java7 because the version of Jetty (v9) it uses for the
>> standalone server requires Java7 (which in turn is because the version
>> of the servletAPI is "Servlet 3.0+").
>>
>> As it is Java7, there is use of "Files" and "Path" which are quite
>>useful.
>>
>> It does not oblige the Jena libraries to be Java7.
>>
>>      Andy
>>
>