ResourceBundles should be commented out, but we missed that one.  I just 
commented it out and pushed the change.  Should be in the nightly build for the 
MXRoyale branch.

This kind of bug wouldn't matter if you use Ant or Maven.  Just use the one you 
prefer.

HTH,
-Alex

On 8/3/18, 2:00 AM, "chembali" <chemb...@hotmail.com> wrote:

    Tried js/bin/mxmlc. Getting the following error now.
    
    
C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src>C:\devenv\GitHub\royale-asjs/j
    s/bin/mxmlc
    -compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\
    src C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml
    Using Royale Compiler codebase: C:\devenv\GitHub\royale-asjs\js\bin\..\..
    Using Royale SDK: C:\devenv\GitHub\royale-asjs
    MXMLJSC
    
-sdk-js-lib=C:\devenv\GitHub\royale-asjs\frameworks\js\Royale\generated-sources
    -compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src
    C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml
    Error: Unable to resolve resource bundle 'rpc'
    
    
    4.925945806 seconds.
    
    Any ideas?
    
    
    
    --
    Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7Ce4ce53cb24ff46ca02c908d5f91f8608%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636688836157078382&amp;sdata=gwEW1x26lq8h%2Ff18BPS6IPShWj6QOYchM3zvaGDa7TU%3D&amp;reserved=0
    

Reply via email to