[ http://jira.codehaus.org/browse/MNG-1446?page=comments#action_51636 ]
Dave Sag commented on MNG-1446: ------------------------------- yes that's fine for setting general plugin congigs but each specific goal has its own config deatails which seeming can not be configured independently. so i'll modify my last statment to say Currently is it not possible, save in the most trivial of circumstances, to configure goals that are not bound to a lifecycle phase. what was the reasoning behind the 'no goal config' idea? why should i have to have differnet names for inputFile? This seems like an entireky unreasonable restriction. but as i said previously - i got around it by binding the goal to a lifecycle phase and simply avoiding the commandline use. > 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]
