That's right, apart from the fact that maven has a lot of predefined goals Again, and maven-goal is the ant-task closest notion, but it is NOT equivalent. That's why it's very straightforward to parse and display every targets from an ant file, which is not so simple with maven pom and inheritance model.
In ant, only the defined targets exist. In maven, configured plugins can be only a small part of what is actually used. The lifecycle defines a lot of things. But, yes, I guess something could try to analyze the effective-pom to see what's configured and display every goals of every plugins configured... I guess you could file an improvement request about it if you really miss it. But I really think you're gonna argument the whole use-case to attire attention on it. Precisely, how to filter goals and plugins, based on what and so on. Cheers. > -----Message d'origine----- > De : Trevor Harmon [mailto:[email protected]] > Envoyé : lundi 22 décembre 2008 17:17 > À : [email protected] > Objet : Re: [m2eclipse-user] Easier invocation of goals? > > On Dec 19, 2008, at 5:49 PM, MATHUS Baptiste wrote: > > > Click on Maven/Run as/Maven Build, > > In the goal field, click select, you're done for the list of every > > plugins and goals I guess. > > Thanks, but I don't want a list of every goal, just the ones that are > actually available in the current POM. For instance, I have a simple > POM that only adds in the docbkx plugin. Having to go through Run > > Run As > Maven Build... > Select > docbkx > generate-html > OK > Run > is much more tedious and time consuming than, say, Run > Run As > > Maven install. > > It would be nice if Maven could detect the plugins that the POM has > declared and populate the Run As menu accordingly. For example: > > Maven build > Maven clean > Maven docbkx > \- generate-html > generate-pdf > generate-text > Maven install > ... > > This is the kind of thing I'm used to in Ant. For instance, if you add > a new target to an Ant build file, Eclipse will automatically show it > in the Outline pane. You can then can right-click on it, choose Run As > > Ant Build, and Eclipse will run the target. It's that simple. No > need to manually create Run Configurations or pick a goal from a list > of hundreds over and over again. It's disappointing that Maven is a > step down from Ant in this regard. > > Trevor > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
