[
http://opensource.atlassian.com/projects/hibernate/browse/HV-185?page=com...
]
Hardy Ferentschik commented on HV-185:
--------------------------------------
I did a little test to check whether a package renaming of the new hibernate code would
conflict with any class from the legacy validator. This is not the case.
Here is what I've done. For each code base I dumped all java file names into a text
file. In case of the new code I also renamed 'validation' to 'validator':
find hibernate-validator/src/main/java/ -name "*.java" | sed -e
's@/validation/@/validator/@g' | sort > hibernate-validator-classes.txt
find hibernate-validator-legacy/src/main/java/ -name "*.java" | sort >
hibernate-validator-legacy-classes.txt
comm -1 -2 hibernate-validator-legacy-classes.txt hibernate-validator-classes.txt
There were common classes, hence renaming would not cause any class conflicts.
Change package name in codebase from org.hibernate.validation to
org.hibernate.validator
----------------------------------------------------------------------------------------
Key: HV-185
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-185
Project: Hibernate Validator
Issue Type: Improvement
Components: engine
Affects Versions: 4.0.0.Beta2
Reporter: Hardy Ferentschik
Fix For: 4.0.0.CR1
Need to think about this one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira