Re: Tour De Flex component explorer

2014-08-08 Thread OmPrakash Muppirala
On Thu, Aug 7, 2014 at 11:37 PM, Justin Mclean wrote: > Hi, > > > 1. As mentioned, it would be good to include Flex 4 stuff as well. > I'd welcome a hand with that - either we'll need to work on getting the > app in TourDeFlex (as opposed to TourDeFlex3) working or move over each > example. > >

Re: Tour De Flex component explorer

2014-08-08 Thread Tom Chiverton
Some tiny things - will it run as part of the flex.apache.org site in future ? In the README the first line seems cumbersome. How does this sound instead The Tour De Flex component explorer provides a sample set of working Apache Flex examples. Tom On 08/08/14 03:15, Justin Mclean wrote: > Hi,

Re: Tour De Flex component explorer

2014-08-08 Thread Justin Mclean
Hi, > Some tiny things - will it run as part of the flex.apache.org site in > future ? Don't see why not - may need to have some navigation around it etc if we did that. Thanks, Justin

Re: Tour De Flex component explorer

2014-08-08 Thread Justin Mclean
Hi, Well that was rather painful, but the mx examples are now updated to use the more recent version of mx. Some improvements that can be made but IMO good enough for a first release. Justin

Re: Tour De Flex component explorer

2014-08-08 Thread Alex Harui
On 8/8/14 5:55 AM, "Justin Mclean" wrote: >Hi, > >Well that was rather painful, but the mx examples are now updated to use >the more recent version of mx. Some improvements that can be made but IMO >good enough for a first release. Did that cause the warnings to go away? I think the reason the

Re: Tour De Flex component explorer

2014-08-08 Thread Justin Mclean
Hi, > Did that cause the warnings to go away? All but one which is an SDK issue I think. Justin

Re: Tour De Flex component explorer

2014-08-08 Thread Alex Harui
On 8/7/14 11:55 PM, "Justin Mclean" wrote: > >> -I saw a note in http://www.apache.org/legal/resolved.html that says: >> "Many of these licenses have specific attribution terms that need to be >> adhered to, for example CC-A, often by adding them to the NOTICE file." > >Saw that as well - no ide

git server throws HTTP Error 502 when trying to push

2014-08-08 Thread Mihai Chira
I tried to push some commits to our git repo, and got this error: "fatal: unable to access 'https://git-wip-us.apache.org/repos/asf/flex-sdk.git/': The requested URL returned error: 502" Can others commit?

Re: git server throws HTTP Error 502 when trying to push

2014-08-08 Thread Mihai Chira
ok, works now. On 8 August 2014 17:11, Mihai Chira wrote: > I tried to push some commits to our git repo, and got this error: > "fatal: unable to access > 'https://git-wip-us.apache.org/repos/asf/flex-sdk.git/': The requested > URL returned error: 502" > > Can others commit?

Re: [JIRA](ISSUE #FLEX-34119) Dev review request

2014-08-08 Thread Mihai Chira
Frédéric, have you found out anything else regarding FishEye? I took a look, but the Flex project isn't there (in fact, there seems to be only one project, called "Default Project". It would be great to review each other's code using this. Piotr, have you committed the TLF automatic test running c

RE: [JIRA](ISSUE #FLEX-34119) Dev review request

2014-08-08 Thread Frédéric THOMAS
For Crucible (code review), nothing we can do on our side, only INFRA could request it and I didn't ask them to do so (if you want to ask, it's up to you, it would be a very nice feature but you don't be in hurry), only FishEye has been setup while ago https://fisheye6.atlassian.com/browse/flex-

Re: [JIRA](ISSUE #FLEX-34119) Dev review request

2014-08-08 Thread OmPrakash Muppirala
Our code is mirrored almost in real-time on to github. Github has excellent code review features. We can use that to do our post-commit code reviews. Here are the steps: 1. Go to https://github.com/apache/flex-sdk 2. In the 'branch' dropdown, select the branch: FLEX-34119 3. Click on the butt

Re: [JIRA](ISSUE #FLEX-34119) Dev review request

2014-08-08 Thread Mihai Chira
This is so useful, indeed! I'll start posting the links to my commits on github from now on when requesting dev reviews. Thanks, Om! On 8 August 2014 18:47, OmPrakash Muppirala wrote: > Our code is mirrored almost in real-time on to github. Github has > excellent code review features. We can

Re: [1/2] git commit: [flex-utilities] [refs/heads/develop] - an ant script to generate an installer RC including committing it to dist/dev/flex, tagging the git repo and generating a mailto with the

2014-08-08 Thread Justin Mclean
Hi, Isn't hard coding this a bit dangerous (causing potential incorrect info on changes to be mailed out)? > +Issues addressed in this release:\n\ > +- Installer will report more information when installs fail.\n\ > +- Bugs fixed in ant_on_air required by latest nightly builds of FalconJX and >

Tour de Flex

2014-08-08 Thread Juan Felipe Covarrubias Pous
I'd be glad to help, just let me know what i can do as a newbie developer Juan Felipe Covarrubias Director General *WorkStation* www.workstation.com.mx 6381 1316 04455 3433 7867

Re: Tour de Flex

2014-08-08 Thread Justin Mclean
HI, > I'd be glad to help, just let me know what i can do as a newbie developer Take a look as the examples here and either improve them or come up with a few more examples would be a good help. https://github.com/apache/flex-utilities/tree/develop/TourDeFlex/TourDeFlex3/src Currently all of t

Re: Tour de Flex

2014-08-08 Thread Justin Mclean
Hi, Open a JIRA for this conversion work and started on converting a few so you can see how it's done. https://issues.apache.org/jira/browse/FLEX-34459 Thanks, Justin

Re: [1/2] git commit: [flex-utilities] [refs/heads/develop] - an ant script to generate an installer RC including committing it to dist/dev/flex, tagging the git repo and generating a mailto with the

2014-08-08 Thread Alex Harui
On 8/8/14 5:20 PM, "Justin Mclean" wrote: >Hi, > >Isn't hard coding this a bit dangerous (causing potential incorrect info >on changes to be mailed out)? > >> +Issues addressed in this release:\n\ >> +- Installer will report more information when installs fail.\n\ >> +- Bugs fixed in ant_on_air