[RESULT] [VOTE] [BlazeDS] Release of Apache BlazeDS 4.7.0 RC2

Hi guys. Thanks :-) The vote passed with 3 +1 votes and no others. I'll set the staging repo to "release" right away. What else do I have to do now? Send an announcement to the dev- and user-list ... send one to the announce apache list and publish the source archives somewhere ... could you p

[BlazeDS] Continuing work on blazeds

Hi, I just created the develop branch. Whoever is planning on working on BlazeDS please use that branch as we have releases the Master is now reserved for released code. So after having the first release out the door, I would like to clean up the project. I don't want to do this without your

[FlexPMD] Starting work on FlexPMD

Hi, Summarizing the last state of FlexPMD in order to get others up to speed ... As PMD didn't support adding new languages, Adobe seem to have forked PMD years ago in order to build FlexPMD with this. This base version of PMD hasn't been updated for a long, long time. While the standalone An

RE: [fisheye] can we close the ticket ?

Hi, Thanks guys for having test that, the few feedbacks were positive, I therefore asked for closing the ticket at Atlassian, as a reminder I keep the link on it here [1]. Frédéric THOMAS [1] https://support.atlassian.com/servicedesk/customer/portal/18/FSH-15797 > From: mihai.ch...@gmail.com >

RE: Setup for patching

Side notes for monkey patching... 1. You can use it in your regular applications to override the classes in the flex sdk. 2. You will need to keep the path of the files package. You can find this by browsing through folders or looking up its ASDOC page. A button would be listed under "spa

Re: [fisheye] can we close the ticket ?

Late, but I can confirm that this works for me. Thanks Frédéric, for taking care of this issue! Regards, Om On Fri, Mar 6, 2015 at 2:29 AM, Frédéric THOMAS wrote: > Hi, > Thanks guys for having test that, the few feedbacks were positive, I > therefore asked for closing the ticket at Atlassian,

Re: [RESULT] [VOTE] [BlazeDS] Release of Apache BlazeDS 4.7.0 RC2

Hi, > I'll set the staging repo to "release" right away. What else do I have to do > now? - Publish the files to https://dist.apache.org/repos/dist/release/flex/ (via SVN) [1] - Update web site with release info - Wait 24 hours (for mirrors to catchup) then make an official announcement - Mark

Re: [BlazeDS] Continuing work on blazeds

Hi, > I would like to: > > - create an "attic" directory in the "modules" directory and move the root of > the current project there (ok ... all except the modules directory ;-) ) Perhaps "historical"? Apache has an attic [1] and probably best not suggest the code is there. > - move the cont

Re: [FlexPMD] Starting work on FlexPMD

Hi, > As the current version of PMD supports language modules, I would like to > extract the parts of FlexPMD that make up the Flex language support and > convert this into a PMD language module and drop the old PMD code. Do you have any idea of how much effort it going to be to convert the old

Re: [FlexPMD] Starting work on FlexPMD

Have fun! On 3/6/15, 1:01 AM, "Christofer Dutz" wrote: >Hi, > > >Summarizing the last state of FlexPMD in order to get others up to speed >... > > >As PMD didn't support adding new languages, Adobe seem to have forked PMD >years ago in order to build FlexPMD with this. This base version of PMD >

Re: [BlazeDS] Continuing work on blazeds

IMO, before doing something like this, I would wait until a week or so after the announcement of the BlazeDS release to see if folks try Apache Flex BlazeDS and then complain about lack of Ant support. -Alex On 3/6/15, 12:53 AM, "Christofer Dutz" wrote: >Hi, > > >I just created the develop bran

AW: [FlexPMD] Starting work on FlexPMD

Well actually I think it's not that difficult. Today I migrated the parser and the rule set part and a fist version (codename "MadeByMyGuyver") seems tob e runnning. Now I need to do a lot of cleaning up. The original testsuite was a mess of JUnit 3 and JUnit 4 ... so I started cleaning that up

AW: [BlazeDS] Continuing work on blazeds

BlazeDS supports nither Maven nor Ant ... it's just built with one or the other. So noone will probably complain about a release not supporting Ant ;-) Chris -Ursprüngliche Nachricht- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Freitag, 6. März 2015 22:32 An: dev@flex.apache.org

Re: [FlexPMD] Starting work on FlexPMD

Hi, > Today I migrated the parser and the rule set part and a fist version > (codename "MadeByMyGuyver") seems tob e runnning. Now I need to do a lot of > cleaning up. Any chance you could branch and check in as you go rather than just at the end? That way people can review and help out. PMD

Re: JAR in TLF svn/git mirror

Hi, Just replace the copyright text in th test with machine translated text from our README, as far as I can se eI've not broken any tests, but sorry in advanced if I have done so. I think that's all know IP issues dealt with and we can now close this JIRA. [1] Thanks, Justin 1. https://issue