[ http://jira.codehaus.org/browse/MNG-1446?page=comments#action_51621 ]
Dave Sag commented on MNG-1446: ------------------------------- so are you saying there is no way to configure plugins that are not bound to part of the lifecycle? i have got around this by simply binding all my goals to the lifecycle and not even trying to run mvn qalab:merge > unable to config goals that are not bound to part of the standard lifecycle > --------------------------------------------------------------------------- > > Key: MNG-1446 > URL: http://jira.codehaus.org/browse/MNG-1446 > Project: Maven 2 > Type: Bug > Versions: 2.0 > Reporter: Dave Sag > Assignee: John Casey > > Original Estimate: 2 hours > Remaining: 2 hours > > My QALab plugin has three different goals and only a few of their config > params are in common with each other. so each goal must have its own config. > So right now, for simplicity's sake, I just want the qalab:merge goal to work > when i enter %mvn qalab:merge > my build section is as follows: > <build> > <plugins> > <plugin> > <groupId>net.objectlab</groupId> > <artifactId>maven-qalab-plugin</artifactId> > <executions> > <execution> > <configuration> > > <handler>net.objectlab.qalab.parser.CheckstyleStatMerge</handler> > > <inputFile>${project.build.directory}/checkstyle-result.xml</inputFile> > </configuration> > <goals> > <goal>merge</goal> > </goals> > </execution> > </executions> > </plugin> > </plugins> > </build> > when I try %mvn qalab:merge > i get > [ERROR] BUILD ERROR > [INFO] > ---------------------------------------------------------------------------- > [INFO] One or more required plugin parameters are invalid/missing for > 'qalab:merge' > [0] inside the definition for plugin: 'maven-qalab-plugin'specify the > following: > <configuration> > ... > <handler>VALUE</handler> > </configuration>. > [1] inside the definition for plugin: 'maven-qalab-plugin'specify the > following: > <configuration> > ... > <inputFile>VALUE</inputFile> > </configuration>. > if i move the config from the executions block such that it is like so: > <plugin> > <groupId>net.objectlab</groupId> > <artifactId>maven-qalab-plugin</artifactId> > <configuration> > <handler>net.objectlab.qalab.parser.CheckstyleStatMerge</handler> > > <inputFile>${project.build.directory}/checkstyle-result.xml</inputFile> > </configuration> > </plugin> > then the params are accepted, but now I can't have different params for the > different goals, indeed i can't see how i'd go about specifying different > configs for the different goals in such a case. I need goal specific > parameter config, not plugin-wide config. or should I make these goals into > totally different plugins instead? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]