To complement what Alex said and for MAVEN+ANT build:
* I run Maven first then ANT
* ROYALE_COMPILER_HOME:
- ant wipe-all
- mvn clean install -DskipTests --quiet
* ROYALE_TYPEDEFS_HOME
- ant wipe
- mvn clean install --quiet
* ROYALE_ASJS_HOME:
- ant super-clean
- mvn clean install -P with-distribution,option-with-swf
-DdistributionTargetFolder="$SDK_FOLDER"
Notice as Alex said that you can have some files left from older builds, so
if something fails check RAT.txt to remove the files listed there
Notice 2: If js/lib/dom4j-LICENSE.txt continue to be a problem let us
know so we can add to excluded rat check, but I expect the other steps will
remove it and not cause you more problems
Let us know if all goes well.
Thanks
El mié., 11 mar. 2020 a las 2:44, Alex Harui (<[email protected]>) escribió:
> Just look in the files referenced in the output like
> /mnt/c/dev/royale-asjs/target/rat.txt
>
> It should tell you what file it didn’t like. Sometimes an interrupted
> Maven build will leave an unexpected file.
>
>
>
> HTH,
>
> -Alex
>
>
>
> *From: *Brian Raymes <[email protected]>
> *Reply-To: *"[email protected]" <[email protected]>
> *Date: *Tuesday, March 10, 2020 at 5:12 PM
> *To: *"[email protected]" <[email protected]>
> *Subject: *RE: VSCode + Royale SDK: Ant != Maven Distribution
>
>
>
> Ah, good to know. If that’s the case, then some git ignore must be hiding
> the differences that I wasn’t seeing.
>
>
>
> I’ll do more testing. Thank you.
>
>
>
>
>
> Brian
>
>
>
> *From:* Alex Harui <[email protected]>
> *Sent:* Tuesday, March 10, 2020 5:09 PM
> *To:* [email protected]
> *Subject:* Re: VSCode + Royale SDK: Ant != Maven Distribution
>
>
>
> It can be tricky to run both Maven after running Ant in a folder. Maven
> knows how to clean up its own stuff with the “clean” target but doesn’t
> know to clean up stuff from Ant and often that’s the reason for a RAT
> error. Running “ant super-clean” should remove all of the Ant stuff, but
> there might be bugs where it doesn’t clean something up, so check the
> rat.txt and add stuff to the appropriate clean or super-clean targets.
>
>
>
> I keep separate working copies for Ant and Maven.
>
>
>
> -Alex
>
>
>
> *From: *Brian Raymes <[email protected]>
> *Reply-To: *"[email protected]" <[email protected]>
> *Date: *Tuesday, March 10, 2020 at 4:51 PM
> *To: *"[email protected]" <[email protected]>
> *Subject: *RE: VSCode + Royale SDK: Ant != Maven Distribution
>
>
>
> Now, strangely, in both Windows CMD or WSL, I see the same RAT error when
> trying to build with maven.
>
>
>
> I have verified that my git clone is the latest and clean.
>
>
>
> *From:* Brian Raymes <[email protected]>
> *Sent:* Tuesday, March 10, 2020 4:25 PM
> *To:* [email protected]
> *Subject:* RE: VSCode + Royale SDK: Ant != Maven Distribution
>
>
>
> Currently building this on the Windows command line as it fails in WSL
> Debian (see below).
>
>
>
> *Windows:*
>
>
>
> Source location:
>
> c:\dev\royale-asjs
>
>
>
> Maven build (tried with and without the swf-option):
>
> mvn clean install -P with-examples,with-distribution,option-with-swf
> -DdistributionTargetFolder=c:\dev\royale-sdk
>
>
>
> When I point vs-code to c:\dev\royale-sdk for the SDK, all of the errors
> and issues I listed before, are seen.
>
>
>
> If I simply perform `ant all` in c:\dev\royale-asjs, and point vs-code to
> c:\dev\royale-asjs, all is well.
>
>
>
> This workaround is fine for me for now, but could be problematic for
> others.
>
>
>
> *WSL Debian:*
>
>
>
> I wish I could build it here as most of my dev work is done within WSL,
> but, unfortunately, it fails every time with this license issue:
>
>
>
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.13:check
> (license-check) on project royale-framework-parent: Too many files with
> unapproved license: 1 See RAT report in:
> /mnt/c/dev/royale-asjs/target/rat.txt -> [Help 1]
>
>
>
> The license in question is:
>
>
>
> !????? js/lib/dom4j-LICENSE.txt
>
>
>
> -----------------------
>
>
>
> I can start creating issues for anything that I find on the github project
> if preferred.
>
>
>
> Brian
>
>
>
> *From:* Carlos Rovira <[email protected]>
> *Sent:* Tuesday, March 10, 2020 3:46 PM
> *To:* [email protected]
> *Subject:* Re: VSCode + Royale SDK: Ant != Maven Distribution
>
>
>
> Hi Brian,
>
>
>
> Maven should give you code completion without problem.
>
>
>
> The only issue right now with Maven SDK is if you want to build using SDK
> in an IDE (in VSCode CMD+SHIFT+ENTER), instead to build with normal maven
> command (mvn install) using a pom.xml (as normal).
>
> Building with IDE was working some weeks ago for VSCode, but Moonshine
> reported it was not working and I couldn't get back to fix that issue. But
> as I said, I think is not critical and should not be a problem in your case.
>
>
>
> * Are you generating the SDK with Maven with: -P with-distribution ?
>
> * Where are you generating the SDK? by default is in
> royale-asjs/distribution/target, but you can generate in other folder
> using -DdistributionTargetFolder=/path-to-folder
>
>
>
> think that ANT creates SDK in royale-asjs folder directly, while maven is
> not doing that, so you can have ROYALE_HOME pointing to royale-asjs, for
> ANT but you should point to some external SDKs folder to the generated SDK
> current folder
>
>
>
>
>
>
>
>
>
> El mar., 10 mar. 2020 a las 20:28, Brian Raymes (<[email protected]>)
> escribió:
>
> Hi all,
>
>
>
> While testing Royale for a migration project, I started with building the
> latest SDK (update daily) with Ant. Linking the SDK to VSCode was all fine
> and well until I reported an issue was it was suggested I move to Maven.
>
>
>
> I now have a Maven project using the latest remote 0.9.7-SNAPSHOTs, but I
> still need a local SDK for code-completion, etc.
>
>
>
> The SDK produced with Ant was great. Code completion and error
> highlighting all work as expected.
>
>
>
> After switching to Maven, and building and linking the Distribution SDK,
> my code is now riddled with “errors” that are not really errors and
> code-completion only partially works.
>
>
>
> Here are a few issues I see with the *Maven* built SDK:
>
>
>
> 1. *dispatchEvent(…any event…)* is seen as an error because the
> *Event* is not an Object.
>
>
>
> · Implicit coercion of a value of type
> org.apache.royale.events.Event to an unrelated type Object.(1067)
>
>
>
> 2. *addEventListener()* / removeEventListener() are seen as errors
> in many cases.
>
>
>
> · Attempted access of inaccessible method addEventListener
> through a reference with static type Timer.
>
>
>
> 3. Code-completion doesn’t work for Jewel components, but does for
> properties.
>
>
>
> · <j:Bu will not suggest or auto-complete to <j:Button>
>
> · <j:Button la will auto complete label=””
>
>
>
> Once I switch back to the Ant built SDK, all of these kinds errors go away
> and code-completion is working as expected.
>
>
>
> Thoughts?
>
>
>
> Brian
>
>
>
>
> --
>
> Carlos Rovira
>
> http://about.me/carlosrovira
> <https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C677c019e063743ccd86d08d7c550ed3f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637194823687714663&sdata=TocJufy5ETIbem%2FQI3f6T6ZRG3cb7Pp2WoJxNNZv2KI%3D&reserved=0>
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
