have a look at how it is done via mvn help:effective-pom
- Kristian On Sat, Sep 24, 2011 at 4:54 PM, Andy Glick <[email protected]> wrote: > You would normally do this by using a pluginManagement tag in your pom and > in that context declaring the plugin and setting the version to 2.7. This is > particularly useful in a parent pom because the version will be inherited by > all child poms. Then you would not include the version tag in the plugin > declaration in the plugins tag. > > I think that it may be possible to configure this in a site super pom. > > On 9/24/11 6:22 AM, Jonny Andersson wrote: >> >> Hi! >> >> I have a question that I guess already have been asked somewhere but I >> have not been able to find the answer myself. The question came up when I >> ran the command mvn deploy:deploy-file on the command line and found that >> the arg sources (given as -Dsources=...) wasn't recognized. It turned out >> that the command mvn deploy:deploy file always resolves to version 2.5 >> >> mvn org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy-file >> >> where I would like it to resolve to resolve to version 2.7 >> >> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file >> >> as that version have the sources arg as an option so the question is, is >> it possible to configure which version of the plugin the unqualified >> commands for a plugin like mvn deploy:deploy-file should resolve to? >> >> I use Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) in Win XP with java >> 1.6.0 >> >> Thanks for any information about this! >> >> Jonny Andersson >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
