No. We’re running the compiler-jx project with the following arguments:
+royalelib="C:\dev\flexjs\royale-asjs\frameworks"
+configname=royale
-debug
-closure-lib=C:\dev\goog\closure-library
--js-library-path+=C:\Users\Yishay\Documents\printui-flexjs\PortedPrintUI\lib
--js-external-library-path+=C:\Users\Yishay\Documents\printui-flexjs\PortedPrintUI\typedefs
--remove-circulars=true
--html-template=src\resources\mdl-js-index-template.html
--js-compiler-option+=--skip_type_inference
--targets=JSRoyale
C:\Users\Yishay\Documents\printui-flexjs\PortedPrintUI\src\PortedPrintUI.mxml
________________________________
From: Piotr Zarzycki <piotrzarzyck...@gmail.com>
Sent: Sunday, October 14, 2018 12:41:41 PM
To: dev@royale.apache.org
Subject: Re: Royale Compiler Brings Wrong Dependencies
Hi Yishay,
Do you load during the build -theme?
Piotr
On Sun, Oct 14, 2018, 9:45 AM Yishay Weiss <yishayj...@hotmail.com> wrote:
> Hi,
>
> We’re seeing a bug where beads from MXRoyale are loaded even though the
> project doesn’t reference MXRoyale. This results in a runtime error when
> opening a ComboBox.
>
> Specifically, it looks like these lines
>
> Basic|ComboBoxList
> {
> IDataProviderItemRendererMapper:
> ClassReference("mx.controls.listClasses.DataItemRendererFactoryForICollectionViewData");
> IBeadModel:
> ClassReference("mx.controls.beads.models.SingleSelectionICollectionViewModel");
> }
>
> Are bring read from MXRoyale’s defaults.css, changing the default model
> for ComboBoxList. I haven’t been able to reproduce this in a simple [1]
> example.
>
> I spent some time in the compiler trying to figure out what was going on
> but no luck so far. What I have noticed is that in
> RoyaleJSTarget.findAllCompilationUnitsToLink() the list of found
> dependencies includes compilation units I wouldn’t expect to find. For
> example, in the simple test [1] I created one of the dependencies has the
> AceJS compilation unit.
>
> Any pointers?
>
> [1] https://paste.apache.org/N5As
>
>
