I see - these are already generated archetypes. Let me be more clear: I have an
example project that has the archetype plugin set to “create-from-project” and
then install the archetype.
<plugin>
<artifactId>maven-archetype-plugin</artifactId>
<version>2.4</version>
<executions>
<execution>
<id>deploy</id>
<phase>deploy</phase>
<goals>
<goal>create-from-project</goal>
</goals>
<configuration>
<archetypePostPhase>deploy</archetypePostPhase>
</configuration>
</execution>
<execution>
<id>package</id>
<phase>package</phase>
<goals>
<goal>create-from-project</goal>
</goals>
<configuration>
<archetypePostPhase>install</archetypePostPhase>
</configuration>
</execution>
</executions>
<configuration>
<propertyFile>${project.basedir}/archetype.properties</propertyFile>
</configuration>
</plugin>
On August 17, 2015 at 7:33:21 AM, Thomas Broyer ([email protected]) wrote:
On Mon, Aug 17, 2015 at 2:27 PM Jordan Zimmerman <[email protected]>
wrote:
I want the whole project as an archetype - from the parent down. You can’t make
the parent pom’s packaging maven-archetype. Right?
Each module of gwt-maven-archetypes is an archetype *for a multimodule
project*. (sources for each is in src/main/resources/archetype-resources
though; so the projects cannot be used as examples at the same time)
On August 17, 2015 at 7:24:54 AM, Thomas Broyer ([email protected]) wrote:
On Mon, Aug 17, 2015 at 2:15 PM Jordan Zimmerman <[email protected]>
wrote:
> I’m not using packaging “maven-archetype”. It doesn’t seem to work with
> multi-module projects.
Works pretty-well for me: https://github.com/tbroyer/gwt-maven-archetypes/
