On Tue, 2005-11-08 at 22:36 -0500, David H. DeWolf wrote: > > What are you trying to do exactly? > > I'm attempting to create a plugin which will automate the installation > of the Pluto Portalinto an app server. My requirements go beyond simply > deploying the war as Pluto requires some configuration, integration with > other webapps, and the deployment of shared and endorsed artifacts into > the app server. > > I currently have a version of the plugin that will complete this task > when executed from within a utilities subproject (using the "just > created" artifacts). I'd like to modify the plugin so that the > installation can use artifacts in the repository so that users don't > have to check out the source code first. I'd also prefer not to have > the artifacts embeded within the plugin.
Are you strictly interested in creating a plug-in or are you interested in making a tool that you could use from a different environment, say an Eclipse plug-in? If you are then I would suggest taking a look at the embedder. You could create something with the embedder and then wrap the resulting tool you create in a mojo to make it work within Maven 2.x. http://maven.apache.org/guides/mini/guide-embedding-m2.html Inside a mojo you would then use the @component tag to pull in the embedder but that's the only component you would need as the embedder is really a facade over all the features of Maven we would like to expose to tool integrators. -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org We know what we are, but know not what we may be. -- Shakespeare --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
