On Mon, 9 Dec 2002 23:13, Nathan Coast wrote:
> you can define tasks for a specific project within the maven.xml for that
> project. or if you wish to use the plugins across a number of projects,
> create a plugin and install it. The simplest way to create a plugin is to
> do a full cvs checkout of maven, and copy the plugin structure of one of
> the plugins beneath jakarta-turbine-maven/src/plugins-build. Once you have
> written the plugin by modifying the plugin.xml, plugin.properties and
> writing any sources java, xml etc, install it by executing:
>
> jakarta-turbine-maven>maven maven:plugin -Dplugin.name=foo-plugin
Thanks - I sorta get that.
I am defining a plugin and I want to use it in 30 or so projects. This plugin
essentially essentially deals with the way that distributions are built. I
would like to have some way to define that the plugin is needed so that users
would not have t0o manually much about with their maven install.
I would also like a way to have a generic maven.xml so that everyone of those
projects don't have to add the same customizations.
Is any of this possible?
--
Cheers,
Peter Donald
Doubt is not a pleasant condition, but certainty is absurd.
-- Voltaire
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
