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

Bug 437961

Summary: Allow additional quotations around string literals in deployment manifest
Product: [ECD] Orion Reporter: Maciej Bendkowski <maciej.bendkowski>
Component: DeploymentAssignee: Project Inbox <orion.server-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: 6.0 RC3   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Maciej Bendkowski CLA 2014-06-23 12:34:46 EDT 
Cloud Foundry accepts quotation marks as valid characters in many (if not all) deployment parameters, thus distinguishing between "<string literal>" and <string literal>. Since many developers are used to the fact that such string literals are equivalent, we could facilitate the error recovery in case of failing deployments using parameters with quotation marks. If we detect such a scenario, we may suggest to the user that the reason for the deployment to fail is the misleading use of quotation marks around string literals.
Comment 1 Maciej Bendkowski CLA 2014-06-24 05:39:57 EDT 
Having investigated the official Cloud Foundry CLI, I discovered that the quotation strategy has changed from the previous Ruby implementation. The new CLI, does not distinguish between quoted string literals and their unquoted alternatives. Since the previous CLI implementation is considered deprecated, we ought to adjust our quoting strategy and assume the new one, instead of supporting both contradicting strategies.