Opened https://issues.apache.org/jira/browse/INFRA-12170 to request JDK 6 or 7 to be used.
On Fri, Jun 24, 2016 at 2:34 AM, Francesco Chicchiriccò <[email protected] > wrote: > Yes, I have experienced the same failures with JDK 8 when building OpenJPA. > > JDK 7 would be fine, but JDK 6 even better since we are retaining > compatibility with Java 6. > > I am completely unfamiliar with buildbot: should we open an issue to > INFRA, maybe? > > Regards. > > > On 23/06/2016 22:56, Jody Grassel wrote: > >> Looks like it might have pulled in my changes after all, but looking at >> the >> errors: >> >> javadoc: warning - Error fetching URL: >> http://commons.apache.org/collections/api-release/ >> >> >> /Users/jgrassel/Documents/Development/JPA/OpenJPA/2.2.x/openjpa-lib/src/main/java/org/apache/openjpa/lib/ant/AbstractTask.java:75: >> warning: no @param for haltOnError >> >> public void setHaltOnError(boolean haltOnError) { >> >> >> I did notice that 2.2.x is running with java 8: >> >> Command line was: /usr/lib/jvm/java-8-oracle/jre/../bin/javadoc >> -J-Xmx1024m @options >> >> While trunk appears to be running with java 7 ( >> >> https://ci.apache.org/builders/openjpa-trunk-docs/builds/338/steps/compile/logs/stdio >> ): >> >> JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk-amd64 >> >> After a bit of searching, it sounds like Java 8 made checking more >> stricter, which the 2.2.x build is running afoul of. Is there any chance >> of getting the 2.2.x doc build to run with java 7 (which is what I used to >> pass my local sandbox, switching to Java 8 my sandbox fails the same way >> as >> the nightly build.) >> >> On Thu, Jun 23, 2016 at 9:28 AM, Jody Grassel <[email protected]> wrote: >> >> Ok, so I had checked in 1749783, which maven completed successfully in my >>> local sandbox. However, it looks like last night's build ( >>> https://ci.apache.org/builders/openjpa-2.2.x-docs/builds/325 ) picked up >>> a mid-may revision instead of the latest revision (that integrated to >>> trunk, no less, not 2.2.x.) Any suggestions on how to force it to pick >>> up >>> the new 2.2.x track? >>> >>> On Fri, Jun 17, 2016 at 1:57 PM, Jody Grassel <[email protected]> >>> wrote: >>> >>> Locally, the changes I posted to OPENJPA-2645 allow my maven build to >>>> complete successfully. By in large, most of the changes have been >>>> poached >>>> from trunk, though I had to force the use of newer maven plugins on some >>>> occasions (such as maven-assembly-plugin). Does anyone have any >>>> objections >>>> to the proposed patch? >>>> >>>> Patch can be tested by applying, and then executing at the branch root: >>>> mvn -U clean site install -DskipTests -Pjavadoc-profile,docbook-profile >>>> >>> > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Involved at The Apache Software Foundation: > member, Syncope PMC chair, Cocoon PMC, Olingo PMC, > CXF Committer, OpenJPA Committer, PonyMail PPMC > http://home.apache.org/~ilgrosso/ > >
