Hi Dan, > Welcome on board,
Thanks :-) > latext > pom.xml > latext-maven-shared > latext-maven-plugin > lalext-maven-achetype Ok > The shared project is optional, but I truely believe it is the way to > go so that other plugin/app can reuse your component directly > This is from my experience working with truezip and wagon ( have not > had time to split them yet ) I'm not sure it's worth having a shared project, as the plugin is really a unique small Java class... I will refactor the plugin structure with an intermediary pom-packaged parent project, and the plugin and archetype as child projects. BTW I could not come up with an easy solution for writing tests, as the plugin relies on external executable to be launched. Any idea? Cheers -- http://izpack.org/ http://jpz-log.info/ http://julien.ponge.info/ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
