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

Key: SDK-13569
Type: Bug Bug
Status: Closed Closed
Resolution: Deferred
Priority: C C
Assignee: Kristen Sindac
Reporter: Kristen Sindac
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Flex SDK

Deprecation warnings still reported even when -show-deprecation-warnings=false

Created: 11/15/07 07:13 PM   Updated: 01/17/08 10:55 PM
Component/s: MXML Compiler - Error Reporting
Security Level: Public (All JIRA Users )

File Attachments: 1. File Deprecation.mxml (0.6 kb)


Severity: Incorrectly Functioning with Workaround
Reproducibility: Every Time
Discoverability: Medium
Affected OS(s): Windows - XP
Steps to Reproduce:
Found in SDK build 187476

Steps to reproduce:
1. Get attached bugfile and compile with the following command call:
> mxmlc Deprecation.mxml

Notice that there are 4 deprecation warnings reported. (Note: the duplicate warning is being tracked on a different bug number)

2. Now, compile with -show-deprecation-warnings=false
>mxmlc -show-deprecation-warnings=false Deprecation.mxml


 Actual Results:
 3 Deprecation warnings are still reported

Deprecation.mxml(12): Warning: 'getString' has been deprecated since 3.0. Please use 'ResourceManager.getString()'.

                        trace(rb.getString("foo"));

Deprecation.mxml(14): Warning: 'testDeprecated' has been deprecated since 3.0.0. Please use 'testReplacement'.

                        testDeprecated();

Deprecation.mxml(28): Warning: Property protocol is deprecated. Please use an appropriate channel from your services configuration file (DefaultHTTP or DefaultHTTPS for instance); when useProxy is false set your URL to use the right protocol

        <mx:WebService protocol="foo"/>
 
 Expected Results:
 No warnings reported.
 
 Workaround (if any):
 Compile using -warnings=false to remove all warning reporting altogether
>mxmlc -warnings=false Deprecation.mxml

 
 
Language Found: English
Bugbase Id: none
Triaged: Yes
Regression: No
QA Owner: Gaurav Jain
Resolved by: Lauren Park
Participants: Jono, Kristen Sindac and Lauren Park


 All   Comments      Sort Order:
Kristen Sindac - [11/15/07 07:20 PM - edited ]
This may not be a regression since deprecation warnings are not properly reported before. This is an effect of ASC now reporting deprecation warnings but mxmlc -show-deprecation-warnings option does not know about these warnings and does not suppress them.

Jono - [11/15/07 08:35 PM ]
Unavoidable unless we want to integrate a new ASC -- ASC is not aware of these settings, and I'm not aware of a way to pass configuration options to ASC (gut says to use ContextStatics or something...). -warnings=false may provide insight on this, though odds are that it just ignores ALL warnings from ASC rather than telling ASC to not emit them.

We could rename this to -show-deprecation-warnings to -show-mxml-deprecation-warnings -- this flag will definitely disable warnings that come from MXML components; AS is unavoidable.

Lauren Park - [11/18/07 10:41 PM ]
Deferred for Moxie

Jono - [11/19/07 01:09 PM - edited ]
* Making the option advanced and hidden (similar to compiler.show-dependency-warnings), in the meantime.
* Removing it from flex-config.xml and air-config.xml, since that is high-exposure.
* Ant tasks still support it.
* OEM API still supports it because there is no nice way to hide it, and deprecating it would be wrong (hah).

188245 should get reverted when the bug is revisited, and docs for this feature should be re-added or re-worded to announce its triumphant return!

Kristen Sindac - [11/22/07 04:49 PM ]
confirmed that -show-deprecation-warnings is hidden in command line help list and config file