Calling a custom maven plugin

I could get it to run that way if I changed the groupId of my mojo to "org.apache.maven.plugins". It seems rather inappropriate to use this groupId myself? Is there another way to get my mojo to run without having to be so verbose? Thanks very much. -- Tristan JC Rouse

Resolving artifacts in Maven API

ct a DefaultArtifactRepository *or better yet*, get maven to instantiate an ArtifactRepository for me configured to represent the local repository, etc would be greatly appreciated. Thanks! PS Is there really that little human written information in the javadocs? -- Tristan JC Rouse

Re: Resolving artifacts in Maven API

I apologize for rewriting this without seeing Benjamin Bentmann's response to my earlier letter. I fail at using mailing lists. Thanks very much for the response. On Fri, Sep 18, 2009 at 3:30 PM, Tristan JC Rouse < tris...@tristanjcrouse.com> wrote: > Hi, > > I'm trying

Plugin Development: resolving arbitrary artifacts

y and update the value returned by the Artifact.getFile() method. I could be off base here. Any input on how to accomplish these tasks in maven is greatly appreciated. Thanks -- Tristan JC Rouse