We see the same problem. None of our Java5 Maven builds work any longer. Some of the classes in the maven-plugin.hpi are Java6 format:

[sweeney@hudson0 plugins]$ unzip -l -p maven-plugin.hpi 'WEB-INF/classes/hudson/maven/ProcessCache$GetSystemProperties.class' > xxx
[sweeney@hudson0 plugins]$ file xxx
xxx: compiled Java class data, version 50.0
[sweeney@hudson0 plugins]$ rm xxx
[sweeney@hudson0 plugins]$

We have to have Java5 artefacts because the target J2EE container runs atop Java5. We can work round this by using the Java6 compiler and modifying the build to explicitly request Java5-compatible artefacts, but that means changing several dozen jobs. If Java5 is deprecated in this release I would have expected to see something in the changelog.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to