Bugzilla – Full Text Bug Listing
| Summary: | Run As Maven package is missing | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Tim Ames <tim.ames> |
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Dieter.Koenig, gayanper, igor, robn |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Tim Ames
FYI, we plan to get rid of all static RunAs->MavenNNN entries except Build... but introduce history of most recently executed maven builds. There are no plans to (re)introduce additional static RunAs->MavenNNN entries. What should i say? Do you still want that m2e is gonna being used? If m2e people will continue to do that way, there will be soon an another eclipse maven plugin which is going to serve the needs of people. When you develop m2e you may not think like maven developers did or maybe still do: "maven/m2e is gonna being used only for java projects". In fact the reality is maven has replaced ant. And as you know ant was used to build everything. So m2e should not just provide workspace resolution and that's it... Its very annoying if you have to switch to console just for doing a fast "mvn package" test or define run configurations for tons of projects. This is then explicitly needed for projects that are not some kind of 'simple java' (jar, war, ...). P.S.: And please do one of the following: 1. Remove support for external maven installations 2. Support external maven installations properly. To 1.: This will probably increase the speed people stop using m2e and itroduce some "maven 2"-version of it or whatever. To 2.: If it is said "use maven 2" than use maven 2 for everything (also workspace resolution and so on). People CANT switch in 5 minutes from maven 2 to maven 3 but applying maven 3 gives tons of compile errors as for example some poms of plugin dependencies can be maven-3-incompatible. And you may not have the time to adapt this plugin at this point and so on. You do know that you can run package (or, better yet, "clean package") through RunAs->MavenBuild..., right? I plan to eventually get rid of all predefined run-as->maven launch configurations. (In reply to Igor Fedorenko from comment #4) > I plan to eventually get rid of all predefined run-as->maven launch > configurations. How about a kind of community process to decide such things? Adding more and more commands to Run-As menu does not scale. I am willing to bet most of existing predefined commands are never used for the same project, so they just clutter the UI. And, obviously, it is not possible to add all useful "mvn xxx" commands and their permutations to Run-As menu. This is a usability problem and I don't want to make it worse. Please provide a quality patch that improves usability of Run-As Maven UI and I'll review the patch and give my feedback. Thanks to the original poster about this bug. I've been using m2e for many years and have always been baffled by mvn package missing. Glad to see I am not alone.
Currently I make a generic Run Configuration that will package the current project:
Name: mvn package
Base Dir: ${project_loc}
Goals: package
When the m2e menu items for install and clean are eventually removed (as advised by Igor) I will do likewise for them.
Once you create these generic run configurations for standard maven commands and use them once, you then have them in your Run History so you can execute them easily enough.
I can see Igor's point of view but having all the fundamental maven commands in the menu would be a good thing.
*** Bug 562614 has been marked as a duplicate of this bug. *** |