History | Log In     View a printable version of the current page.  
Issue Details (XML)

Key: FB-9154
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Assignee: Soenke Rohde
Reporter: Soenke Rohde
Votes: 2
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Flash Builder / Flex Builder

Unable to avoid absolut paths in .actionScriptProperties .flexProperties with FDS

Created: 08/30/07 11:28 AM   Updated: 03/12/08 09:13 AM
Component/s: Flex Project Natures
Security Level: Public (All JIRA Users )

File Attachments: None
Image Attachments:

1. eclipse-linked-resources.png
(78 kb)

Severity: Data Loss/Corruption
Reproducibility: Every Time
Discoverability: High
Found in Version: Moxie M2 (Beta 1)
Milestone: Moxie M3 (zero)
Affected OS(s): All OS Platforms
Steps to Reproduce:
With FDS the .flexProperties contain the serverRoot and the .actionScriptProperties -services and outputFolderLocation which are absolute paths.
This does not allow a team to share this files in a version control system.

Eclipse has a feature called Linked Resources (see screenshot) where a user can define variables for e.g. the path to Tomcat and to a root directory which contains all Flex project directories (I use Modules and multiple Flex projects for one project).
This variables should also be used within the property files which would allow to use only relative paths.

For the Flex Compiler the Additional compiler arguments then should not be
-services "D:\tools\apache-tomcat-5.5.20\webapps\myprojectWEB-INF\flex\services-config.xml" -locale en_US
but
-services "${CATALINA_HOME}\webapps\myprojectWEB-INF\flex\services-config.xml" -locale en_US

Same for Project Properties->Flex Server->Root folder

Steps to reproduce:
1. Create an FDS project
2. Try to share code via version control system
 
 Actual Results:
 Not possible due to absolute path
 
 Expected Results:
Should work with relative paths and Linked Resources
 
 
 Workaround (if any):
 -
 
 Flex Builder already uses Linked resources for Project Properties->Flex Build Path->Output folder.
I could browse the directory and it was replaced with ${CATALINA_HOME}\webapps\myproject\flex
So I consider it a bug that Linked Resources are not used for all kind of path definitions.
Language Found: English
Bugbase Id: none
Triaged: Yes
Regression: No
QA Owner: Gelu Blanariu
Resolved by: Mihai Pricope (Miti)
Participants: Gelu Blanariu, Larry McLister, Mihai Corlan, Mihai Pricope (Miti), Soenke Rohde and Tanya Dimalsky
Eclipse Configuration: Eclipse 3.2


 All   Comments      Sort Order:
Mihai Corlan - [08/31/07 02:29 AM ]
The linked resources framework from eclipse is working only if the Variable is at the begining of the string. For Compiler Additiona arguments we have the path for services-config.xml in the middle of the string and at the start. Thus for supporting the linked resources here we need to custom handle the whole string (eg. we could extract the value for -services and use Eclipse linked respources framework to replace any variable).

We are supporting linked resources for all the path stored in .actionScriptProperties and .flexProperties: output folder location, server root, library paths and source paths. The only restriction is to use the linked resources at the begining of the string (this is how the Eclipse API is working).


Tanya Dimalsky - [08/31/07 11:42 AM ]
IRB: opened to Mihai

Mihai Pricope (Miti) - [09/04/07 03:33 AM ]
(in 181385) I've added the linked resource path variables as compiler tokens. This should do some tricks. We also have for projects compiled with Moxie SDK a PathResolver injected in the SDK so it will solve more linked resource cases, but it will not work for pre-Moxie SDKs.


Larry McLister - [09/18/07 11:55 AM ]
Opened to Miti

Larry McLister - [09/18/07 11:56 AM ]
looks like the priority is off. set to b for A+

Mihai Pricope (Miti) - [10/03/07 01:54 AM ]
in 183941
- solved for rootFolder and outputFolder.