Zbyněk,

please open a community jira first if there is not one.

https://hibernate.onjira.com/browse/HV-525

These issues relate to https://hibernate.onjira.com/browse/HV-525 and https://hibernate.onjira.com/browse/HV-528.

Hibernate Validator 4.2.0 is using JDK 6 for building. It has issues when building with JDK7. These issues have been address in the Jiras above and in the HV 4.3.0.Alpha1 release. The 4.3 version compiles and tests successfully against JDK7.

The issues affect only the build and test process.

These tests have been fixed in HV 4.3.0.Alpha1 to make them compatible to run on jDK7 and is expected to fail on HV 4.2.0.Final(version used in EAP 6.0.0.ER3).
This is test-only known issue and we have decided to leave this open until we go for an upgrade of HV in EAP.

I"m resovling this as won't fix, since this only affects test code.

There are some more failures noticed in ER7 on JDK7(Oracle/IBM/OpenJDK) after the previously skipped tests were run in ER7

https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Hibernate/job/EAP6-qa-hibernate-validator-trunk/62/

I am reopening this and marking it to be tracked so that the issue is tracked and we can verify it when we go for a component upgrade for Hibernate Validator

List of some tests failing on all JDK7

org.hibernate.validator.ap.AnnotationTypeValidationTest
org.hibernate.validator.ap.ConstraintValidationProcessorTest
org.hibernate.jsr303.tck.tests.xmlconfiguration.DuplicateConfigurationTest
org.hibernate.jsr303.tck.tests.xmlconfiguration.XmlConfigurationTest
org.hibernate.validator.test.xml.XmlMappingTest

Link: Added: This issue is a dependency of JBPAPP-9188

What's the status on this?  Has there been a component upgrade?  Should I backport HV-528?

[~madhumita12], was there a component upgrade for EAP6?

There was a component upgrade in EAP6.From EAP6 we started using Hibernate-validator-4.2.0.Final and there has been no more upgrades after that so far.
As per my last discussion(with Hardy/Strong) since this affected only test code fixed in HV 4.3.0 we decided to leave it until next upgrade of validators in EAP.
However If you wish to backport the fixes from HV 4.3.0. to 4.2.0 nothing better than that.

FYI, looking at the last set of failing tests:

{quote}
org.hibernate.validator.ap.AnnotationTypeValidationTest
org.hibernate.validator.ap.ConstraintValidationProcessorTest
org.hibernate.jsr303.tck.tests.xmlconfiguration.DuplicateConfigurationTest
org.hibernate.jsr303.tck.tests.xmlconfiguration.XmlConfigurationTest
org.hibernate.validator.test.xml.XmlMappingTest
{quote}

I am not quite sure how they would be connected to HV-525 and HV-528. But then again, I did not see the stack trace or error report. However, I just tested 4.3 again and it compiles/tests fine w/ JDK 7. I was using:

{code}
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /opt/java/maven
Java version: 1.7.0_05, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac"
{code}

[~hardy.ferentschik], I'm running the test suite on the 4.3 branch and had this failure, although the ones originally mentioned worked fine.

OpenJDK7
Maven 3.0.4
Fedora 17

testBeanMetaDataCanBeGarbageCollected(org.hibernate.validator.test.internal.metadata.BeanMetaDataManagerTest): Metadata instances should be garbage collectible

Not sure what else could be different on the CI job's environment.

@Brett, _BeanMetaDataManagerTest_ is a new test in 4.3 so I am not surprised it did not show up before. That the other errors disappeared is a good sign and as mentioned expected.

Is the test failure in _BeanMetaDataManagerTest_ repeatable? The test is trying to force a _OutOfMemoryException_ to verify that afterwards weak references have been cleared. I think we had some problems with the test before and we changed. It might be worth comparing the version on the 4.3 branch with master - https://github.com/hibernate/hibernate-validator/blob/master/engine/src/test/java/org/hibernate/validator/test/internal/metadata/BeanMetaDataManagerTest.java

[~hardy.ferentschik], BeanMetaDataManagerTest fails for me on both 4.3 and master branches, w/ both Sun and OpenJDK 7.  However, everything else seems to pass.  With that test as the exception, we should be all set for the component upgrade.

Hibernate components will be upgraded in EAP 6.1.0.

Release Notes Docs Status: Added: Not Required

Release Notes Docs Status: Removed: Not Required 
Docs QE Status: Removed: NEW