Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315611 - Run As/Debug As "Google Web Application" launch wrong project
Summary: Run As/Debug As "Google Web Application" launch wrong project
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.5.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-03 11:11 EDT by Hong Chen CLA
Modified: 2010-06-03 11:47 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hong Chen CLA 2010-06-03 11:11:33 EDT 
Build Identifier: Build id: 20100218-1602  

I have a few Google GWT projects in Eclipse and debug and test them using google development server. At some point, the "Run as" command always launch cause the google development server to start a particular project. For example, I right click on "project b" and select "run as web application", it will still start "project a". This behavior only happens to google web application. If I right click other projects, they will still start correctly. 

Reproducible: Sometimes

Steps to Reproduce:

1. Create on google gwt project. run it or debug it
2. create another google gwt proejct. run it or debug it.
3. switch back to first project and run it or debug it. Second project would be run.
Comment 1 Darin Wright CLA 2010-06-03 11:20:38 EDT 
I think this bug should be filed against the tooling that provides the google action (launch shortcut). It may be providing the debug platform with incorrect information (resource associated with the selection, or configuration associated with the selection).
Comment 2 Darin Wright CLA 2010-06-03 11:33:12 EDT 
Marking as "not Eclipse". Suggest to file against with Google.
Comment 3 Hong Chen CLA 2010-06-03 11:47:29 EDT 
Found a work around. Just change the port number