[
http://opensource.atlassian.com/projects/hibernate/browse/HV-137?page=com...
]
Gunnar Morling commented on HV-137:
-----------------------------------
Hi,
According to
http://jira.codehaus.org/browse/ARCHETYPE-152 archetype.xml seems to be
obsolete and replaced by archetype-metadata.xml with version 2.0 of the Maven archetype
plugin. Therefore I removed the archetype.xml file.
I am not sure what you mean by "I think we should also support the more explicit way
by specifying properties on the command line."?
The archetype catalog should only be relevant for end users but not for the creation of
the archetype. End users could either refer to the catalog file:
mvn archetype:generate
-DarchetypeCatalog=http://repository.jboss.com/maven2/archetype-catalog.xml
and then choose the archetype from which an instance project shall be created from a list
with all archetypes of the catalog.
Or they can refer directly to the archetype by archetypeRepository, archetypeArtifactId
and archetypeGroupId:
mvn archetype:generate -DarchetypeGroupId=org.hibernate
-DarchetypeArtifactId=hibernate-validator-archetype
-DarchetypeRepository=http://repository.jboss.com/maven2/
I like the idea of having an instance project in SVN and creating the archetype on the fly
from it. After calling archetype:create-from-project the generated archetype project would
have to be built, too in order to deploy it to the local/JBoss Maven repo (while the
instance project JAR shouldn't be deployed at all).
And the instance project would have to be renamed (e.g. to
hibernate-validator-quickstart), as archetype:create-from-project will add
"-archetype" to the artifactId of the generated archetype, currently resulting
in hibernate-validator-archetype-archetype probably.
Gunnar
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