Before open source version discontinued their support of Oracle db, I had the system working. My problem was upgrading to the 6.2.0 version. I narrowed it down to the upgrade script did not set permissions on a table there by giving me problems.
I found I had two issues. The first was security for the user I was trying to run the build process. Once I got that all worked out. I found a second problem, which was the one above. I actually found a work around. The default_master.properties file has a property called maven-localrepo-path. If this is set to the path of where the jasperserver-repo is located it seems to pick up the artifact correctly. The maven process must have not been retrieving the pom correctly or maybe it was my adding the jboss repo to my settings.xml. I did both so either could have fixed the problem.
