You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sander Verhagen (JIRA)" <ji...@codehaus.org> on 2008/08/22 21:26:26 UTC
[jira] Created: (MECLIPSE-484) Not finding main(...) through
workspace resolution
Not finding main(...) through workspace resolution
--------------------------------------------------
Key: MECLIPSE-484
URL: http://jira.codehaus.org/browse/MECLIPSE-484
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Environment: Eclipse Platform 3.3.1.1, Maven Integration for Eclipse 0.9.5.20080717-1821
Reporter: Sander Verhagen
Attachments: testgroup.zip
As discussed in http://www.nabble.com/Not-finding-main(...)-through-workspace-resolution-to19103273.html
On a certain project Eclipse is not finding the main(...) that is located in one of its dependencies when it needs to be resolved through workspace resolution.
Steps to reproduce:
Given a project1 with an executable main class and a project2 that depends on project1. See the attachment.
- Load project1 in Eclipse
- Load project2 in Eclipse
- Make sure that project2 is set to workspace resolution
- Right-click project2 in the Package Explorer
- Choose "Run As"
- Choose "Java Application"
- Observe the following outcome: "Launch Error" "Selection does not contain a main type"
Verification:
- Set project2 to disabled workspace resolution
- Right-click project2 in the Package Explorer
- Choose "Run As"
- Choose "Java Application"
- Observe the following outcome: "This is my main" in the Console view
--
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