Seems I didn't remember correctly: When using pax-exam 4.4.0 it is not possible to build using JDK 6.
However it is posssible to build using JDK 7 *and* to create Java6 compliant class files (what we do with maven-compiler-plugin setting). And I think each developer uses at least JDK 7 anyway, right? The only risk is that we use some class/method not available in Java6, but that is independent from pax-exam version. So I think we can keep pax-exam 4.4.0. Sorry for the confusion. Kind Regards, Stefan On 01/06/2015 11:04 AM, Colm O hEigeartaigh wrote: > I guess it's not such a good idea to impose a minimum JDK version on a > minor release. I will revert the pax exam change unless someone thinks it > should stay? > > Colm. > > On Mon, Jan 5, 2015 at 5:48 PM, Stefan Seelmann <[email protected]> > wrote: > >> On 01/05/2015 04:15 PM, [email protected] wrote: >>> - <pax-exam.version>3.5.0</pax-exam.version> >>> - <pax-url.version>2.2.0</pax-url.version> >>> + <pax-exam.version>4.4.0</pax-exam.version> >>> + <pax-url.version>2.3.0</pax-url.version> >> >> When using pax-exam 4.4.0 we need to set compiler level of our projects >> to Java 1.7 otherwise the OSGi tests will fail. I'm ok with increasing >> the compiler level, but maybe some users still stick to 1.6? >> >> Kind Regards, >> Stefan >> >> > >
