Why do you think it's Hibernate validator? What do you see in Progress View?
The progress view shows two items "Building Workspace 99%" and "Validating Hibernate (HIBERNATE_XML_FILE_HERE). The HIBERNATE_XML_FILE_HERE changes to the various .hbm.xml files in our project every 20 minutes or so.
I disabled the "Validator" and "Hibernate Builder" Builders for our hibernate project and now the build takes about 80 seconds.
Incidentally, this project is also built using a Maven Script and in NetBeans as well. In both of those environments, builds take anywhere from 60-100 seconds if the Unit Tests are not executed.
The primary difficulty with building in JBoss Tools is that this long build time prevents additional builds from happening. So, while I've made several changes, I can't deploy my WAR files or otherwise test my changes... for hours. I'm inclined to think that I should just keep the Hibernate validation disabled, but then, why use JBoss Tools at all?
BTW, we are using a combination of Seam and IceFaces in our project and were hoping to take advantage of the Seam features of JBoss Tools. I'd really like to get this working. I can't go back to Ganymede for various reasons and I realize that JBoss Tools in 'beta' for Helios at this time.
Once again, any help is greatly appreciated.
OK, cool, thx.
So, in the meantime, I just keep it disabled?
Sad to say, but that's correct.
note Hibernate Builder does nothing, so you coul leave it enabled.
Is another disabled builder's name is "Validation" but not "Validator"?
Does your project have JPA facet enabled?
Could you send me your project ( or it part with hibernate.hbm.xml file and mapped classes)?
As a team, we have since decided against using JBoss and JBoss tools altogether. I have deleted my Eclipse project and we have (unfortunately) returned to using Netbeans and Glassfish.
Ouch Without any concrete examples is going to be hard to track down.
We know there were some older versions where certain constructs caused unneccesary and timeconsuming validations. We fixed those as soon as we could reproduce them.
If you one day have the time to recreate the situation we would appreciate you open a jira or post info here with details on it.