Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 427879

Summary: Launch configurations don't render in Deploy As
Product: [ECD] Orion Reporter: Malgorzata Janczarska <malgorzata.tomczyk>
Component: ClientAssignee: Malgorzata Janczarska <malgorzata.tomczyk>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: Silenio_Quarti
Version: 5.0   
Target Milestone: 5.0 RC2   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Malgorzata Janczarska CLA 2014-02-11 05:40:17 EST 
1. Open project with saved launch configurations -> they are launched
2. Open workspace root
3. Open project again -> no launch configurations in Deploy As

Also the Deploy action not always work, because the item passed to actions is not enhanced with the project data.
Comment 1 Malgorzata Janczarska CLA 2014-02-11 05:48:43 EST 
I'm not sure if this was done on purpuse, but deploy actions where changed to be render based on the file/folder opened on the right against to the project root. The problem is that the opened file metadata do not contain information about project that are added in project model.
Comment 2 Silenio Quarti CLA 2014-02-11 10:21:20 EST 
The extra actions scope was changed to render with the opened file metadata because the Fork action was added to that scope and the Fork action needs the open file metadata.    If we are going to render with the treeRoot, we need to update the visibleWhen of the Fork action.  Or the Fork action needs another scope.

I am not sure what is the best option here.  Lately, we have been moving around the commands quite a bit.   Every time we move a command from an scope to another, we risk breaking it because its visibleWhen/callback requires a specific item.

Right now, the file,edit,view actions are rendered with the nav selection.   The tools actions are rendered with the opened file metadata.   The extra actions is now rendered with the treeRoot.

It would be good if we could code the visibleWhen/callback of the commands to accept any item.
Comment 3 Malgorzata Janczarska CLA 2014-02-11 12:03:02 EST 
The Fork action was updated to the treeRoot. Unfortunately the deploy actions could not work with file metadata only without doing some extra data fetching.