Cyrill Zadra created FLEX-33241:
-----------------------------------

             Summary: Error: Unexpected exception 
'java.lang.IllegalArgumentException' when the same @namespace definition occurs 
twice in <fx:Style/>
                 Key: FLEX-33241
                 URL: https://issues.apache.org/jira/browse/FLEX-33241
             Project: Apache Flex
          Issue Type: Bug
          Components: MXML Compiler
            Reporter: Cyrill Zadra
             Fix For: Apache Flex Next


When the  @namespace "library://ns.adobe.com/flex/mx"; is set twice then 
following exception occurs.

C:\dev\apache-flex\falcon\compiler.tests\functional-tests\f\mxml\DuplicateCSSNamseSpace.mxml
Error: Internal error in ABC generator subsystem, when generating code for: 
C:\dev\apache-flex\falcon\compiler.tests\functional-tests\f\mxml\DuplicateCSSNamseSpace.mxml:
 java.lang.IllegalArgumentException: duplicate key: 
        at 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
        at 
com.google.common.collect.RegularImmutableMap.<init>(RegularImmutableMap.java:72)
        at 
com.google.common.collect.ImmutableMap$Builder.fromEntryList(ImmutableMap.java:221)
        at 
com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:207)
        at com.google.common.collect.Maps.uniqueIndex(Maps.java:492)
        at 
org.apache.flex.compiler.internal.css.CSSDocument.<init>(CSSDocument.java:140)
        at 
org.apache.flex.compiler.internal.css.CSSTree.stylesheet(CSSTree.java:245)
        at 
org.apache.flex.compiler.internal.css.CSSDocument.parse(CSSDocument.java:81)
        at 
org.apache.flex.compiler.internal.tree.mxml.MXMLStyleNode.getCSSDocument(MXMLStyleNode.java:88)
        at 
org.apache.flex.compiler.internal.as.codegen.MXMLClassDirectiveProcessor.processMXMLStyle(MXMLClassDirectiveProcessor.java:3171)
        at 
org.apache.flex.compiler.internal.as.codegen.MXMLClassDirectiveProcessor.processNode(MXMLClassDirectiveProcessor.java:771)
        at 
org.apache.flex.compiler.internal.as.codegen.MXMLClassDirectiveProcessor.traverse(MXMLClassDirectiveProcessor.java:649)
        at 
org.apache.flex.compiler.internal.as.codegen.MXMLClassDirectiveProcessor.traverse(MXMLClassDirectiveProcessor.java:619)
        at 
org.apache.flex.compiler.internal.as.codegen.MXMLClassDirectiveProcessor.processMainClassDefinitionNode(MXMLClassDirectiveProcessor.java:515)
        at 
org.apache.flex.compiler.internal.as.codegen.GlobalDirectiveProcessor.declareMXMLDocument(GlobalDirectiveProcessor.java:510)
        at 
org.apache.flex.compiler.internal.as.codegen.DirectiveProcessor.processNode(DirectiveProcessor.java:232)
        at 
org.apache.flex.compiler.internal.as.codegen.DirectiveProcessor.traverse(DirectiveProcessor.java:188)
        at 
org.apache.flex.compiler.internal.as.codegen.ABCGenerator.generate(ABCGenerator.java:122)
        at 
org.apache.flex.compiler.internal.units.MXMLCompilationUnit.handleABCBytesRequest(MXMLCompilationUnit.java:198)
        at 
org.apache.flex.compiler.internal.units.CompilationUnitBase.processABCBytesRequest(CompilationUnitBase.java:866)
        at 
org.apache.flex.compiler.internal.units.CompilationUnitBase.access$3(CompilationUnitBase.java:864)
        at 
org.apache.flex.compiler.internal.units.CompilationUnitBase$3$1.call(CompilationUnitBase.java:309)
        at 
org.apache.flex.compiler.internal.units.CompilationUnitBase$3$1.call(CompilationUnitBase.java:1)
        at 
org.apache.flex.compiler.internal.units.requests.RequestMaker$1.call(RequestMaker.java:228)
        at 
org.apache.flex.compiler.internal.units.requests.RequestMaker$1.call(RequestMaker.java:1)
        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to