[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1407: ----------------------------------- Since I'm still receiving the following using the latest JDK 7 build for OSX ... [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test (surefire-idlj) on project jts: Execution surefire-idlj of goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test failed: java.lang.reflect.InvocationTargetException; nested exception is java.lang.reflect.InvocationTargetException: null: com/arjuna/ArjunaOTS/OTSAbstractRecordPOA: com.arjuna.ArjunaOTS.OTSAbstractRecordPOA -> [Help 1] I'm assuming we haven't made the automatic build the default? Building for both ORBs is something that has only just happened. So users currently really don't expect an IDLJ build. However, as a developer what I'd prefer is for the build system to not cr*p out ;-) if it can only find one ORB. If it can't find both and I asked it to build JTS then that's definitely an error. But if I just specify JTS on the build line I think I'm either meaning "Build JTS with JacORB" (given the last 7 years of history) or "Build JTS and I really don't care which ORB you use". Therefore, I suggest changing the build so that it only fails if it can't find either ORB. If it can't find both ORBs then at the end it should print out a message saying which one failed to build. Plus add a jacorb option to the build to correspond to the idlj option, so someone can specify "build jacorb only". This would mean the following: ./build.sh -P jts --> build with any ORB, I really don't care which ./build.sh -P jts idlj --> build with only the IDLJ ORB ./build.sh -P jts jacorb --> build with only JacORB -- 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