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 >
