[
http://opensource.atlassian.com/projects/hibernate/browse/HV-137?page=com...
]
Hardy Ferentschik commented on HV-137:
--------------------------------------
I looked at the patch and it does not seem to include archetype.xml. This way the
archetype creation will only work with the catalog approach. I think we should also
support the more explicit way by specifying properties on the command line.
I am also wondering whether we should use packaged="false" in the archetype
descriptor. Basically we would use fixed package names, for example
org.hibernate.validator.quickstart. This way we can actually import the archetype as
another module into the IDE and change/refactor the files.
Another maybe even better idea is to have a 'normal' maven project under
hibernate-validator-archetype. It would contain the model and test classes. Then at
build-time we call 'archetype:create-from-project' to actually dynamically create
the archetype. This way we can easily maintain the actual code, but also get the benefit
of an archetype.
Create a Hibernate Validator maven archetype
--------------------------------------------
Key: HV-137
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-137
Project: Hibernate Validator
Issue Type: Task
Components: documentation
Reporter: Hardy Ferentschik
Fix For: 4.0.0.Beta1
Attachments: archetype.patch
Creating and deploying a HV maven archetype will make it even easier for people to get
started and we can use the archetype to keep some of the example classes.
We can add the archetype just as another submodule
--
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