That is fine with me. I would not be shy about bumping the component version up by a major release to mark the change, even if the component itself does not have 'major' changes itself.
Gary > -----Original Message----- > From: Oliver Heger [mailto:oliver.he...@oliver-heger.de] > Sent: Thursday, December 24, 2009 11:37 > To: dev@commons.apache.org > Subject: [ALL] Switch to JDK 1.4 in a minor release - was: > [configuration] Minimum required JDK version > > Thanks for the feedback so far. However, before taking concrete actions > I would like to put the question again in a broader scope. > > The question is: Is it okay for a component to change its minimum > required JDK from 1.3 to 1.4 in a minor release? > > I just want to make sure that there are no vetos when it comes to the > next release. > > Oliver > > > Oliver Heger wrote: > > > >> Currently the 1.x version of [configuration] requires JDK 1.3. I > wonder > >> whether it makes sense to switch to JDK 1.4 instead. > >> > >> I used to think that a switch of the minimum JDK version was only > >> possible for a major release. However, JDK 1.3 reached its EOL so > long > >> ago that this should not be an issue now. > >> > >> Also, JDK 1.4 would make some things easier for us. For instance, we > >> could drop some XML-related dependencies. And we would not have to > test > >> a release on a JDK 1.3. > >> > >> Are there any objections? > > > > +1, go ahead > > > > - Jörg > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org
