Just as a quick follow-up (in case anyone else is looking for the same) adding: <classifier>js</classifier> to all the swc dependencies in the pom meant I could compile the js-only project. <targets>JS</targets> alone was not enough.
However I am seeing some runtime errors with things like base.js:628 goog.require could not find: org.apache.flex.core.HTMLElementWrapper and similar. I'm currently trying to figure this out. On Tue, May 2, 2017 at 5:19 AM, Greg Dove <greg.d...@gmail.com> wrote: > Thanks Alex, > > This helps > <targets>JS</targets> > Still some stuff left to figure out, but that is progress. Pretty sure > that falls into "I am hoping there is something simple that I didn't see" - > thanks again. > > btw I think : > <outputJavaScript>true</outputJavaScript> > > is presumably redundant in any pom.xml now, including that example. My > reason for thinking that is that it is coming up 'red', with tooltip > "Element outputJavaScript is not allowed here", for a local project via > code highlighting in Intellij (which was really helpful initially to > understand this change). > > > > On Tue, May 2, 2017 at 4:42 AM, Alex Harui <aha...@adobe.com> wrote: > >> I believe examples/native/ButtonExample only produces JS output. >> >> -Alex >> >> On 5/1/17, 9:11 AM, "Greg Dove" <greg.d...@gmail.com> wrote: >> >> >Chris, or perhaps Alex: >> >With the latest changes for maven, I am trying to figure out how to get >> >the >> >same result with maven as >> ><outputJavascript>true</outputJavascript> >> > >> >which previously permitted js-only compilation so that COMPILE::JS was >> not >> >needed in js-only target project, and it was possible to use, for >> example, >> >var style:CSSStyleDeclaration, >> >window['Intl'] etc >> >outside of COMPILE::JS >> > >> >Is this still possible in some way after the change? I can see options >> for >> >maven like >> >skipAS etc, but have not figured out a combination that achieves the >> same. >> > >> >I am hoping there is something simple that I didn't see - I am still >> >getting my head around using maven, (apart from finding it mostly very >> >intuitive to 'read'). >> >If not, I can always go through the code and wrap things in COMPILE::JS, >> >was just hoping that I don't need to do that. >> >Thanks, >> >Greg >> > >> > >> >On Tue, May 2, 2017 at 2:51 AM, Christofer Dutz >> ><christofer.d...@c-ware.de> >> >wrote: >> > >> >> But in general, “mvn clean compile” should have worked. I even double >> >> checked with the debugger … if the other modules are part of the build >> >>it >> >> would acutally resolve the artifacts from the target directories >> >>instead of >> >> from the maven local repo … I’ll continue investigating this. >> >> >> >> Chris >> >> >> >> Am 30.04.17, 23:42 schrieb "Justin Mclean" <jus...@classsoftware.com>: >> >> >> >> Hi, >> >> >> >> > You are running “mvn clean compile” which compiles each module >> and >> >> created the swcs in the target directories. Unfortunately, they just >> >>stay >> >> there as they are not copied to your maven local repository. >> >> >> >> Thanks Chris that would explain the error. >> >> >> >> > To do that, you need to run “mvn clean install”. I would give >> >>that a >> >> try. >> >> >> >> Looks like typedef is now broken as I’m getting this: >> >> >> >> [INFO] --- exec-maven-plugin:1.5.0:exec (patch-js) @ >> >> flexjs-typedefs-js --- >> >> error: patch failed: js/target/downloads/svg.js:401 >> >> error: js/target/downloads/svg.js: patch does not apply >> >> [ERROR] Command execution failed. >> >> >> >> I’m assume the patch file no longer matches what’s at [1]? >> >> >> >> Thanks, >> >> Justin >> >> >> >> 1. >> >>https://na01.safelinks.protection.outlook.com/?url=https%3 >> A%2F%2Fstorage. >> >>googleapis.com%2Fgoogle-code-archive-&data=02%7C01%7C%7C6d >> 802edc936741aa1 >> >>c4e08d490acbcb6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0 >> %7C636292518959 >> >>818809&sdata=XnKepN4BFugfoG%2BrYp3Kpsc%2F8ZGRT64IpOKGuJ0%2 >> Fk%2Fo%3D&reser >> >>ved=0 >> >> downloads/v2/code.google.com/closureidl/svg.js >> >> >> >> >> >> >> >> >> >> >
