[FLEX-12650] Namespace manifest tag in flex-config.xml no longer supports relative paths when invoked from MXMLC

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: Adobe Flex SDK Previous
• Component/s: MXML Compiler, MXML Compiler - Properties
• Environment: Affected OS(s): Windows; Affected OS(s): Windows XP; Language Found: English
• Assignee: Adobe JIRA
• Reporter: Adobe JIRA
• Created: 02/Oct/07 11:46
• Updated: 29/Apr/11 10:23
• Resolved: 17/Oct/07 02:03

Description

This became evident as we tested upgrading from beta 1 to beta 2. In our flex-config.xml file we have the following:

<namespaces>
<!-- Specify a URI to associate with a manifest of components for use as MXML -->
<!-- elements. -->
<namespace>
<uri>http://www.adobe.com/2006/mxml</uri>
<manifest>mxml-manifest.xml</manifest>
</namespace>
<namespace>
<uri>http://www.decisionviewsoftware.com/2007/view</uri>
<manifest>../../core/conf/component-manifest.xml</manifest>
</namespace>
</namespaces>

Steps to reproduce:

Enter a component manifest in flex-config.xml with a relative path..

Actual Results:
Compiler errors out because it says it can't find the file.

Expected Results:
Behavior would remain unchanged from Flex 2 and Flex 3 Beta 1, when this behavior worked.

Workaround (if any):
1. Place the manifest file in the frameworks folder, alongside the mxml-manfiest.xml file
or
2. Use a hard path in the manfiest tag (I had to even include "C:/"--just starting with "/" still caused the error)