On Tue, May 2, 2017 at 10:09 AM, Alex Harui <aha...@adobe.com> wrote:
> "Non-us" may be a typo. I think it happens everywhere. > > If you can upgrade to latest Java 8, the problem should go away. > Otherwise see: > > http://www.oracle.com/technetwork/java/javase/ > downloads/jce8-download-21331 > 66.html > > > There is a similar link for Java 7. > I am pretty sure I have the latest version of Java. *java version "1.8.0_131"* *Java(TM) SE Runtime Environment (build 1.8.0_131-b11)* *Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)* > AIUI, consumers of the binaries don't hit this issue, only those building > from source. > Yes, the binaries are never a problem. I am talking about compiling from source. My point is that - if the user cannot cleanly compile from the sources, we should not be shipping with that module. Thanks, Om > > -Alex > > On 5/2/17, 9:58 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" > <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: > > >On May 2, 2017 9:43 AM, "Christofer Dutz" <christofer.d...@c-ware.de> > >wrote: > > > >Hi Om, > > > >This is due to the annoying sourceforge ssl update that prevents > >downloading files from sourceforge with non-us JVMs. You have to manually > >update the encryption module of your JVM to download those files. I just > >lived with commenting out the fonts module from my build as it was only > >one > >example that actually needed that and we can download that from the Apache > >SNAPSHOTS repo. > > > > > >Chris, thanks for the response. > > > >What is non-us JVM? > > > >If this is not essential, perhaps we can ship with these modules disabled? > >And add instructions for those who want to enable it? > > > >Thanks, > >Om > > > > > >Chris > > > > > >Am 01.05.17, 21:18 schrieb "omup...@gmail.com im Auftrag von OmPrakash > >Muppirala" <omup...@gmail.com im Auftrag von bigosma...@gmail.com>: > > > > flex-falcon and flex-typedefs built fine for me. > > > > The flex-asjs build is broken for me on the Fonts project. > > > > Here is the relevant log: > > > > > >https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fpaste.apa > >che.org%2FkATQ&data=02%7C01%7C%7C3f941efbc62043ed91e208d4917c > 8a78%7Cfa7b1b > >5a7b34438794aed2c178decee1%7C0%7C0%7C636293411471086252& > sdata=QTsZvivy0jT1 > >FdWjAkXpKLskL%2BfzKNL5UYsg%2FwEnhb0%3D&reserved=0 > > > > Can someone please take a look? > > > > Thanks, > > Om > > > > On Mon, May 1, 2017 at 11:50 AM, OmPrakash Muppirala < > >bigosma...@gmail.com> > > wrote: > > > > > For folks who want to help out but are not sure how to, please > >follow > >the > > > step by step instructions here on how to build the FlexJS SDK from > >the > > > sources: > > > > > > > >https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fcwiki.apa > >che.org%2Fconfluence%2Fdisplay%2FFLEX%2F&data=02% > 7C01%7C%7C3f941efbc62043e > >d91e208d4917c8a78%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C63629341147 > >1086252&sdata=x9xIhSCxIwEx%2FU4qSU2E0gLTIElb3nS0y% > 2BJfdAtuTBM%3D&reserved= > >0 > > > Building+FlexJS+with+Maven > > > > > > Thanks, > > > Om > > > > > > On Mon, May 1, 2017 at 10: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% > > >> 3A%2F%2Fstorage > > >> > . > > >> > >>googleapis.com%2Fgoogle-code-archive-&data=02%7C01%7C% > > >> > 7C6d802edc936741aa1 > > >> > >>c4e08d490acbcb6%7Cfa7b1b5a7b34438794aed2c178de > > >> > cee1%7C0%7C0%7C636292518959 > > >> > >>818809&sdata=XnKepN4BFugfoG%2BrYp3Kpsc%2F8ZGRT64IpOKGuJ0% > > >> > 2Fk%2Fo%3D&reser > > >> > >>ved=0 > > >> > >> downloads/v2/code.google.com/closureidl/svg.js > > >> > >> > > >> > >> > > >> > >> > > >> > >> > > >> > > > >> > > > >> > > > > > > > >
