You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Elliot (JIRA)" <ji...@codehaus.org> on 2006/03/16 21:39:13 UTC

[jira] Created: (MNGECLIPSE-87) Enabling Maven on a project does not change the context sensitive menu

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
 Assigned to: 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


[jira] Commented: (MNGECLIPSE-87) Enabling Maven on a project does not change the context sensitive menu

Posted by "Robert Elliot (JIRA)" <ji...@codehaus.org>.
    [ 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


[jira] Commented: (MNGECLIPSE-87) Enabling Maven on a project does not change the context sensitive menu

Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNGECLIPSE-87?page=comments#action_61282 ] 

Eugene Kuleshov commented on MNGECLIPSE-87:
-------------------------------------------

Robert, please clarify following:

-- Is "Maven2 Decoratior" enabled in General / Appearance / Label Decorations ?
-- What Eclipse view you are using to work with your projects? Please try and confirm about "Package Explorer" view 
-- What JRE you are using to run Eclipse?

Also, check .log file under .metadata in your workspace (or Error Log view) for any exceptions in the pluin code.

> 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


[jira] Commented: (MNGECLIPSE-87) Enabling Maven on a project does not change the context sensitive menu

Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNGECLIPSE-87?page=comments#action_61289 ] 

Eugene Kuleshov commented on MNGECLIPSE-87:
-------------------------------------------

Robert, I don't have time to check it on 3.2M5a now, but it is working on 3.2M5 (not "a"). "a" build suppose to fix some backward incompatibilities for ancient plugins, but I am not sure if there is anything else. If you can try on 3.2M5 and let us know here it would save us some time... Thanks.

> 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


[jira] Commented: (MNGECLIPSE-87) Enabling Maven on a project does not change the context sensitive menu

Posted by "Robert Elliot (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNGECLIPSE-87?page=comments#action_61301 ] 

Robert Elliot commented on MNGECLIPSE-87:
-----------------------------------------

Chased it down a bit further; it's not M5a that's the issue, it's the Web Standard Tools or one of its dependencies.  With a vanilla M5 install it works as expected; add in the WST (and J2EE) stuff and I get the behaviour described above.  Tomorrow I'll try and track it down further - might be GET or VE or something like that that is the real culprit.

> 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


[jira] Commented: (MNGECLIPSE-87) Enabling Maven on a project does not change the context sensitive menu

Posted by "Robert Elliot (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNGECLIPSE-87?page=comments#action_61288 ] 

Robert Elliot commented on MNGECLIPSE-87:
-----------------------------------------

- Is "Maven2 Decoratior" enabled in General / Appearance / Label Decorations ?

Yes

- What Eclipse view you are using to work with your projects? Please try and confirm about "Package Explorer" view 

Package Explorer and Navigator

- What JRE you are using to run Eclipse?

5.0.6

Checked .log - nothing of interest (there's an exception thrown by the subclipse plugin, but that's it).

It seems to be related to Eclipse M5a acting incorrectly on the plugin.xml; the logic around visibility of org.eclipse.ui.popupMenus objectContributions doesn't seem to be working.  This seems to be an issue with the Spring plugin, too - it also only allows me to add Spring nature, I can't then remove it.  Don't know if this is an Eclipse M5a bug or just Eclipse M5a changing its application of plugin rules?  I can't fnd a relevant bug in Eclipse's bugzilla, but then I seldom can...

> 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


[jira] Commented: (MNGECLIPSE-87) Enabling Maven on a project does not change the context sensitive menu

Posted by "Robert Elliot (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNGECLIPSE-87?page=comments#action_61411 ] 

Robert Elliot commented on MNGECLIPSE-87:
-----------------------------------------

Eclipse bug here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=132419

> 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


[jira] Closed: (MNGECLIPSE-87) Enabling Maven on a project does not change the context sensitive menu

Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNGECLIPSE-87?page=all ]
     
Eugene Kuleshov closed MNGECLIPSE-87:
-------------------------------------

    Resolution: Won't Fix

Not a plugin issue. 

WTP released new version which fixed JST issue and alligned to Eclipse 3.2M6. It is available from the Callisto update site at http://download.eclipse.org/callisto/releases

> 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