[ http://jira.codehaus.org/browse/MNGECLIPSE-87?page=comments#action_61408 ]
Robert Elliot commented on MNGECLIPSE-87: ----------------------------------------- Narrowed it down - it's J2EE Standard Tools (JST) 1.0.1 that causes the problem. And it definitely does it to the Spring plugin, too - incorrect visibility context menus appearing. I'll look for/raise a bug over at Eclipse. > Enabling Maven on a project does not change the context sensitive menu > ---------------------------------------------------------------------- > > Key: MNGECLIPSE-87 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-87 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.5 > Environment: Eclipse 3.2 M5a > Reporter: Robert Elliot > Assignee: Eugene Kuleshov > > > 1) Create a new Java project in Eclipse 3.2 M5a > 2) Right click on the project, and in the resulting context sensitive menu go > to Maven2 -> Enable > 3) Complete the wizard, making this a Maven enabled project > 4) Notice that the Maven nature & builder is correctly added to the .project > file > 5) Notice that the Maven icon is not added to the Project > 6) Right click on the project, and in the resulting context sensitive menu go > to Maven2. Notice that the only available option is still "Enable" - you > cannot disable or add dependencies. > 7) Notice that you can right-click on the pom and add dependencies. > No errors in the m2 console, nor anything immediately obvious in the debug > output. Don't currently understand Eclipse plugins well enough to work it > out from the code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
