Trevor It isn't the same. There are many plugins defined in the super POM that are automatically inherited. Your list would be quite long if you tried to do what you are thinking.
I also think you are kind of missing one of the major points of Maven. You shouldn't have to put project specific goals in the UI. Those things go in the POM but should be executed seemlessly under the hood without a dev knowing that the build needs to do execute particular goal. For instance, as a developer on your project just getting up to speed, I shouldn't have to know that there even is a docbkx goal defined in your POM in order to do a build. All I should need to know are the core life cycle phases like package, install, deploy, site, etc... If your project needs to do some some docbkx stuff, then that stuff should be bound to the appropriate place in the lifecycle. One of key benefits of Maven is that it provides this convention on all Maven projects. You don't have to learn specific ant targets when going from one project to the next. It is a differnt way of thinking over ant and I admit it does take some getting used to. Good luck. --- Todd Thiessen > -----Original Message----- > From: Trevor Harmon [mailto:[email protected]] > Sent: Monday, December 22, 2008 11:17 AM > To: [email protected] > Subject: 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
