Vincent Massol wrote: >Could you please explain the rationale for this? > > I was getting annoyed at guessing between [plugin-name], report and generate.
Since some plugins have more than one report, I picked the one people are probably most familiar with. It's the primary purpose the plugin. Eg. Changelog has "changelog:changelog", "changelog:dev-activity", "changelog:file-activity". Would you make the first :report and append -report to the others? append -report to the first? Rename the plugin to maven-scm-reports (which we've discussed too :) It was also the least number of changes to make. >I'm quite strongly against it unless there is a very good reason which I >don't see ATM (I don't consider the fact that other plugins do it a good >enough reason - I think they are also wrong ;-)). > > I think its right for the reasons above, but we can discuss/change before the next releases. >The reasons I don't like it: > >- The name clover for a goal doesn't mean anything. "clover:report" is much >better than "clover:clover" for understanding what the goal does. > > It doesn't execute clover on it? What would you rename jar:jar to then? >- I don't think the report goal should be more important than another one in >the Clover plugin. There are different goals that do different things >(clover:check, clover:report, etc). > > You don't think that it is what most people expect as the default behaviour? >I would be ok (even though I don't like particularly like it) to create >another Mojo mapped to the clover goal and that would delegate to the >clover:report. > It would be better to allow aliasing, though I'd rather it be easier to know what is the right one upfront. >I think your motivation comes from the fact that there is a >clover:clover goal in m1, right? > > No, but I'm sure it had its reasons. >Of course I would even prefer a goal aliasing mechanism or a new default >goal javadoc parameter (@default-goal) to specify a default plugin goal when >it makes sense. This goal could be called when [plugin name]:[plugin name] >is called and if none are defined an error saying that the plugin has no >default goal would be displayed, possibly listing all the available goals. > > Just as easy to alias individual goals that to introduce any special default syntax. I understand your point, but I don't agree at this juncture. Let's here what others have to say. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
