I've done some further (rather lengthy) investigation into this, documented in ISIS-568 [1].
The long-and-short of it is that moving to JDK 7 also requires upgrading to ASM 4.x and cglib 3.x... this impacts our a) wrapper factory b) isis-core-bytecode-cglib module (n/a if using JDO) c) our unit tests that use JMock and the jmock-legacy module for mocking concrete classes. The first two could be tackled, I think, but the last is quite a big dependency. It might be the least work to help the JMock guys move their library up to cglib 3.x Suggest we use [1] to track further discussion on this matter. [1] https://issues.apache.org/jira/browse/ISIS-568 On 14 October 2013 08:45, GESCONSULTOR - Óscar Bou <[email protected]>wrote: > +1 > > > El 13/10/2013, a las 20:13, Michael Xiao <[email protected]> > escribió: > > > +1 > > > > > > On 11 October 2013 23:59, Dan Haywood <[email protected]> > wrote: > > > >> Several reasons: > >> > >> 1. Martin Grigorov (Wicket committer) and Michael Haitz (similar Wicket > >> expert) are working on ISIS-537 [1] to restyle Wicket using Bootstrap3. > >> One of their key dependencies is currently only available under JDK 1.7. > >> > >> 2. Wicket 7.0 will mandate JDK 1.7, and, obviously Isis' Wicket viewer > >> should keep up with the latest version of Wicket. > >> > >> 3. its 2013 already. > >> > >> > >> Any votes +1 or -1? > >> > >> Thx > >> Dan > >> > >> > >> [1] https://github.com/l0rdn1kk0n/isis/commits/ISIS-537 > >> > >
