Is there some way to restrict the build to only run on machines that don't have this problem? I've tried to run it for OOZIE-1449 3 times now and all failed because of this.
thanks - Robert On Sat, Jul 13, 2013 at 6:37 PM, Rohini Palaniswamy <[email protected] > wrote: > It happens on some build machines which have jdk versions lesser than < > jdk6u25 . http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6302954 > > On Fri, Jul 12, 2013 at 2:11 PM, Robert Kanter <[email protected]> > wrote: > > > On OOZIE-1449, test-patch keeps complaining that: > > -1 COMPILE > > . -1 HEAD does not compile > > . -1 patch does not compile > > It's happened more than once, so I don't think its the flakiness we > > sometimes get with test-patch > > > > In the output, maven fails to compile the project (before applying the > > patch): > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile > > (default-compile) on project oozie-client: Compilation failure > > [ERROR] > > > /x1/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/client/src/main/java/org/apache/oozie/client/event/jms/JMSMessagingUtils.java:[75,43] > > type parameters of <T>T cannot be determined; no unique maximal > > instance exists for type variable T with upper bounds > > T,org.apache.oozie.client.event.message.EventMessage > > > > > > It compiles locally for me, so I'm not sure what's going on; any ideas? > > > > thanks > > - Robert > > >
