Hi Carlos,

Definitely NOT urgent.

Yes, doing CTRL+Shift+B for the AS compile (Release and Debug produce these 
errors, Clean never seems to finish), but reading the README said I needed a 
clean Maven build so tried that as well with the Maven Visual Code plug-in, 
with the error noted in my prior email.

Of note, I get the same result against the current 0.9.7 stable build. For 
both, I downloaded the JS only version.

Jason

From: Carlos Rovira <[email protected]>
Sent: Sunday, February 21, 2021 3:20 PM
To: [email protected]
Subject: Re: MXRoyaleJS.swc could not be found

Hi Jason,

if I load in VSCode + AS3&MXML the folder 
"/examples/mxroyale/RemoteObjectAMFTest" and build with CMD+SHIFT+B, then 
select "Debug with ActionScript extension (this is what I guess you are doing) 
I can reproduce the problem with a nightly.

 Also today I was fixing Maven SDK distribution so I'll wait for the next 
nightly build to check what's going on. I tried building with Maven and seems 
to work, also building with a fixed Maven distribution SDK seems to pass but I 
see some warning that I need to investigate further. For now if you are in a 
hurry can only say that your only path right now is to build with Maven instead 
with IDE. If you choose that path you can use this gist [1] to build from 
scratch all repos with Maven and then with ANT (you can just use one of them, I 
build both to ensure all is ok as an SDK developer).

[1] 
https://gist.github.com/carlosrovira/200753108de263fa43e80d3228213509<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Fcarlosrovira%2F200753108de263fa43e80d3228213509&data=04%7C01%7C%7C0047beb2cb4b4cff18e508d8d6bf423d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637495464223534895%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=HS2k5pL5jRmmP6YEHXsnIAc7ALC7QR4txZoliH8YufI%3D&reserved=0>


El lun, 22 feb 2021 a las 0:00, Jason Fillman 
(<[email protected]<mailto:[email protected]>>) escribió:
Hi Carlos,

I found the more recent builds. FYI, the link to the nightly Royale build here: 
https://royale.apache.org/get-involved/<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fget-involved%2F&data=04%7C01%7C%7C0047beb2cb4b4cff18e508d8d6bf423d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637495464223544850%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=NWA5Ri0uD%2BdjebLAksCA8t3ZOL49mE0mt9erSk3Gbb8%3D&reserved=0>
  resolves to build #2276 vs the most recent list.

I did search both lists and the only threads I found that seemed to address 
this issue indicated to add the below code to the asconfig.json file, however, 
this exact code is already in the file, so seems to be something else/something 
I am doing wrong...

"library-path": [
    "${royalelib}/js/libs/MXRoyaleJS.swc"
],
"js-library-path": [
    "${royalelib}/js/libs/MXRoyaleJS.swc"
]

Still unclear to me is if I am compiling using the AS compiler or Maven, within 
VS, however, neither seem to work. Using AS, I get these SWC not found errors. 
Using a clean Maven build, I get the following:

PS C:\...\royale-asjs\examples\mxroyale\RemoteObjectAMFTest> & 
"c:\...\royale-asjs\mvnw.cmd" clean -f 
"c:\...\royale-asjs\examples\mxroyale\RemoteObjectAMFTest\pom.xml"
Files was unexpected at this time.

I get the same type of result with the SAMPLEAMFWEBAPP project using Maven 
clean build (see included image), so wondering if I need to install Maven 
outside of VS instead of the VS plug-in or maybe some other environment setup 
issues I am missing.

[cid:[email protected]]

From: Carlos Rovira <[email protected]<mailto:[email protected]>>
Sent: Sunday, February 21, 2021 5:46 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: MXRoyaleJS.swc could not be found

Hi Jason,

since this question was solved more than one time in user and dev lists, please 
search for it on how to solve it.
Mainly MXRoyale is not included in royale config by default but is in flex 
config, so you need to add it specifically to it.
Also if you're using a nightly please use the newer one and keep up to date if 
possible.



El sáb, 20 feb 2021 a las 20:30, Jason Fillman 
(<[email protected]<mailto:[email protected]>>) escribió:
Compiling RemoteObjectAMFTest against 097 and the Jan 1 098 nightly, I get a 
bunch of errors: ...\MXRoyaleJS.swc could not be found

One example output:
c:\...\royale-asjs\frameworks\js\libs\MXRoyaleJS.swc Warning: The definition 
org.apache.royale.events.Event depended on by mx.core.ScrollControlBase in the 
SWC c:\...\royale-asjs\frameworks\js\libs\MXRoyaleJS.swc could not be found

The terminal process "C:\Program Files (x86)\Common 
Files\Oracle\Java\javapath\java.exe '-jar', 
'c:\Users\jmfil\.vscode\extensions\bowlerhatllc.vscode-nextgenas-1.6.0\bin\asconfigc.jar',
 '--sdk', 'c:\...\royale-asjs', '--debug=false', '--project', 
'c:\...\royale-asjs\examples\mxroyale\RemoteObjectAMFTest\asconfig.json'" 
terminated with exit code: 3.

I checked the file path referenced and the swc file is there, so not sure...

Visual Studio Code; JDK 8u281


--
Carlos Rovira
Apache Member & Apache Royale PMC
Apache Software Foundation
http://about.me/carlosrovira<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=04%7C01%7C%7C0047beb2cb4b4cff18e508d8d6bf423d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637495464223544850%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mWfxW1Pet1nQ8e6nTE1Oi7xtwMbJR7tB2ArzQ7uz8wU%3D&reserved=0>



--
Carlos Rovira
Apache Member & Apache Royale PMC
Apache Software Foundation
http://about.me/carlosrovira<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=04%7C01%7C%7C0047beb2cb4b4cff18e508d8d6bf423d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637495464223554806%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=JtQ5I5i5wv%2F0wR3eUoJsmKaP%2F%2BTrphzqKAd5J8LFomk%3D&reserved=0>

Reply via email to