
|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
None
|
|
Image Attachments:
|
|
|
| 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.
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:
|
|
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).