m2eclipse dependency search problem workaround

 

m2eclipse Issues Mailing List - [m2e issues] [JIRA] Created- (MNGECLIPSE-2130) Open Type from Ma

Open Type from Maven..., dependency resolution, and Select... goals buttons do not work out of the box
------------------------------------------------------------------------------------------------------
                 Key: MNGECLIPSE-2130
                 URL: http://issues.sonatype.org/browse/MNGECLIPSE-2130
             Project: Dev - M2E - OSS
          Issue Type: Bug
    Affects Versions: 0.10.0
         Environment: eclipse 3.4.2
            Reporter: Greg Loring
install eclipse and m2e as per instructional video (no extras)
open the "Search class in Maven repositories" dialog via Navigate / Open Type from Maven...
type in org.apache.commons.logging.LogFactory or just LogFactory
see "Results for ... (0)" at the bottom of the dialog
same behavior if "Search class in Maven repositories" dialog is reached via the "Search dependency for LogFactory" quick fix
also, no goals will appear in the "Select Goal" dialog no matter where it is started from:
- Window / Preferences / Maven / "Goals to run on project import:"
- Window / Preferences / Maven / "Goals to run when updating project configuration:"
- Project / Properties / Maven / Lifecycle Mapping / "Goals to invoke after project clean:"
- Project / Properties / Maven / Lifecycle Mapping / "Goals to invoke on resource changes (...)"
one workaround (there may be others):
open the "Maven Repositories" view
right click on "Global Repositories" / "central (http://repo1..." node
click on "Full Index Enabled" (and wait for a long time while eclipse stops responding)
then the "Search class in Maven repositories" and "Select Goal" dialogs start working
COMMENT: found this workaround after a ridiculous amount of searching the web and sonatype jira; this basic functionality should just work, period
setting the central repository back to "Minimum Index Enabled" turns the class search and goal selecting functionality off once again
have not tried to see how all this affected artifacts that are not in central
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:http://issues.sonatype.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira