[JXPATH] Java Version

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

[JXPATH] Java Version

Benedikt Ritter-4
Hi,

any preference on which Java Version JXPath 1.4 target? Currently the build
is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my machine,
so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't see
a reason to keep support for such old Java versions.

Thoughts?
Benedikt

--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Uwe Barthel
Java 1.6 would be old enough I think.

But, JXPath doesn't follow the three digit version schema.
So any change of Java dependency may should force a major change.
How will it handled in other Commons with projects two digit version schema?

Maybe should be used: http://www.mojohaus.org/animal-sniffer/ 

-- Uwe


> On 21 Nov 2015, at 12:50, Benedikt Ritter <[hidden email]> wrote:
>
> Hi,
>
> any preference on which Java Version JXPath 1.4 target? Currently the build
> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my machine,
> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't see
> a reason to keep support for such old Java versions.
>
> Thoughts?
> Benedikt
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Benedikt Ritter-4
Hello Uwe,

2015-11-21 13:21 GMT+01:00 Uwe Barthel <[hidden email]>:

> Java 1.6 would be old enough I think.
>
> But, JXPath doesn't follow the three digit version schema.
> So any change of Java dependency may should force a major change.
>

Are you referring to SemVer here? I'm not sure it contains any rules about
changes to the platform a component is running on. From an API PoV we won't
break anything.


> How will it handled in other Commons with projects two digit version
> schema?
>

Usually only have three digit versions when we release a bugfix. So we
start with for example 1.0, then release 1.1 and 1.2 and if we need to
bugfix 1.2 that will become 1.2.1. Maybe it would be better to have three
digit versions all the way around.


>
> Maybe should be used: http://www.mojohaus.org/animal-sniffer/


Doesn't work with Java < 1.5 :-(

Benedikt


>
>
> -- Uwe
>
>
> > On 21 Nov 2015, at 12:50, Benedikt Ritter <[hidden email]> wrote:
> >
> > Hi,
> >
> > any preference on which Java Version JXPath 1.4 target? Currently the
> build
> > is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
> machine,
> > so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
> see
> > a reason to keep support for such old Java versions.
> >
> > Thoughts?
> > Benedikt
> >
> > --
> > http://people.apache.org/~britter/
> > http://www.systemoutprintln.de/
> > http://twitter.com/BenediktRitter
> > http://github.com/britter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

garydgregory
In reply to this post by Benedikt Ritter-4
I'd go with Java 7.

Gary
On Nov 21, 2015 3:50 AM, "Benedikt Ritter" <[hidden email]> wrote:

> Hi,
>
> any preference on which Java Version JXPath 1.4 target? Currently the build
> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my machine,
> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't see
> a reason to keep support for such old Java versions.
>
> Thoughts?
> Benedikt
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>
Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Benedikt Ritter-4
I'm fine with Java 7, since Java 6 has already reached EOL.

2015-11-21 19:48 GMT+01:00 Gary Gregory <[hidden email]>:

> I'd go with Java 7.
>
> Gary
> On Nov 21, 2015 3:50 AM, "Benedikt Ritter" <[hidden email]> wrote:
>
> > Hi,
> >
> > any preference on which Java Version JXPath 1.4 target? Currently the
> build
> > is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
> machine,
> > so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
> see
> > a reason to keep support for such old Java versions.
> >
> > Thoughts?
> > Benedikt
> >
> > --
> > http://people.apache.org/~britter/
> > http://www.systemoutprintln.de/
> > http://twitter.com/BenediktRitter
> > http://github.com/britter
> >
>



--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Dave Brosius-2
As has java 7 reached end of life.

On 11/22/2015 09:06 AM, Benedikt Ritter wrote:

> I'm fine with Java 7, since Java 6 has already reached EOL.
>
> 2015-11-21 19:48 GMT+01:00 Gary Gregory <[hidden email]>:
>
>> I'd go with Java 7.
>>
>> Gary
>> On Nov 21, 2015 3:50 AM, "Benedikt Ritter" <[hidden email]> wrote:
>>
>>> Hi,
>>>
>>> any preference on which Java Version JXPath 1.4 target? Currently the
>> build
>>> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
>> machine,
>>> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
>> see
>>> a reason to keep support for such old Java versions.
>>>
>>> Thoughts?
>>> Benedikt
>>>
>>> --
>>> http://people.apache.org/~britter/
>>> http://www.systemoutprintln.de/
>>> http://twitter.com/BenediktRitter
>>> http://github.com/britter
>>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Benedikt Ritter-4
Okay, so we go with Java 8? Doesn't feel like it has reached enough market
penetration yet. But I don't know numbers about that.

2015-11-22 15:20 GMT+01:00 Dave Brosius <[hidden email]>:

> As has java 7 reached end of life.
>
> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
>
>> I'm fine with Java 7, since Java 6 has already reached EOL.
>>
>> 2015-11-21 19:48 GMT+01:00 Gary Gregory <[hidden email]>:
>>
>> I'd go with Java 7.
>>>
>>> Gary
>>> On Nov 21, 2015 3:50 AM, "Benedikt Ritter" <[hidden email]> wrote:
>>>
>>> Hi,
>>>>
>>>> any preference on which Java Version JXPath 1.4 target? Currently the
>>>>
>>> build
>>>
>>>> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
>>>>
>>> machine,
>>>
>>>> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
>>>>
>>> see
>>>
>>>> a reason to keep support for such old Java versions.
>>>>
>>>> Thoughts?
>>>> Benedikt
>>>>
>>>> --
>>>> http://people.apache.org/~britter/
>>>> http://www.systemoutprintln.de/
>>>> http://twitter.com/BenediktRitter
>>>> http://github.com/britter
>>>>
>>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

James Ring
Unfortunately Android still uses Java 7, if you want Android
developers to be able to use the library then I think you should
target 7.

On Sun, Nov 22, 2015 at 7:12 AM, Benedikt Ritter <[hidden email]> wrote:

> Okay, so we go with Java 8? Doesn't feel like it has reached enough market
> penetration yet. But I don't know numbers about that.
>
> 2015-11-22 15:20 GMT+01:00 Dave Brosius <[hidden email]>:
>
>> As has java 7 reached end of life.
>>
>> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
>>
>>> I'm fine with Java 7, since Java 6 has already reached EOL.
>>>
>>> 2015-11-21 19:48 GMT+01:00 Gary Gregory <[hidden email]>:
>>>
>>> I'd go with Java 7.
>>>>
>>>> Gary
>>>> On Nov 21, 2015 3:50 AM, "Benedikt Ritter" <[hidden email]> wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> any preference on which Java Version JXPath 1.4 target? Currently the
>>>>>
>>>> build
>>>>
>>>>> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
>>>>>
>>>> machine,
>>>>
>>>>> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
>>>>>
>>>> see
>>>>
>>>>> a reason to keep support for such old Java versions.
>>>>>
>>>>> Thoughts?
>>>>> Benedikt
>>>>>
>>>>> --
>>>>> http://people.apache.org/~britter/
>>>>> http://www.systemoutprintln.de/
>>>>> http://twitter.com/BenediktRitter
>>>>> http://github.com/britter
>>>>>
>>>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

sebb-2-2
Java 7 seems OK to me, though if the code builds and test OK with Java
1.6, why not leave it at that?

Just because Java 1.6 is EOL does not mean that Java 1.6-compatible
code will stop working.

So long as the Java runtime used to run the code is updated to a
currently supported version of Java, that is enough to ensure that any
JVM bugs are fixed.


On 22 November 2015 at 15:19, James Ring <[hidden email]> wrote:

> Unfortunately Android still uses Java 7, if you want Android
> developers to be able to use the library then I think you should
> target 7.
>
> On Sun, Nov 22, 2015 at 7:12 AM, Benedikt Ritter <[hidden email]> wrote:
>> Okay, so we go with Java 8? Doesn't feel like it has reached enough market
>> penetration yet. But I don't know numbers about that.
>>
>> 2015-11-22 15:20 GMT+01:00 Dave Brosius <[hidden email]>:
>>
>>> As has java 7 reached end of life.
>>>
>>> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
>>>
>>>> I'm fine with Java 7, since Java 6 has already reached EOL.
>>>>
>>>> 2015-11-21 19:48 GMT+01:00 Gary Gregory <[hidden email]>:
>>>>
>>>> I'd go with Java 7.
>>>>>
>>>>> Gary
>>>>> On Nov 21, 2015 3:50 AM, "Benedikt Ritter" <[hidden email]> wrote:
>>>>>
>>>>> Hi,
>>>>>>
>>>>>> any preference on which Java Version JXPath 1.4 target? Currently the
>>>>>>
>>>>> build
>>>>>
>>>>>> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
>>>>>>
>>>>> machine,
>>>>>
>>>>>> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
>>>>>>
>>>>> see
>>>>>
>>>>>> a reason to keep support for such old Java versions.
>>>>>>
>>>>>> Thoughts?
>>>>>> Benedikt
>>>>>>
>>>>>> --
>>>>>> http://people.apache.org/~britter/
>>>>>> http://www.systemoutprintln.de/
>>>>>> http://twitter.com/BenediktRitter
>>>>>> http://github.com/britter
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>>
>> --
>> http://people.apache.org/~britter/
>> http://www.systemoutprintln.de/
>> http://twitter.com/BenediktRitter
>> http://github.com/britter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

garydgregory
In reply to this post by Dave Brosius-2
On Sun, Nov 22, 2015 at 6:20 AM, Dave Brosius <[hidden email]> wrote:

> As has java 7 reached end of life.


FYI: I think IBM still supports their Java 7 IIRC

Gayr

>
>
> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
>
>> I'm fine with Java 7, since Java 6 has already reached EOL.
>>
>> 2015-11-21 19:48 GMT+01:00 Gary Gregory <[hidden email]>:
>>
>> I'd go with Java 7.
>>>
>>> Gary
>>> On Nov 21, 2015 3:50 AM, "Benedikt Ritter" <[hidden email]> wrote:
>>>
>>> Hi,
>>>>
>>>> any preference on which Java Version JXPath 1.4 target? Currently the
>>>>
>>> build
>>>
>>>> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
>>>>
>>> machine,
>>>
>>>> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
>>>>
>>> see
>>>
>>>> a reason to keep support for such old Java versions.
>>>>
>>>> Thoughts?
>>>> Benedikt
>>>>
>>>> --
>>>> http://people.apache.org/~britter/
>>>> http://www.systemoutprintln.de/
>>>> http://twitter.com/BenediktRitter
>>>> http://github.com/britter
>>>>
>>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
E-Mail: [hidden email] | [hidden email]
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Pascal Schumacher
If you pay Oracle for long term support you still get updates for Java 7.

This means that there will be some people (like me at work :() which
have to stick to Java 7 for some time.

Am 22.11.2015 um 16:44 schrieb Gary Gregory:

> On Sun, Nov 22, 2015 at 6:20 AM, Dave Brosius <[hidden email]> wrote:
>
>> As has java 7 reached end of life.
>
> FYI: I think IBM still supports their Java 7 IIRC
>
> Gayr
>
>>
>> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
>>
>>> I'm fine with Java 7, since Java 6 has already reached EOL.
>>>
>>> 2015-11-21 19:48 GMT+01:00 Gary Gregory <[hidden email]>:
>>>
>>> I'd go with Java 7.
>>>> Gary
>>>> On Nov 21, 2015 3:50 AM, "Benedikt Ritter" <[hidden email]> wrote:
>>>>
>>>> Hi,
>>>>> any preference on which Java Version JXPath 1.4 target? Currently the
>>>>>
>>>> build
>>>>
>>>>> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
>>>>>
>>>> machine,
>>>>
>>>>> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
>>>>>
>>>> see
>>>>
>>>>> a reason to keep support for such old Java versions.
>>>>>
>>>>> Thoughts?
>>>>> Benedikt
>>>>>
>>>>> --
>>>>> http://people.apache.org/~britter/
>>>>> http://www.systemoutprintln.de/
>>>>> http://twitter.com/BenediktRitter
>>>>> http://github.com/britter
>>>>>
>>>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Benedikt Ritter-4
I've updated JXPATH to Java 7. There is a lot of work to update the code
base to use Java 7 languages features and APIs. I invite everybody to join
me here...

Thanks,
Benedikt

2015-11-22 19:28 GMT+01:00 Pascal Schumacher <[hidden email]>:

> If you pay Oracle for long term support you still get updates for Java 7.
>
> This means that there will be some people (like me at work :() which have
> to stick to Java 7 for some time.
>
>
> Am 22.11.2015 um 16:44 schrieb Gary Gregory:
>
>> On Sun, Nov 22, 2015 at 6:20 AM, Dave Brosius <[hidden email]>
>> wrote:
>>
>> As has java 7 reached end of life.
>>>
>>
>> FYI: I think IBM still supports their Java 7 IIRC
>>
>> Gayr
>>
>>
>>> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
>>>
>>> I'm fine with Java 7, since Java 6 has already reached EOL.
>>>>
>>>> 2015-11-21 19:48 GMT+01:00 Gary Gregory <[hidden email]>:
>>>>
>>>> I'd go with Java 7.
>>>>
>>>>> Gary
>>>>> On Nov 21, 2015 3:50 AM, "Benedikt Ritter" <[hidden email]> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>> any preference on which Java Version JXPath 1.4 target? Currently the
>>>>>>
>>>>>> build
>>>>>
>>>>> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
>>>>>>
>>>>>> machine,
>>>>>
>>>>> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
>>>>>>
>>>>>> see
>>>>>
>>>>> a reason to keep support for such old Java versions.
>>>>>>
>>>>>> Thoughts?
>>>>>> Benedikt
>>>>>>
>>>>>> --
>>>>>> http://people.apache.org/~britter/
>>>>>> http://www.systemoutprintln.de/
>>>>>> http://twitter.com/BenediktRitter
>>>>>> http://github.com/britter
>>>>>>
>>>>>>
>>>>>>
>>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Uwe Barthel
> I've updated JXPATH to Java 7. There is a lot of work to update the code
> base to use Java 7 languages features and APIs. I invite everybody to join
> me here…

Do you like to start these changes before or after the release 1.4?
I prefer to create the release as soon as possible and start rework on that baseline.

-- Uwe


> On 24 Nov 2015, at 21:44, Benedikt Ritter <[hidden email]> wrote:
>
> I've updated JXPATH to Java 7. There is a lot of work to update the code
> base to use Java 7 languages features and APIs. I invite everybody to join
> me here...
>
> Thanks,
> Benedikt
>
> 2015-11-22 19:28 GMT+01:00 Pascal Schumacher <[hidden email]>:
>
>> If you pay Oracle for long term support you still get updates for Java 7.
>>
>> This means that there will be some people (like me at work :() which have
>> to stick to Java 7 for some time.
>>
>>
>> Am 22.11.2015 um 16:44 schrieb Gary Gregory:
>>
>>> On Sun, Nov 22, 2015 at 6:20 AM, Dave Brosius <[hidden email]>
>>> wrote:
>>>
>>> As has java 7 reached end of life.
>>>>
>>>
>>> FYI: I think IBM still supports their Java 7 IIRC
>>>
>>> Gayr
>>>
>>>
>>>> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
>>>>
>>>> I'm fine with Java 7, since Java 6 has already reached EOL.
>>>>>
>>>>> 2015-11-21 19:48 GMT+01:00 Gary Gregory <[hidden email]>:
>>>>>
>>>>> I'd go with Java 7.
>>>>>
>>>>>> Gary
>>>>>> On Nov 21, 2015 3:50 AM, "Benedikt Ritter" <[hidden email]> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>> any preference on which Java Version JXPath 1.4 target? Currently the
>>>>>>>
>>>>>>> build
>>>>>>
>>>>>> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
>>>>>>>
>>>>>>> machine,
>>>>>>
>>>>>> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
>>>>>>>
>>>>>>> see
>>>>>>
>>>>>> a reason to keep support for such old Java versions.
>>>>>>>
>>>>>>> Thoughts?
>>>>>>> Benedikt
>>>>>>>
>>>>>>> --
>>>>>>> http://people.apache.org/~britter/
>>>>>>> http://www.systemoutprintln.de/
>>>>>>> http://twitter.com/BenediktRitter
>>>>>>> http://github.com/britter
>>>>>>>
>>>>>>>
>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Thomas Neidhart
On 11/24/2015 09:55 PM, Uwe Barthel wrote:
>> I've updated JXPATH to Java 7. There is a lot of work to update the code
>> base to use Java 7 languages features and APIs. I invite everybody to join
>> me here…
>
> Do you like to start these changes before or after the release 1.4?
> I prefer to create the release as soon as possible and start rework on that baseline.

If the idea is to roll out a bugfix release that people are awaiting
then I do not see the point in updating the minimum java version and
changing the code to use new language / jdk features.

This will just limit the use of the bugfix release, as not every
application using it will have been upgraded already. Also, every change
might introduce another problem, but this is up to the judgement of the
maintainer(s).

For the release afterwards (i.e. 1.5), I think it is fine to apply all
the changes, and updating the minimum java version in minor releases is
ok and has been done for other components already.

Just my 2 cents

Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Matt Benson-2
On Tue, Nov 24, 2015 at 3:06 PM, Thomas Neidhart
<[hidden email]> wrote:

> On 11/24/2015 09:55 PM, Uwe Barthel wrote:
>>> I've updated JXPATH to Java 7. There is a lot of work to update the code
>>> base to use Java 7 languages features and APIs. I invite everybody to join
>>> me here…
>>
>> Do you like to start these changes before or after the release 1.4?
>> I prefer to create the release as soon as possible and start rework on that baseline.
>
> If the idea is to roll out a bugfix release that people are awaiting
> then I do not see the point in updating the minimum java version and
> changing the code to use new language / jdk features.
>
> This will just limit the use of the bugfix release, as not every
> application using it will have been upgraded already. Also, every change
> might introduce another problem, but this is up to the judgement of the
> maintainer(s).
>
> For the release afterwards (i.e. 1.5), I think it is fine to apply all
> the changes, and updating the minimum java version in minor releases is
> ok and has been done for other components already.

I really want to see JXPath get e.g. generics. That said, there is
wisdom in leaving that until after the immediate release. I don't have
the patience for acting as RM, but I think I'll have a few spare
cycles to work on upgrades. What does everyone think about creating a
branch for this work?

Matt

>
> Just my 2 cents
>
> Thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Emmanuel Bourg-3
In reply to this post by Thomas Neidhart
Le 24/11/2015 22:06, Thomas Neidhart a écrit :

> If the idea is to roll out a bugfix release that people are awaiting
> then I do not see the point in updating the minimum java version and
> changing the code to use new language / jdk features.

I agree with Thomas. Let's update the JDK for simplifying the release
process, but updating the syntax now isn't necessary.

Emmanuel Bourg


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Peter Ansell
On 25 November 2015 at 09:29, Emmanuel Bourg <[hidden email]> wrote:
> Le 24/11/2015 22:06, Thomas Neidhart a écrit :
>
>> If the idea is to roll out a bugfix release that people are awaiting
>> then I do not see the point in updating the minimum java version and
>> changing the code to use new language / jdk features.
>
> I agree with Thomas. Let's update the JDK for simplifying the release
> process, but updating the syntax now isn't necessary.

One simple addition you can do when moving to Java-7 is to add
java.lang.AutoCloseable to any relevant classes that are not already
java.io.Closeable, but still have resources that need to be cleaned
up. Then users can then use them in try-with-resources (and IDE's can
start warning about resource cleanups), even if the jxpath codebase
doesn't internally change from the previous try pattern to
try-with-resources immediately.

Cheers,

Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Emmanuel Bourg-3
In reply to this post by Benedikt Ritter-4
Le 22/11/2015 15:06, Benedikt Ritter a écrit :
> I'm fine with Java 7, since Java 6 has already reached EOL.

The free of charge Oracle Java 6 is EOL, but this isn't the only Java 6
distributions. OpenJDK 6 is still maintained by RedHat [1] and is
commonly used on servers. On Debian OpenJDK 6 is still installed on 35%
of the machines with OpenJDK [2].

On the desktop side the figures are quite different. On the application
I maintain I observe that Java 8 dominates around 75%. Java 6 is around
17%, mostly due to OS X users not upgrading the Apple Java to the more
recent Oracle Java.

Emmanuel Bourg

[1] http://hg.openjdk.java.net/jdk6/jdk6/jdk/
[2]
https://qa.debian.org/popcon-graph.php?packages=openjdk-6-jre-headless+openjdk-7-jre-headless+openjdk-8-jre-headless&show_installed=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Benedikt Ritter-4
In reply to this post by Thomas Neidhart
2015-11-24 22:06 GMT+01:00 Thomas Neidhart <[hidden email]>:

> On 11/24/2015 09:55 PM, Uwe Barthel wrote:
> >> I've updated JXPATH to Java 7. There is a lot of work to update the code
> >> base to use Java 7 languages features and APIs. I invite everybody to
> join
> >> me here…
> >
> > Do you like to start these changes before or after the release 1.4?
> > I prefer to create the release as soon as possible and start rework on
> that baseline.
>
> If the idea is to roll out a bugfix release that people are awaiting
> then I do not see the point in updating the minimum java version and
> changing the code to use new language / jdk features.
>

The problem with JDK 1.4 is, that I don't have it on any machine. The
oldest JDK you can get for Mac OS X to my knowledge is 1.6. I wouldn't want
to RM for a project when I can't test with the target JDK. If anybody knows
where to get a JDK 1.4 for Mac OS, that would be very much appreciated.


>
> This will just limit the use of the bugfix release, as not every
> application using it will have been upgraded already. Also, every change
> might introduce another problem, but this is up to the judgement of the
> maintainer(s).
>
> For the release afterwards (i.e. 1.5), I think it is fine to apply all
> the changes, and updating the minimum java version in minor releases is
> ok and has been done for other components already.


> Just my 2 cents
>
> Thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Reply | Threaded
Open this post in threaded view
|

Re: [JXPATH] Java Version

Benedikt Ritter-4
In reply to this post by Uwe Barthel
2015-11-24 21:55 GMT+01:00 Uwe Barthel <[hidden email]>:

> > I've updated JXPATH to Java 7. There is a lot of work to update the code
> > base to use Java 7 languages features and APIs. I invite everybody to
> join
> > me here…
>
> Do you like to start these changes before or after the release 1.4?
> I prefer to create the release as soon as possible and start rework on
> that baseline.
>

I have already started to upgrade the code base.


>
> -- Uwe
>
>
> > On 24 Nov 2015, at 21:44, Benedikt Ritter <[hidden email]> wrote:
> >
> > I've updated JXPATH to Java 7. There is a lot of work to update the code
> > base to use Java 7 languages features and APIs. I invite everybody to
> join
> > me here...
> >
> > Thanks,
> > Benedikt
> >
> > 2015-11-22 19:28 GMT+01:00 Pascal Schumacher <[hidden email]>:
> >
> >> If you pay Oracle for long term support you still get updates for Java
> 7.
> >>
> >> This means that there will be some people (like me at work :() which
> have
> >> to stick to Java 7 for some time.
> >>
> >>
> >> Am 22.11.2015 um 16:44 schrieb Gary Gregory:
> >>
> >>> On Sun, Nov 22, 2015 at 6:20 AM, Dave Brosius <[hidden email]>
> >>> wrote:
> >>>
> >>> As has java 7 reached end of life.
> >>>>
> >>>
> >>> FYI: I think IBM still supports their Java 7 IIRC
> >>>
> >>> Gayr
> >>>
> >>>
> >>>> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
> >>>>
> >>>> I'm fine with Java 7, since Java 6 has already reached EOL.
> >>>>>
> >>>>> 2015-11-21 19:48 GMT+01:00 Gary Gregory <[hidden email]>:
> >>>>>
> >>>>> I'd go with Java 7.
> >>>>>
> >>>>>> Gary
> >>>>>> On Nov 21, 2015 3:50 AM, "Benedikt Ritter" <[hidden email]>
> wrote:
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>>> any preference on which Java Version JXPath 1.4 target? Currently
> the
> >>>>>>>
> >>>>>>> build
> >>>>>>
> >>>>>> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
> >>>>>>>
> >>>>>>> machine,
> >>>>>>
> >>>>>> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I
> don't
> >>>>>>>
> >>>>>>> see
> >>>>>>
> >>>>>> a reason to keep support for such old Java versions.
> >>>>>>>
> >>>>>>> Thoughts?
> >>>>>>> Benedikt
> >>>>>>>
> >>>>>>> --
> >>>>>>> http://people.apache.org/~britter/
> >>>>>>> http://www.systemoutprintln.de/
> >>>>>>> http://twitter.com/BenediktRitter
> >>>>>>> http://github.com/britter
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: [hidden email]
> >>>> For additional commands, e-mail: [hidden email]
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
> >
> >
> > --
> > http://people.apache.org/~britter/
> > http://www.systemoutprintln.de/
> > http://twitter.com/BenediktRitter
> > http://github.com/britter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
12