Re: own plugin without need for pom.xml

2007-12-14 Thread Peter Fischer
Hello, next question? ;) The DeployFileMojo uses a method getDeployer() of the AbstractDeployMojo class; I also tried to extend the AbstractDeployMojo class, but now getDeployer() returns only null. What do I wrong? regards, Peter -- View this message in context: http://www.nabble.com/own-pl

Re: own plugin without need for pom.xml

2007-12-14 Thread Peter Fischer
Hello, I use maven as build-tool and need many not mavenized equinox-bundles in an internal project (gmf, ...). Upgrading to a new version of this set of bundles is much stupid work. struberg wrote: > > Peter, just out of curiosity: How do you decide which groupId, artifactId > and versionId y

RE: own plugin without need for pom.xml

2007-12-13 Thread Peter Fischer
Hello, struberg 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 > This works fine. Thank you! regars, Peter -- View this message in context: http://www.nabble.com/ow

own plugin without need for pom.xml

2007-12-13 Thread Peter Fischer
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 pro