Hello Uwe, 2015-11-21 13:21 GMT+01:00 Uwe Barthel <bart...@x-reizend.de>:
> 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 <brit...@apache.org> 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: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
