I’m not using packaging “maven-archetype”. It doesn’t seem to work with multi-module projects. I’m merely adding the archetype plugin to my example project and building the archetype on package phase.
-Jordan On August 17, 2015 at 12:45:39 AM, Hervé BOUTEMY ([email protected]) wrote: Hi, This is unusual: how do you build it once as a project and once as an archetype? Because, in general, the build as archetype is done by definig "maven- archetype" packaging [1], which makes the project unusable as direct project Regards, Hervé [1] http://maven.apache.org/archetype/archetype-packaging/ Le dimanche 16 août 2015 18:38:21 Jordan Zimmerman a écrit : > Hi, > > I have an example project that also serves as source for an archetype. So, > the pom has: > > <build> > <plugins> > <plugin> > <artifactId>maven-archetype-plugin</artifactId> > …. > </plugin> > </plugins> > </build> > > Of course, this means that the resulting archetype has this in its POM. Is > there any way to filter this out? Is there another plugin I can use in > conjunction with the archetype plugin? Or maybe this would make for a good > addition to the archetype plugin itself. > > Thoughts? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
