I think we should stick to the plan I outlined. I hope to have some time to
work in JXPATH this weekend. I'll also work on a VM for building JXPATH
with Java 4.
BR,
Benedikt
2015-12-02 21:17 GMT+01:00 Uwe Barthel :
> Hi,
>
> should we start a official vote for the Java version topic for JXPath o
Hi,
should we start a official vote for the Java version topic for JXPath or
following the release plan provided by Benedikt?
-- Uwe
> On 25 Nov 2015, at 20:18, Gary Gregory wrote:
>
> On Wed, Nov 25, 2015 at 9:27 AM, sebb wrote:
>
>> On 25 November 2015 at 16:49, Gary Gregory wrote:
>>>
On Wed, Nov 25, 2015 at 9:27 AM, sebb wrote:
> On 25 November 2015 at 16:49, Gary Gregory wrote:
> > On Tue, Nov 24, 2015 at 11:57 PM, Uwe Barthel
> wrote:
> >
> >>
> >> > Do you like to start these changes before or after the release 1.4?
> > I prefer to create the release as soon as poss
On 25 November 2015 at 16:49, Gary Gregory wrote:
> On Tue, Nov 24, 2015 at 11:57 PM, Uwe Barthel wrote:
>
>>
>> > 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.
>>>
>> Mayb
On Tue, Nov 24, 2015 at 11:57 PM, Uwe Barthel wrote:
>
> > 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.
>>>
>>
> Maybe my statement was a bit ambiguous. I'm fine with a Java vers
> 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.
Maybe my statement was a bit ambiguous. I'm fine with a Java version 1.6 or
1.7 but would not wait until the code is overall refurbishe
2015-11-24 21:55 GMT+01:00 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
2015-11-24 22:06 GMT+01:00 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
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 st
On 25 November 2015 at 09:29, Emmanuel Bourg 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 feat
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 simpli
On Tue, Nov 24, 2015 at 3:06 PM, Thomas Neidhart
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 t
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 cre
> 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
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 :
> If you pay Oracle for long term support you still get updates for Java
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 wrote:
As has jav
On Sun, Nov 22, 2015 at 6:20 AM, Dave Brosius 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:
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, t
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 wrote:
> Okay, so we go with Java 8? Doesn't feel like it has reached enough market
> penetration yet. But I don
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 :
> 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
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 :
I'd go with Java 7.
Gary
On Nov 21, 2015 3:50 AM, "Benedikt Ritter" wrote:
Hi,
any preference on which J
I'm fine with Java 7, since Java 6 has already reached EOL.
2015-11-21 19:48 GMT+01:00 Gary Gregory :
> I'd go with Java 7.
>
> Gary
> On Nov 21, 2015 3:50 AM, "Benedikt Ritter" wrote:
>
> > Hi,
> >
> > any preference on which Java Version JXPath 1.4 target? Currently the
> build
> > is set to 1
I'd go with Java 7.
Gary
On Nov 21, 2015 3:50 AM, "Benedikt Ritter" 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. Furth
Hello Uwe,
2015-11-21 13:21 GMT+01:00 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.
>
Are you referring to SemVer here? I'm not sure it contains any rules ab
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-snif
25 matches
Mail list logo