I was missing the groupId...that fixes it...many thanks. -Dave
On Thu, Sep 24, 2015 at 12:28 PM, Robert Scholte <[email protected]> wrote: > Hi, > > if there is generated documentation for the goal, you should be able to > see it. > E.g. compile:compile [1] > > You can call this by its full name, i.e. > org.apache.maven.plugins:maven-compiler-plugin:3.3:compile > The version is optional, Maven will look for a matching version in the > pom.xml first > > thanks, > Robert > > > [1] > http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html > > > Op Thu, 24 Sep 2015 19:59:30 +0200 schreef David Hoffer < > [email protected]>: > > > I'm trying to add the following plugin to my build but the goal prefix is >> license which conflicts with maven-license-plugin used in my parent pom. >> I >> can't change the parent so how do I handle multiple plugins that both have >> a goal prefix of license? Note in my pom I want to run some license goals >> from the command line and also bind other goals to phases. It's the >> command line goals I'm currently having trouble with. >> >> How can I run the goal with the fully qualified plugin name or is there >> another way to do this? >> >> >> <groupId>com.mycila</groupId> >> <artifactId>license-maven-plugin</artifactId> >> >> -Dave >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
