[ http://opensource.atlassian.com/projects/hibernate/browse/HV-137?page=com... ] Gunnar Morling updated HV-137: ------------------------------ Attachment: archetype.patch Hardy, please find attached my patch for the HV archetype. Upon instantiation it will create a project with the Car and CarTest classes from the "Getting started" section of the reference guide. I'm not yet totally sure about a versioning scheme for the archetype. I think in the projects created by the archetype always the newest HV version should be referenced, which probably means that also a new version of the archetype project is required, whenever a new HV version comes out. Therefore I added the archetype project as module to the parent POM. The HV version is hard-coded to 4.0.0.Beta1-SNAPSHOT in archetype-resources/pom.xml for now. If we decide to update the archetype with each new HV version, here the HV version as specified in the parent POM could be used, but unfortunately right now I am not aware of any way to reference this version in the pom.xml for the instance projects (filtering the pom.xml doesn't seem to work as expected). Another question is how users should reference the archetype. I like the concept of archetype catalogs. If a file archetype-catalog.xml with the contents <?xml version="1.0" encoding="UTF-8"?> <archetype-catalog> <archetypes> <archetype> <groupId>org.hibernate</groupId> <artifactId>hibernate-validator-archetype</artifactId> <version>LATEST</version> <repository>http://repository.jboss.com/maven2/</repository> <description>Archetype for creating the Hibernate Validator Quickstart project</description> </archetype> </archetypes> </archetype-catalog> was published to the JBoss Maven repository, end users could use the archetype as follows: mvn archetype:generate -DarchetypeCatalog=http://repository.jboss.com/maven2/archetype-catalog.xml WDYT? Gunnar -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-137?page=com... ] Hardy Ferentschik commented on HV-137: -------------------------------------- I actually committed now some code which would use the latter approach. WDYT? -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-137?page=com... ] Hardy Ferentschik commented on HV-137: -------------------------------------- What I meant with "specifying properties on the command line" was to use the syntax without specifiying archetypeRepository. This does not work without archetype.xml. Turns out that 'archetype:generate' generated both - archetype-metadata.xml and archetype.xml. I guess there is no need to explicitly delete the latter. -- 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