Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
Hi, I'm trying a simple Hello World in IntelliJ I did at the time of the 0.6 release (with the Josh tutorial in NExtGestAS3), now with 0.7 nigthly (through Flex SdK installer), and getting the same error as Justin: Error:[HelloIDEA]: java.lang.NoClassDefFoundError: org/apache/flex/tools/FlexTool I check if it could be flex-tool-api.jar, but this jar is in "flexjs/js/lib" folder Anyone knows what could be the problem? Thanks 2016-03-16 22:29 GMT+01:00 Justin Mclean : > Hi, > > > Thanks for noticing that. Have you looked at the notice files in the > builds? > > Only the source ones and they seem OKish (they don’t 100% follow policy > but there’s no legal issues that I can see). I’ve not looked at the binary > ones. I think a bigger issue (but again not one that would block a release > but more a nice to have) is that as a user I would expect a lot more in the > REAME about changes from the previous version. Having a list of bug > fixes/new features would be a help to adoption. > > I’m also still unable to get the FlexJS source to compile but not looked > too deeply into it. > > compile-asjs: > [echo] Cross-compiling Core-0.6.0.swc > [echo] FALCONJX_HOME: > /Users/justinmclean/Downloads/ApacheFlexJS/apache-flex-falconjx-0.6.0-bin/js/ > [java] Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/flex/tools/FlexTool > > ... > BUILD FAILED > /Users/justinmclean/Downloads/ApacheFlexJS/apache-flex-flexjs-0.6.0-src/frameworks/projects/Core/build.xml:125: > Replace: source file > /Users/justinmclean/Downloads/ApacheFlexJS/apache-flex-flexjs-0.6.0-src/frameworks/projects/Core/target/generated-sources/flexjs/org/apache/flex/events/IEventDispatcher.js > doesn't exist > > Thanks, > Justin -- Carlos Rovira Director General M: +34 607 22 60 05 http://www.codeoscopic.com http://www.avant2.es Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la prestación del servicio o información solicitados, teniendo usted derecho de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación necesaria.
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
On 3/22/16, 12:19 AM, "piotrz" wrote: >Hi Alex, > >I'll try examining FlexJS package tomorrow. Do you expect to do from PMCs >something more than in your approval script? The approval script attempts to guide you to check the minimum requirements. > >I'm still try to change paths in Build.xml for examples, but building >FlexJS >is taking me more time than I thought. - For sure these changes are not >for >this relese. What problems are you running into getting the repo to build? -Alex
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
I checked the nightly bin and src yesterday on my Mac and they checked out fine. I'm going to fire up my Windows machine today and see what happens. Peter > On Mar 22, 2016, at 2:49 AM, Alex Harui wrote: > > I think I'm done fixing bugs. We should cut an RC soon in case there are > complications. Has everyone who plans to vote reviewed the nightly > packages? Anybody have anything else they want to cram in this release? > > Thanks, > -Alex > >> On 3/14/16, 10:41 PM, "Alex Harui" wrote: >> >> I did a pass through the packages and made some changes that should now be >> reflected in the nightly builds. It would be helpful if others also >> examined the packages before we start cutting release candidates. >> >> FlexJS: >> http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs/lastSuccessfulBuild >> / >> artifact/out/ >> FalconJX: >> http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/lastSuccessfulBui >> l >> d/artifact/out/ >> For FalconJX, we are only interested in the apache-flex-falconjx packages, >> not the apache-flex-falcon packages. >> >> -Alex >
RE: LAST CALL] Release FlexJS/FalconJX 0.6.0
I haven't gotten around to checking it. I'll look it over tonight. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, March 22, 2016 2:50 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: LAST CALL] Release FlexJS/FalconJX 0.6.0 I think I'm done fixing bugs. We should cut an RC soon in case there are complications. Has everyone who plans to vote reviewed the nightly packages? Anybody have anything else they want to cram in this release? Thanks, -Alex On 3/14/16, 10:41 PM, "Alex Harui" wrote: > >I did a pass through the packages and made some changes that should now be >reflected in the nightly builds. It would be helpful if others also >examined the packages before we start cutting release candidates. > >FlexJS: >http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs/lastSuccessfulBuild >/ >artifact/out/ >FalconJX: >http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/lastSuccessfulBui >l >d/artifact/out/ >For FalconJX, we are only interested in the apache-flex-falconjx packages, >not the apache-flex-falcon packages. > >-Alex >
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
Hi Alex, I'll try examining FlexJS package tomorrow. Do you expect to do from PMCs something more than in your approval script? I'm still try to change paths in Build.xml for examples, but building FlexJS is taking me more time than I thought. - For sure these changes are not for this relese. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/LAST-CALL-Release-FlexJS-FalconJX-0-6-0-tp51803p51924.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
I think I'm done fixing bugs. We should cut an RC soon in case there are complications. Has everyone who plans to vote reviewed the nightly packages? Anybody have anything else they want to cram in this release? Thanks, -Alex On 3/14/16, 10:41 PM, "Alex Harui" wrote: > >I did a pass through the packages and made some changes that should now be >reflected in the nightly builds. It would be helpful if others also >examined the packages before we start cutting release candidates. > >FlexJS: >http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs/lastSuccessfulBuild >/ >artifact/out/ >FalconJX: >http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/lastSuccessfulBui >l >d/artifact/out/ >For FalconJX, we are only interested in the apache-flex-falconjx packages, >not the apache-flex-falcon packages. > >-Alex >
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
On 3/15/16, 10:16 PM, "Justin Mclean" wrote: > >I think there's a few ads issues that someone may want to look into: >http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs/lastSuccessfulBuild >/artifact/out/asdoc/validation_errors.log Thanks for noticing that. Have you looked at the notice files in the builds? -Alex
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
Hi, > Thanks for noticing that. Have you looked at the notice files in the builds? Only the source ones and they seem OKish (they don’t 100% follow policy but there’s no legal issues that I can see). I’ve not looked at the binary ones. I think a bigger issue (but again not one that would block a release but more a nice to have) is that as a user I would expect a lot more in the REAME about changes from the previous version. Having a list of bug fixes/new features would be a help to adoption. I’m also still unable to get the FlexJS source to compile but not looked too deeply into it. compile-asjs: [echo] Cross-compiling Core-0.6.0.swc [echo] FALCONJX_HOME: /Users/justinmclean/Downloads/ApacheFlexJS/apache-flex-falconjx-0.6.0-bin/js/ [java] Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/flex/tools/FlexTool ... BUILD FAILED /Users/justinmclean/Downloads/ApacheFlexJS/apache-flex-flexjs-0.6.0-src/frameworks/projects/Core/build.xml:125: Replace: source file /Users/justinmclean/Downloads/ApacheFlexJS/apache-flex-flexjs-0.6.0-src/frameworks/projects/Core/target/generated-sources/flexjs/org/apache/flex/events/IEventDispatcher.js doesn't exist Thanks, Justin
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
Hi, > FlexJS: > http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs/lastSuccessfulBuild/ > artifact/out/ > FalconJX: > http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/lastSuccessfulBuil > d/artifact/out/ > For FalconJX, we are only interested in the apache-flex-falconjx packages, > not the apache-flex-falcon packages. I think there's a few ads issues that someone may want to look into: http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs/lastSuccessfulBuild/artifact/out/asdoc/validation_errors.log Justin
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
On 3/11/16, 8:49 AM, "Alex Harui" wrote: > > >On 3/10/16, 11:49 PM, "Justin Mclean" wrote: > >>Hi, >> >>Is there a dummy/test release to look at so the LICENSE/NOTICE, release >>notes etc etc can be checked? > >There are the nightly builds. I haven't worked on RELEASE_NOTES or >double-checked LICENSE and NOTICE yet, but the more eyes on it sooner, the >better off we are. I did a pass through the packages and made some changes that should now be reflected in the nightly builds. It would be helpful if others also examined the packages before we start cutting release candidates. FlexJS: http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs/lastSuccessfulBuild/ artifact/out/ FalconJX: http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/lastSuccessfulBuil d/artifact/out/ For FalconJX, we are only interested in the apache-flex-falconjx packages, not the apache-flex-falcon packages. -Alex
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
On 3/11/16, 9:34 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >On Mar 11, 2016 8:49 AM, "Alex Harui" wrote >> >> I'm wondering if we need to have a release branch. I don't think there >>is >> anything due to land in the develop branch that "shouldn't" go out in >> these releases. It saves time by not having to set up release branches >> and merge them back in. > >I think we should follow the tried and tested release process no matter >what. Otherwise, IMHO it would set a bad precedent. We've never cut a release branch for any prior release of FlexJS, so the bad precedence has already been set. I'm not a fan of burning time if there isn't any advantage. -Alex
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
On Mar 11, 2016 8:49 AM, "Alex Harui" wrote: > > > > On 3/10/16, 11:49 PM, "Justin Mclean" wrote: > > >Hi, > > > >Is there a dummy/test release to look at so the LICENSE/NOTICE, release > >notes etc etc can be checked? > > There are the nightly builds. I haven't worked on RELEASE_NOTES or > double-checked LICENSE and NOTICE yet, but the more eyes on it sooner, the > better off we are. > > I'm wondering if we need to have a release branch. I don't think there is > anything due to land in the develop branch that "shouldn't" go out in > these releases. It saves time by not having to set up release branches > and merge them back in. I think we should follow the tried and tested release process no matter what. Otherwise, IMHO it would set a bad precedent. Thanks, Om > > -Alex >
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
On 3/10/16, 11:49 PM, "Justin Mclean" wrote: >Hi, > >Is there a dummy/test release to look at so the LICENSE/NOTICE, release >notes etc etc can be checked? There are the nightly builds. I haven't worked on RELEASE_NOTES or double-checked LICENSE and NOTICE yet, but the more eyes on it sooner, the better off we are. I'm wondering if we need to have a release branch. I don't think there is anything due to land in the develop branch that "shouldn't" go out in these releases. It saves time by not having to set up release branches and merge them back in. -Alex
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
Hi, Is there a dummy/test release to look at so the LICENSE/NOTICE, release notes etc etc can be checked? Thanks, Justin
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
On 3/10/16, 3:17 AM, "Tom Chiverton" wrote: >But means fixing the Mustella tests once and for all. FlexJS is unrelated to the mustella test runs that are failing. I keep hoping someone will be motivated enough to learn how to fix mustella tests so it doesn't always come down to me, but maybe I'll look after the April event. -ALex
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
+1 all things happening looks very promising (maven, npm, spark comps,...) and this should help to get more people interested. 2016-03-10 12:18 GMT+01:00 Michael Schmalle : > +1 I would try using the npm stuff and framework as an outside user, not s > core developer right now so it would be positive. > > Mike > > On Thu, Mar 10, 2016 at 6:09 AM, Kessler CTR Mark J < > mark.kessler@usmc.mil> wrote: > > > +1 > > > > Would have a positive impact and show continuous progress. > > > > > > -Mark > > > > -Original Message- > > From: Alex Harui [mailto:aha...@adobe.com] > > Sent: Wednesday, March 09, 2016 1:41 PM > > To: dev@flex.apache.org > > Subject: [Non-DoD Source] LAST CALL] Release FlexJS/FalconJX 0.6.0 > > > > Hi, > > > > Should we try to cut a release before the SF event? I don't think the > big > > things under development (Maven integration, Spark-like component set, > > XML) will land in time for the SF event, but we've fixed some bugs, added > > some features like Tree, Storage, Proxy, Reflection, and eliminated all > > hand-written JS files. > > > > Thoughts? > > -Alex > > > > > -- Carlos Rovira Director General M: +34 607 22 60 05 http://www.codeoscopic.com http://www.avant2.es Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la prestación del servicio o información solicitados, teniendo usted derecho de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación necesaria.
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
+1 I would try using the npm stuff and framework as an outside user, not s core developer right now so it would be positive. Mike On Thu, Mar 10, 2016 at 6:09 AM, Kessler CTR Mark J < mark.kessler@usmc.mil> wrote: > +1 > > Would have a positive impact and show continuous progress. > > > -Mark > > -Original Message- > From: Alex Harui [mailto:aha...@adobe.com] > Sent: Wednesday, March 09, 2016 1:41 PM > To: dev@flex.apache.org > Subject: [Non-DoD Source] LAST CALL] Release FlexJS/FalconJX 0.6.0 > > Hi, > > Should we try to cut a release before the SF event? I don't think the big > things under development (Maven integration, Spark-like component set, > XML) will land in time for the SF event, but we've fixed some bugs, added > some features like Tree, Storage, Proxy, Reflection, and eliminated all > hand-written JS files. > > Thoughts? > -Alex > >
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
But means fixing the Mustella tests once and for all. The usual trick of closing and opening each player version on the host hasn't worked: http://flex-mustella.cloudapp.net/?auto_refresh=false Tom On 10/03/16 11:09, Kessler CTR Mark J wrote: +1 Would have a positive impact and show continuous progress. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, March 09, 2016 1:41 PM To: dev@flex.apache.org Subject: [Non-DoD Source] LAST CALL] Release FlexJS/FalconJX 0.6.0 Hi, Should we try to cut a release before the SF event? I don't think the big things under development (Maven integration, Spark-like component set, XML) will land in time for the SF event, but we've fixed some bugs, added some features like Tree, Storage, Proxy, Reflection, and eliminated all hand-written JS files. Thoughts? -Alex __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __
RE: LAST CALL] Release FlexJS/FalconJX 0.6.0
+1 Would have a positive impact and show continuous progress. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, March 09, 2016 1:41 PM To: dev@flex.apache.org Subject: [Non-DoD Source] LAST CALL] Release FlexJS/FalconJX 0.6.0 Hi, Should we try to cut a release before the SF event? I don't think the big things under development (Maven integration, Spark-like component set, XML) will land in time for the SF event, but we've fixed some bugs, added some features like Tree, Storage, Proxy, Reflection, and eliminated all hand-written JS files. Thoughts? -Alex
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
On Mar 9, 2016 10:41 AM, "Alex Harui" wrote: > > Hi, > > Should we try to cut a release before the SF event? I don't think the big > things under development (Maven integration, Spark-like component set, > XML) will land in time for the SF event, but we've fixed some bugs, added > some features like Tree, Storage, Proxy, Reflection, and eliminated all > hand-written JS files. > +1 for a release before Apr 4th. I am ready to release the FlexJS npm module on the npm site. It would be a good exercise for me to release 0.5 right away and figure out the stuff needed to release an update while things are fresh in my mind. Thanks, Om > Thoughts? > -Alex >
Re: LAST CALL] Release FlexJS/FalconJX 0.6.0
Sounds good to me! Another release will keep momentum going, and I have some tutorials in the queue that will require 0.6. In terms of features, I also added a Node backend, extending the JSC backend, to output JavaScript for Node.js. It is accessible with the new asnodec script in js/bin. The node.swc only contains the signature for require() right now, but it's pretty cool, even without full typing of every Node API. - Josh On Mar 9, 2016 10:40 AM, "Alex Harui" wrote: > Hi, > > Should we try to cut a release before the SF event? I don't think the big > things under development (Maven integration, Spark-like component set, > XML) will land in time for the SF event, but we've fixed some bugs, added > some features like Tree, Storage, Proxy, Reflection, and eliminated all > hand-written JS files. > > Thoughts? > -Alex > >
