install error (from twitter)
Hi, From twitter: @ApacheFlex Thx. Works now but install fails with unable to create temporary directory. Cleaned out temp files and restarted. Any tips? @ApacheFlex Ok never mind. Creating a new folder outside of #FlashBuilder seems to have worked. So this could be a common error - can we check the permissions on the folder when it is first selected? Justin
Re: Next Donation from Adobe
Thanks you Alex and Adobe! EdB On Sat, Apr 26, 2014 at 6:27 AM, Alex Harui aha...@adobe.com wrote: Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Next Donation from Adobe
Hi, Yep great news! And that's everything Adobe was going to donate right - there's nothing left outstanding? Thanks, Justin
RE: Next Donation from Adobe
Thanks Alex (and Adobe). Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : samedi 26 avril 2014 06:28 À : dev@flex.apache.org Objet : Re: Next Donation from Adobe Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
Re: [DISCUSS] Release Apache Flex SDK 4.12.1 RC1
Hi, There a few minor issues with README/RELEASE_NOTE and AIR/FP 13 support - but certainly not blockers. I've updated and checked in for next RC if there is one. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.12.1 RC1
Hi, Not a big issue but not 100% sure what TLF fixes have gone into this release as the TLF is missing a tag. TLF fixes FLEX-34098, FLEX-33985 and FLEX-33423 are not mentioned in the release notes. Justin
Re: [DISCUSS] Release Apache Flex SDK 4.12.1 RC1
HI, I think FLEX-34013 may be missing from the release notes (or was the checkin comment incorrect and it was meant to be FLEX-34231?). Justin
Re: [DISCUSS] Release Apache Flex SDK 4.12.1 RC1
Hi, Probably not an issue but I noticed that bin/compc and bin/mxmlc are not executable after a build from source - but they probably should be. Justin
Re: [DISCUSS] Release Apache Flex SDK 4.12.1 RC1
Hi, Probably not an issue but I noticed that bin/compc and bin/mxmlc are not executable after a build from source - but they probably should be. This causes ant checkintests to fail after compiling, once fixed, they still fail due to FP trust issue - do we have this documented in the readme/release_notes? Thanks, Justin
Flex JS installer stats
Hi, JFYI. On windows 40 successes, 30 failures. On mac 16 successes no failures. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.12.1 RC1
Hi, Found a potential blocker. After running /ide/constructFlexForIDE.sh on a compile SDK the flex config RSL version numbers are incorrect and have 0 for the build number. I know most people use the installer and won't encounter this issue but probably indicates that something is amiss somewhere. The flex-sdk-description.xml file does have the correct build number. I also tried running /ide/flashbuilder/makeApacheFlexForIDE.sh and it also produced incorrect RSL build numbers. Everything else looks good but I've not fully tested the SDK yet. Thanks, Justin
Re: [VOTE] Apache Flex SDK 4.12.1 RC1
Hi, -1 (binding) for now Signatures + hashes good README, RELEASE_NOTES, NOTICE, LICENCE all OK (minor changes + a few missing fixes can be put into RC2 if you think it's needed) Can compile from source ant checkintests pass (after manually made executable and flash file added to trusted list) Can create RSL files After running /ide/constructFlexForIDE.sh flex config RSL version numbers are incorrect and have 0 for the build number - that's a blocker for me. The files in /ide/config/flashbuilder has 0 as the build number rather than the correct build number - that may be the issue? Tested on OSX and with Flash Builder. Thanks, Justin
RE: Next Donation from Adobe
Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
AW: AW: FlexUnit 4.2 ant build broken
Then I'll have a look at the Maven templates ... As I could see there seems to be a maven release target in the ant scripts, that take care of the signing and deploying. But it's built for the Sonatype OSS repo and not the Apache one ... would investigate a little and update that to Apache. Then you could do the releases yourself. Chris -Ursprüngliche Nachricht- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Freitag, 25. April 2014 15:12 An: dev@flex.apache.org Betreff: Re: AW: FlexUnit 4.2 ant build broken I've already checked in changes like that. We found them moving CI to our own Windows box. Might need to think about doing a 4.2.1. -Alex On 4/25/14 1:47 AM, Christofer Dutz christofer.d...@c-ware.de wrote: Hi, I too encountered some problems with the FlexUnit build on Windows 7 ... I fixed all issues by adjusting one of the URLs in the ant script, which caused a double / in the url for downloading something related with Fluint support. It seems the original github location no longer exists and github forwards the client to another url, but in the case of the double / this doesn't work. By removing the / I got everything to build. I'll re-check my changes and commit them this weekend. One other thing I noticed is that we are downloading binary files from the old flexunit github account ... I think it would be a good Idea to change these urls. Eventually we could download the third party libs from maven central (You can download from Maven Central as you can from any other location). Chris Von: Daniel Tiefenauer daniel.tiefena...@crealogix.com Gesendet: Freitag, 25. April 2014 10:38 An: dev@flex.apache.org Betreff: AW: FlexUnit 4.2 ant build broken Hi Justin I'm using Windows 7. By the way: I read in this post [1] that FlexUnit 4.2 will support Code Coverage with Apparat. When will this be available? I tried to produce a coverage report by running 'ant test -Dbuild.instrument=true -DFLEX_COVER_HOME=path/to/FlexCoverDirectory', As my FlexCoverDirectory I'm using a Flex 4.12/AIR4.0-SDK directory, over which I copied the contents of the 'sdk-modifications-4_0'-folder from the flexcover-0.90.zip found in FlexUnit4FlexCoverListener/in. My ANT_HOME points to an installation of Ant 1.9.3 and my JAVA_HOME to the Java 8 SDK. But I always get a java.lang.NoClasDefFoundError. Is this feature supposed to work? Regards Daniel [1] http://forums.adobe.com/message/3178595 -Ursprüngliche Nachricht- Von: Justin Mclean [mailto:jus...@classsoftware.com] Gesendet: Freitag, 25. April 2014 10:23 An: dev@flex.apache.org Betreff: Re: FlexUnit 4.2 ant build broken Hi, Thanks for fining that - just out of interest what platform were you on? Justin
[FlexJS] Getting \sdks\FlexJS-0.0.1\js\bin\..\..) was unexpected at this time. error
First of all my Heartily Greetings to the entire Apache Flex team for making the FlexJS release a reality, I have been following up the hard work that you people have been putting into it... It's like a dream coming true for most, believe me :) The SDK Installer Ver. 3 works excellent, it just needs a few mouse clicks and it does the required FlexJS setup without requiring any further input. I have set up the FlexJS SDK in my FB 4.7, have imported the Run Configs for it, it all look setup well. I imported the provided sample BarChartExample application and run it as a Flash app, it worked well and showed the Flash Chart running in browser. But when I chose Run External Tools Flex JS(JS COMPC) or Flex JS (FalconJX Debug and Release Build) it gives me following error at console, \sdks\FlexJS-0.0.1\js\bin\..\..) was unexpected at this time. I have a Windows 7-64 bit machine running with Intel Core-i3 processor. Please help, I am dieing to see the power of Flex JS and tell my clients that Flex is not dead rather it's coming back with a BIG-BANG-BANG! Thanks, Prem Flex/AIR/Flash Solution Architect
Maven Release Setup
Hi Guys, I have opened a ticket at infra to setup a staging repository for Apache Flex in the official Apache Maven Repository (Group Id org.apache.flex and below). In parallel I am working on adjusting the pom.template in FlexUnit to allow us publishing maven artifacts. So as soon as we are going to do the next release we will be able to publish them as Maven artifacts. This is also a good practice for setting up the pom-data in order to be able to release other parts as Maven in the near future. Just wanted to inform you, not that Infra starts asking questions and no one here knows why ;-) Chris
RE: Next Donation from Adobe
I ponderate my Great news with bad news because the new FDB is using classes from Falcon, not our actual compiler, so, I'm trying to check if it is possible to cherry pick the code used to debug the workers only (big work), ... Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 11:04:10 +0100 Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
AW: Next Donation from Adobe
Great news :-D As soon as my head is free of the things I'm currently working on ... BlazeDS will definitely get some attention from my side :-) Chris -Ursprüngliche Nachricht- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Samstag, 26. April 2014 06:28 An: dev@flex.apache.org Betreff: Re: Next Donation from Adobe Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
[FlexJS] adt.jar not found on FlexJS SDK
Hi. After installation of FlexJs through the new 3.0 intaller, i am following this https://cwiki.apache.org/confluence/display/FLEX/Using+FlexJS+with+Adobe+Flash+Builder; post to try this new baby. When i try to add flexJS SDK in Flash Builder 4.7, i get the following error. adt.jar not found in classpath of I am on win7 machine. Am i doing something wrong? -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-adt-jar-not-found-on-FlexJS-SDK-tp37266.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [FlexJS] Getting \sdks\FlexJS-0.0.1\js\bin\..\..) was unexpected at this time. error
Hi Prem, Thanks for trying it out. We have been finding bugs in the mxmlc.bat file the (FalconJX Debug and Release Build) launch config runs. There is an updated version in this bug: https://issues.apache.org/jira/browse/FLEX-34258 You can run the batch file directly by running mxmlc -fb path to project from the js\bin folder in the sdk. I'm wondering if there is some spaces-in-the-path issue the batch file isn't handling. Let us know how it goes, and thanks for trying FlexJS. -Alex On 4/26/14 2:46 AM, Prem Pratap Singh singh.pre...@gmail.com wrote: First of all my Heartily Greetings to the entire Apache Flex team for making the FlexJS release a reality, I have been following up the hard work that you people have been putting into it... It's like a dream coming true for most, believe me :) The SDK Installer Ver. 3 works excellent, it just needs a few mouse clicks and it does the required FlexJS setup without requiring any further input. I have set up the FlexJS SDK in my FB 4.7, have imported the Run Configs for it, it all look setup well. I imported the provided sample BarChartExample application and run it as a Flash app, it worked well and showed the Flash Chart running in browser. But when I chose Run External Tools Flex JS(JS COMPC) or Flex JS (FalconJX Debug and Release Build) it gives me following error at console, \sdks\FlexJS-0.0.1\js\bin\..\..) was unexpected at this time. I have a Windows 7-64 bit machine running with Intel Core-i3 processor. Please help, I am dieing to see the power of Flex JS and tell my clients that Flex is not dead rather it's coming back with a BIG-BANG-BANG! Thanks, Prem Flex/AIR/Flash Solution Architect
FlexUnit 4.3 prepared to be able to do Maven Releases
Ok ... so I got further than I expected today ... Actually I'm finished :-)
What I changed:
- Updated the metadata in the pom.template to match the requirements of Apache
releases.
- Updated the ant scripts to perform the releases to the Apache instead of the
Sonatype repos.
- Updated the Sample Maven application to use Flexmojos 7.1.0-SNAPSHOT and
Apache Flex 4.12.
- Tested a release to my private Artifactory instance (Worked great).
!!! IMPORTANT NOTE
In parallel I updated Flexmojos 7.1.0-SNAPSHOT to be able to work with FlexUnit
artifacts having a groupId of org.apache.flex.flexunit.
What actually needs to be done in order to deploy the artifacts in the next
release is:
- The person doing the release has to have PGP correctly setup
- Add a settings.xml file to your user home (~/.m2/settings.xml) and provide
the credentials for deploying artifacts to Apaches Staging repo
?xml version=1.0 encoding=UTF-8?
settings xsi:schemaLocation=http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;
xmlns=http://maven.apache.org/SETTINGS/1.1.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
servers
!-- Apache Maven Servers --
server
idapache.snapshots.https/id
username{myapacheuserid}/username
password{myapachepassword}/password
/server
server
idapache.releases.https/id
username{myapacheuserid}/username
password{myapachepassword}/password
/server
/servers
/settings
- Start the FlexUnit build:
ant apache-maven -Dmaven-pgp-passphrase={pgp-passphrase}
As soon as we have gotten this far we probably have to verify the staged
artifacts and then release the stage to make them officially released and
available. But we'll continue here as soon as Infra have setup everything
correctly.
All changes have been committed to the development branch.
Chris
Re: [DISCUSS] Release Apache Flex SDK 4.12.1 RC1
Did this work in past releases? Sent via the PANTECH Discover, an ATT 4G LTE smartphone. Justin Mclean jus...@classsoftware.com wrote: Hi, Found a potential blocker. After running /ide/constructFlexForIDE.sh on a compile SDK the flex config RSL version numbers are incorrect and have 0 for the build number. I know most people use the installer and won't encounter this issue but probably indicates that something is amiss somewhere. The flex-sdk-description.xml file does have the correct build number. I also tried running /ide/flashbuilder/makeApacheFlexForIDE.sh and it also produced incorrect RSL build numbers. Everything else looks good but I've not fully tested the SDK yet. Thanks, Justin
What GroupId for BlazeDS Maven Artifacts?
While I'm at it, I thought I'd give BlazeDS a try. Had to fix one or two things, but I noticed that the pom.xml files provided in the project all reference com.adobe.blazeds ... I guess we should change this. But what to? org.apache.flex.blazeds or org.aoache.blazeds First GroupId would make it more obvious that BlazeDS has something to do with Flex. But on the other side, could give the impression that you can only use it with Flex. After all even Adobe didn't tie it to Flex. I would suggest to use org.apache.flex.blazeds ... but that's just my opinion. What do you think? Chris
RE: Next Donation from Adobe
Ok, I've been able to pick up the needed code to make it run with our compiler classes used to evaluate expressions, unfortunately I can only test debugging session on command line, I haven't a FB license and my version expired time ago but I've got good result already, I can set a breakpoint in a worker and read values, more tests tomorrow. Btw, is there a open source license available for FB ? I tried with IntelliJ but didn't work, I guess it needs some integration code, not sure thought, so, Alexander, if you are around, please tell me if I can do something on my side or not pls. Will do more tests tomorrow and when good, open a Jira with the compiled fdb.jar for testing purposes and commit on the branch. I noticed the headers in the source files are not the same, there are a * before and after the license text in the current version and not in the new one, which one should we keep ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 15:10:11 +0100 I ponderate my Great news with bad news because the new FDB is using classes from Falcon, not our actual compiler, so, I'm trying to check if it is possible to cherry pick the code used to debug the workers only (big work), ... Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 11:04:10 +0100 Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
RE: FlexUnit 4.3 prepared to be able to do Maven Releases
Cool :-)
Frédéric THOMAS
From: christofer.d...@c-ware.de
To: dev@flex.apache.org
Subject: FlexUnit 4.3 prepared to be able to do Maven Releases
Date: Sat, 26 Apr 2014 15:54:11 +
Ok ... so I got further than I expected today ... Actually I'm finished :-)
What I changed:
- Updated the metadata in the pom.template to match the requirements of
Apache releases.
- Updated the ant scripts to perform the releases to the Apache instead of
the Sonatype repos.
- Updated the Sample Maven application to use Flexmojos 7.1.0-SNAPSHOT and
Apache Flex 4.12.
- Tested a release to my private Artifactory instance (Worked great).
!!! IMPORTANT NOTE
In parallel I updated Flexmojos 7.1.0-SNAPSHOT to be able to work with
FlexUnit artifacts having a groupId of org.apache.flex.flexunit.
What actually needs to be done in order to deploy the artifacts in the next
release is:
- The person doing the release has to have PGP correctly setup
- Add a settings.xml file to your user home (~/.m2/settings.xml) and provide
the credentials for deploying artifacts to Apaches Staging repo
?xml version=1.0 encoding=UTF-8?
settings xsi:schemaLocation=http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;
xmlns=http://maven.apache.org/SETTINGS/1.1.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
servers
!-- Apache Maven Servers --
server
idapache.snapshots.https/id
username{myapacheuserid}/username
password{myapachepassword}/password
/server
server
idapache.releases.https/id
username{myapacheuserid}/username
password{myapachepassword}/password
/server
/servers
/settings
- Start the FlexUnit build:
ant apache-maven -Dmaven-pgp-passphrase={pgp-passphrase}
As soon as we have gotten this far we probably have to verify the staged
artifacts and then release the stage to make them officially released and
available. But we'll continue here as soon as Infra have setup everything
correctly.
All changes have been committed to the development branch.
Chris
RE: What GroupId for BlazeDS Maven Artifacts?
If we really want to seems independant, which I'm not sure, it could be org.apache.blazeds but maybe it was what you meant as org.apache.flex.blazeds is reapeted in the first and last proposal. Frédéric THOMAS From: christofer.d...@c-ware.de To: dev@flex.apache.org Subject: What GroupId for BlazeDS Maven Artifacts? Date: Sat, 26 Apr 2014 18:01:30 + While I'm at it, I thought I'd give BlazeDS a try. Had to fix one or two things, but I noticed that the pom.xml files provided in the project all reference com.adobe.blazeds ... I guess we should change this. But what to? org.apache.flex.blazeds or org.aoache.blazeds First GroupId would make it more obvious that BlazeDS has something to do with Flex. But on the other side, could give the impression that you can only use it with Flex. After all even Adobe didn't tie it to Flex. I would suggest to use org.apache.flex.blazeds ... but that's just my opinion. What do you think? Chris
RE: Next Donation from Adobe
Oh Btw, I won't continue tomorrow as I can't but on Monday. Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 19:54:01 +0100 Ok, I've been able to pick up the needed code to make it run with our compiler classes used to evaluate expressions, unfortunately I can only test debugging session on command line, I haven't a FB license and my version expired time ago but I've got good result already, I can set a breakpoint in a worker and read values, more tests tomorrow. Btw, is there a open source license available for FB ? I tried with IntelliJ but didn't work, I guess it needs some integration code, not sure thought, so, Alexander, if you are around, please tell me if I can do something on my side or not pls. Will do more tests tomorrow and when good, open a Jira with the compiled fdb.jar for testing purposes and commit on the branch. I noticed the headers in the source files are not the same, there are a * before and after the license text in the current version and not in the new one, which one should we keep ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 15:10:11 +0100 I ponderate my Great news with bad news because the new FDB is using classes from Falcon, not our actual compiler, so, I'm trying to check if it is possible to cherry pick the code used to debug the workers only (big work), ... Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 11:04:10 +0100 Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
RE: Next Donation from Adobe
Another point, at the moment I'm integrating it to make it work with our compiler and the fixes I pushed before but the donated version uses the Flacon AST Classes to evaluate expresions, so, I wonder, once Flacon will be completed we could switch back to its classes or we don't need to wait ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 19:54:01 +0100 Ok, I've been able to pick up the needed code to make it run with our compiler classes used to evaluate expressions, unfortunately I can only test debugging session on command line, I haven't a FB license and my version expired time ago but I've got good result already, I can set a breakpoint in a worker and read values, more tests tomorrow. Btw, is there a open source license available for FB ? I tried with IntelliJ but didn't work, I guess it needs some integration code, not sure thought, so, Alexander, if you are around, please tell me if I can do something on my side or not pls. Will do more tests tomorrow and when good, open a Jira with the compiled fdb.jar for testing purposes and commit on the branch. I noticed the headers in the source files are not the same, there are a * before and after the license text in the current version and not in the new one, which one should we keep ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 15:10:11 +0100 I ponderate my Great news with bad news because the new FDB is using classes from Falcon, not our actual compiler, so, I'm trying to check if it is possible to cherry pick the code used to debug the workers only (big work), ... Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 11:04:10 +0100 Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
RE: Next Donation from Adobe
Something I don't get: Adobe is still selling FDB as part of Flash Builder, right? So why is this called a donation ? Maurice -Message d'origine- De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : samedi 26 avril 2014 21:39 À : dev@flex.apache.org Objet : RE: Next Donation from Adobe Another point, at the moment I'm integrating it to make it work with our compiler and the fixes I pushed before but the donated version uses the Flacon AST Classes to evaluate expresions, so, I wonder, once Flacon will be completed we could switch back to its classes or we don't need to wait ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 19:54:01 +0100 Ok, I've been able to pick up the needed code to make it run with our compiler classes used to evaluate expressions, unfortunately I can only test debugging session on command line, I haven't a FB license and my version expired time ago but I've got good result already, I can set a breakpoint in a worker and read values, more tests tomorrow. Btw, is there a open source license available for FB ? I tried with IntelliJ but didn't work, I guess it needs some integration code, not sure thought, so, Alexander, if you are around, please tell me if I can do something on my side or not pls. Will do more tests tomorrow and when good, open a Jira with the compiled fdb.jar for testing purposes and commit on the branch. I noticed the headers in the source files are not the same, there are a * before and after the license text in the current version and not in the new one, which one should we keep ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 15:10:11 +0100 I ponderate my Great news with bad news because the new FDB is using classes from Falcon, not our actual compiler, so, I'm trying to check if it is possible to cherry pick the code used to debug the workers only (big work), ... Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 11:04:10 +0100 Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right
Re: Next Donation from Adobe
Only thing I can think that is still outstanding is the donation of the docs (http://help.adobe.com/en_US/flex/using/index.html). Otherwise, I think that is just about everything I can think of.. -Nick On Sat, Apr 26, 2014 at 2:54 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, Yep great news! And that's everything Adobe was going to donate right - there's nothing left outstanding? Thanks, Justin
Re: What GroupId for BlazeDS Maven Artifacts?
org.apache.flex.blazeds is what I would recommend. BlazeDS is not a TLP. -nick On Sat, Apr 26, 2014 at 2:01 PM, Christofer Dutz christofer.d...@c-ware.dewrote: While I'm at it, I thought I'd give BlazeDS a try. Had to fix one or two things, but I noticed that the pom.xml files provided in the project all reference com.adobe.blazeds ... I guess we should change this. But what to? org.apache.flex.blazeds or org.aoache.blazeds First GroupId would make it more obvious that BlazeDS has something to do with Flex. But on the other side, could give the impression that you can only use it with Flex. After all even Adobe didn't tie it to Flex. I would suggest to use org.apache.flex.blazeds ... but that's just my opinion. What do you think? Chris
RE: FlexUnit 4.3 prepared to be able to do Maven Releases
Ok ... so I got further than I expected today ... Actually I'm finished :-) Nice work
Re: FlexUnit 4.3 prepared to be able to do Maven Releases
That's great news, Chris. Do you want to be the release manager for 4.3? On 4/26/14 1:45 PM, Michael A. Labriola labri...@digitalprimates.net wrote: Ok ... so I got further than I expected today ... Actually I'm finished :-) Nice work
Re: Next Donation from Adobe
On 4/26/14 12:45 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Something I don't get: Adobe is still selling FDB as part of Flash Builder, right? So why is this called a donation ? It is the term we use for 'granting a license to Apache'. -Alex
Re: Next Donation from Adobe
From the pre-incubation promises, that's pretty much it except maybe Flex 3.x. Since then, folks have asked for other things: 1) the search capability in asdoc 2) the docs Nick mentioned 3) the original FlexUnit 4) pieces of Flash Builder I have not done any work on those yet and they are not high on my list. -Alex On 4/26/14 1:07 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: Only thing I can think that is still outstanding is the donation of the docs (http://help.adobe.com/en_US/flex/using/index.html). Otherwise, I think that is just about everything I can think of.. -Nick On Sat, Apr 26, 2014 at 2:54 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, Yep great news! And that's everything Adobe was going to donate right - there's nothing left outstanding? Thanks, Justin
RE: Next Donation from Adobe
Understood. In this case, it would be nice to get the license to use the improved ASDOC tools ( the ones that generate searchable classes etc...) Like in: http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/ Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : samedi 26 avril 2014 23:51 À : dev@flex.apache.org Objet : Re: Next Donation from Adobe On 4/26/14 12:45 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Something I don't get: Adobe is still selling FDB as part of Flash Builder, right? So why is this called a donation ? It is the term we use for 'granting a license to Apache'. -Alex
Re: [FlexJS] adt.jar not found on FlexJS SDK
Hi Alex. Thanks for the reply. No. there isn´t any adt.jar on my instalation. Should i try to re install? 2014-04-26 16:15 GMT+01:00 Alex Harui [via Apache Flex Development] ml-node+s247n3726...@n4.nabble.com: On 4/26/14 7:26 AM, paulo.campos1 [hidden email]http://user/SendEmail.jtp?type=nodenode=37268i=0 wrote: Hi. After installation of FlexJs through the new 3.0 intaller, i am following this https://cwiki.apache.org/confluence/display/FLEX/Using+FlexJS+with+Adobe+ Flash+Builder post to try this new baby. When i try to add flexJS SDK in Flash Builder 4.7, i get the following error. adt.jar not found in classpath of I am on win7 machine. Am i doing something wrong? Hmm. Is there an adt.jar in the lib folder of your FlexJS SDK? Sometimes there can be a problem with the AIR SDK download. Thanks, -Alex -- If you reply to this email, your message will be added to the discussion below: http://apache-flex-development.247.n4.nabble.com/FlexJS-adt-jar-not-found-on-FlexJS-SDK-tp37266p37268.html To start a new topic under Apache Flex Development, email ml-node+s247n1...@n4.nabble.com To unsubscribe from Apache Flex Development, click herehttp://apache-flex-development.247.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=1code=cGF1bG8uY2FtcG9zQHBpY3RlbmdpbmUuY29tfDF8LTQwNDQxODkwMw== . NAMLhttp://apache-flex-development.247.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-adt-jar-not-found-on-FlexJS-SDK-tp37266p37271.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
[FDB] Integration
Hi,
To resume a bit what I did and discover today:
1- I merged the donated code to the the current FDB, keeping the existing fixes
and the current ExpressionEvaluator (I guess It is possible to use the new
Falcon based implementation modifying the ANT script which builds it, in order
to link the Falcon sources).
2- The new commands are worker workerID used to select a parlicular worker
by its ID and info workers, this is an example of what gives a break inside a
worker and what displays the 2 commands :
(fdb) info workers
!mainThread! 0 - !workerRunning!
!inWorker! {worker=1} - !workerSuspended! !workerSelected!
(fdb) worker 0
!workerChanged! !mainThread!
(fdb) info workers
!mainThread! 0 - !workerRunning! !workerSelected!
!inWorker! {worker=1} - !workerSuspended!
(fdb) worker 1
!workerChanged! 1
(fdb) info workers
!mainThread! 0 - !workerRunning!
!inWorker! {worker=1} - !workerSuspended! !workerSelected!
Note for IDE integration:
1- At the moment, watch, displays and breakpoints are set for 1 particular
worker, it means, they need to be defined again when a worker starts.
2- info breakpoints does well display the breakpoints for the same line and
on different worker of the same class but without the relative worker ID (I
guess it could be easily fixed)
I'll be back on it on Monday.
Frédéric THOMAS
Re: [FlexJS] adt.jar not found on FlexJS SDK
Yes, and don't close the installer until you've checked to see if it worked. Post the log from the installer if there are still problems. -Alex On 4/26/14 9:42 AM, paulo.campos1 paulo.cam...@pictengine.com wrote: Hi Alex. Thanks for the reply. No. there isn´t any adt.jar on my instalation. Should i try to re install? 2014-04-26 16:15 GMT+01:00 Alex Harui [via Apache Flex Development] ml-node+s247n3726...@n4.nabble.com: On 4/26/14 7:26 AM, paulo.campos1 [hidden email]http://user/SendEmail.jtp?type=nodenode=37268i=0 wrote: Hi. After installation of FlexJs through the new 3.0 intaller, i am following this https://cwiki.apache.org/confluence/display/FLEX/Using+FlexJS+with+Adobe+ Flash+Builder post to try this new baby. When i try to add flexJS SDK in Flash Builder 4.7, i get the following error. adt.jar not found in classpath of I am on win7 machine. Am i doing something wrong? Hmm. Is there an adt.jar in the lib folder of your FlexJS SDK? Sometimes there can be a problem with the AIR SDK download. Thanks, -Alex -- If you reply to this email, your message will be added to the discussion below: http://apache-flex-development.247.n4.nabble.com/FlexJS-adt-jar-not-f ound-on-FlexJS-SDK-tp37266p37268.html To start a new topic under Apache Flex Development, email ml-node+s247n1...@n4.nabble.com To unsubscribe from Apache Flex Development, click herehttp://apache-flex-development.247.n4.nabble.com/template/NamlSe rvlet.jtp?macro=unsubscribe_by_codenode=1code=cGF1bG8uY2FtcG9zQHBpY3Rlb mdpbmUuY29tfDF8LTQwNDQxODkwMw== . NAMLhttp://apache-flex-development.247.n4.nabble.com/template/NamlSe rvlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=n abble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNames pace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscriber s%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant _email%21nabble%3Aemail.naml -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-adt-jar-not-fo und-on-FlexJS-SDK-tp37266p37271.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [FDB] Integration
Awesome!
On 4/26/14 5:01 PM, Frédéric THOMAS webdoubl...@hotmail.com wrote:
Hi,
To resume a bit what I did and discover today:
1- I merged the donated code to the the current FDB, keeping the existing
fixes and the current ExpressionEvaluator (I guess It is possible to use
the new Falcon based implementation modifying the ANT script which builds
it, in order to link the Falcon sources).
2- The new commands are worker workerID used to select a parlicular
worker by its ID and info workers, this is an example of what gives a
break inside a worker and what displays the 2 commands :
(fdb) info workers
!mainThread! 0 - !workerRunning!
!inWorker! {worker=1} - !workerSuspended! !workerSelected!
(fdb) worker 0
!workerChanged! !mainThread!
(fdb) info workers
!mainThread! 0 - !workerRunning! !workerSelected!
!inWorker! {worker=1} - !workerSuspended!
(fdb) worker 1
!workerChanged! 1
(fdb) info workers
!mainThread! 0 - !workerRunning!
!inWorker! {worker=1} - !workerSuspended! !workerSelected!
Note for IDE integration:
1- At the moment, watch, displays and breakpoints are set for 1
particular worker, it means, they need to be defined again when a worker
starts.
2- info breakpoints does well display the breakpoints for the same line
and on different worker of the same class but without the relative worker
ID (I guess it could be easily fixed)
I'll be back on it on Monday.
Frédéric THOMAS
Re: [DISCUSS] Release Apache Flex SDK 4.12.1 RC1
On 4/26/14 1:22 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Probably not an issue but I noticed that bin/compc and bin/mxmlc are not executable after a build from source - but they probably should be. This causes ant checkintests to fail after compiling, once fixed, they still fail due to FP trust issue - do we have this documented in the readme/release_notes? Feel free to add to either or both. Has it been this way for a while? We could probably wait on doing a real fix since nobody has found it before. I will cut an RC2 soon. -Alex
