Thanks for the research and the reminder.
Based on that, it seems to me that a minor release should be enough.
Perhaps 3.1.0 and not 3.0.8, but probably not 4.0.0, unless we start
actually developing against java 8 (i.e. lambdas, etc...).
Cheers!
Nick
PS: On a side note, did we try it with java 9 so far? Not that I expect
any real problem, but some of our dependencies are really old and may
need to be revisited.
On 2017-09-04 19:22, mck wrote:
But yes, I think it means Tiles 4.x if you are going to require that
users upgrade their Java version in order to upgrade from Tiles 3.x,
because it implies that you are going to use some new language
features that would make Tiles "not interface compatible with the
prior version."
So here there's two separate proposed java bumps…
1) upgrade the jdk required to build from 1.7 to 1.8, and
2) bump the minimum runtime to Java7 (from Java6).
Note (2) was already agreed upon and has been public for some time:
- http://tiles.apache.org/download.html
- http://svn.apache.org/viewvc?view=revision&revision=1536392
-
http://mail-archives.apache.org/mod_mbox/tiles-dev/201310.mbox/%3C1382990767.698.54.camel%40Device-D2AB6C%3E
So the only change here really is bumping the minimum java required to
build the project.
My thoughts now are that this requires only a patch (minor.minor)
version.
While if we were to bump the minimum runtime to Java8, then that would
definitely warrant the new major versions.
what do folk think?
regards,
Mick
ps I came across this having troubles getting Apache's Jenkins
infrastructure to build Tiles projects on JDK1.7, of which i see haven't
managed to fix. (thinking that `maven-toolchains-plugin` needs to be
added to pom's that want to still build with 1.7.)
