I don;t see much to be gained in making surefire require JDK 1.5. There are a lot of people on 2.0.x (heck recent traffic on the list would seem to imply a lot of people starting to use maven 1.1!) and forcing JDK 1.5 on them just to get some of the fixes in surefire would seem to be not nice.
Now that we have maven-plugin-enforcer we should be able to test the core plugins a bit better and that way we can start releasing them more often... just have to wait for Benjamin to wire it up on the grid -Stephen 2009/11/4 Brett Porter <[email protected]>: > The plugin is 1.4 and the booter/api is 1.3 so that you can still run tests > on old JDKs. > > The plugin *could* be updated to 1.5 if it is made to require Maven 2.2. > Probably not worth it at this stage. > > - Brett > > On 03/11/2009, at 6:09 PM, Kristian Rosenvold wrote: > >> I am working on a patch to surefire and find that habitually I'm >> consistently grabbing got my <>'s and java 5 for loops. I see the >> following seems to apply: >> >> Some surefire-providers have an implicit java 5 requirement because >> (like junit 4) they support java 5 projects. >> >> But what language levels are effective in shared modules (like >> surefire-api), surefire-plugin and surefire-booter ? At least sine poms >> don't seem to be entirely correctly set up to refelect language levels >> either (testng provider uses java 5 features but does not seem to be at >> java 5 language level in the poms - AFAIK) >> >> >> Regards, >> >> Kristian Rosenvold >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
