Peter, just out of curiosity: How do you decide which groupId, artifactId and
versionId you should
take for each jar?
txs,
strub
--- Wayne Fay <[EMAIL PROTECTED]> schrieb:
> Peter, I hope you will consider donating this plugin to the Mojo
> project. A number of people have asked about this exact thing on this
> list in the last year or so.
>
> Wayne
>
> On 12/13/07, Mark Struberg <[EMAIL PROTECTED]> wrote:
> > Simply add
> >
> > @requiresProject false
> >
> > to your mojo.
> > An example of this usage can e.g. be found in the maven-archetype-plugin.
> > LieGrü,
> > strub
> >
> > --- Peter Fischer <[EMAIL PROTECTED]> schrieb:
> > > Hello,
> > >
> > > I want to write my own deploy-plugin, which takes a directory and deploys
> > > all contained jars.
> > > In this scenario, I don't need a pom.xml like for "mvn deploy:deploy-file
> > > ...".
> > >
> > > But if I use my own plugin, maven shows me the error:
> > >
> > > [INFO] Cannot execute mojo: bundlesdeploy. It requires a project with an
> > > existing pom.xml, but the build is not using one.
> > >
> > > How can I avoid this error?
> > >
> > > regards,
> > > Peter
__________________________________ Ihr erstes Baby? Holen Sie sich
Tipps von anderen Eltern. www.yahoo.de/clever
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
