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 > -- > View this message in context: > http://www.nabble.com/own-plugin-without-need-for-pom.xml-tp14318109s177p14318109.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und viel mehr bietet das neue Yahoo! Mail - www.yahoo.de/mail --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
