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)
>
>
>
>    1. *addEventListener()* / removeEventListener() are seen as errors in
>    many cases.
>
>
>
>    - Attempted access of inaccessible method addEventListener through a
>    reference with static type Timer.
>
>
>
>    1. 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

Reply via email to