Community
Participate
Working Groups
Steps to reproduce: 1) From any Maven/m2e-enabled project, right-click, Run As, "5 Maven Build...". 2) In the "Edit Configuration" dialog that is shown, next to the "Goals" text box, click on the "Select..." button. 3) Observe that the UI hangs for a few seconds while the system exhibits high CPU, then a "Goals" dialog is shown with an empty list, above a red 'X' and a "No entries available" message. There also is a "Use Qualified Name" checkbox that is checked by default, and unchecking it doesn't modify the result. Typing something in the "Select Goal" textbox at the top of the dialog (assuming maybe the list is only for auto-complete) also has no effect. Manually typing in goals, e.g. "clean package" allows a build to successfully complete as expected.
Using "m2e - Maven Integration for Eclipse (Incubation) 0.13.0.201104282116 org.eclipse.m2e.feature.feature.group".
Any updates on this? Same issue with m2e 1.0.100.20110804-1717.
Any updates on this? This bug seem to have been abandoned even though it's not fixed yet.
I have no plans to implement this using existing maven-indexer backend, but if somebody provides a quality patch I will review and apply it.
Until if/when this is properly fixed, can the "Select..." button at least be hidden or removed? As-is, it looks like a rather glaring bug, instead of missing functionality. (Is there ever a case where this dialog will be populated, without first fixing something else?)
Hey guys, I have had this problem for a few releases. I keep forgetting it is a bug and search all over the internet to find the fix. Keep returning to this bug. I think the best solution for now is to remove the select button so people know they have to enter the entries themselves. It would save people time searching the internet to fix this problem that they can not fix. My Version m2e 1.2.0.20120903-1050 Eclipse Version: 3.8.1
Couldn't agree more. I also thought that I did not have the option of simply typing a maven command there. That button should be removed indeed.
Please consider contributing a quality patch. No immediate plan to work on this otherwise.
Are there any other reasons to keep this "Select.." button? (I.E., does it have any other usages or purpose that I might not be aware of?) Or might a patch to simply remove this button be the most appropriate here?
If goals lookup is completely broken, then yes, removing the button seems reasonable.
If there is no one coming up with a patch, can that button please be removed?
*** Bug 434653 has been marked as a duplicate of this bug. ***
What would be the best way to fix this? I guess the question is really, "how can the eclipse m2e list/access the currently available lifecycle and goals for the current selected eclipse project?" Would it be via: a) information on the pox.xml or 'Effective POM'? (btw, is there an in-memory representation of these objects?) b) executing 'mvc' on the console (or in memory) and parsing the error message shown? [ERROR] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-site, site, post-site, site-deploy, pre-clean, clean, post-clean. -> [Help 1] Question on b), is there a maven command to list the currently available lifecycles and goals?
Maven supports two types of goals: lifecycle phase names and maven plugin goals. Available lifecycle phase names come from the default lifecycle, which is part of maven core, but can also come project build extensions. It is probably ok to ignore project build extensions. Default lifecycle changes very infrequently, so it is probably okay to simply hardcode the names/ List of available plugin goals, on the other hand, depends on contents of maven repositories accessible by the project and there is currently no reliable and efficient way to get the list. As was suggested in comment #5, the easiest fix is probably to disable or remove the button.
(In reply to Igor Fedorenko from comment #14) > As was suggested in comment #5, the easiest fix is probably to disable or > remove the button. This is a possible patch, I created it without testing it. (I face the issue described in Bug 441506, once I get over this I can validate this patch to see if does what I think it does). https://git.eclipse.org/r/31380
Applied the patch, thank you.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
