> I hope with npm I can still use frameworks like crux with royale ? Yes, projects created with the CLI still ultimately compile with a normal Royale SDK, so you should be able to use libraries like Crux.
-- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Thu, May 27, 2021 at 4:36 AM romanisi...@yahoo.com.INVALID <romanisi...@yahoo.com.invalid> wrote: > Hi, > I just want to provide an update on this. I was still unable to use the > maven archetype. I stumbled on the alternative option stated in the site > i.e "Royale CLI". I discovered that I needed to install node js so as to > have npm installed. Once this was done I followed the instructions in the > site. I was able to create a new royale project successfully. > For now since, I am learning royale I intend to stick with npm pending the > time the maven archetype is updated. > I hope with npm I can still use frameworks like crux with royale ? > Thanks for the feedback. > Regards, > On Tuesday, May 25, 2021, 10:52:54 AM GMT+1, > romanisi...@yahoo.com.INVALID <romanisi...@yahoo.com.invalid> wrote: > > Hi, > I am new to Royale. I attempted creating a new Royale project using maven > with the following archetype > mvn archetype:generate -DarchetypeGroupId=org.apache.royale.framework > -DarchetypeArtifactId=royale-simple-application-archetype > -DarchetypeVersion=0.9.8-SNAPSHOT > It does not work. I get the following errors > [INFO] Generating project in Interactive mode[INFO] Archetype repository > not defined. Using the one from > [org.apache.royale.framework:royale-simple-application-archetype:0.9.7] > found in catalog remote[WARNING] The POM for > org.apache.royale.framework:royale-simple-application-archetype:jar:0.9.8-SNAPSHOT > is missing, no dependency information available > > It appears the archetype is no longer valid. > For now I am using visual studio code with the royal sdk configured. I > will prefer using maven. > > > > > >
