Re: Broken Doc Builds

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ò wrote: > Yes, I have experienced the same failures with JDK 8 when building OpenJPA. > > JDK 7 would be fine, but JDK 6 even

Re: Broken Doc Builds

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

Re: Broken Doc Builds

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/

Re: Broken Doc Builds

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

Broken Doc Builds

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