Hello Apache FlexJS Team,
I am pleased to report progress on the open source Moonshine IDE for Flex,
FlexJS, and ActionScript that Dhwani discussed at the FlexJS World Tour in
early April in San Francisco.
We have now released it through the Apple Mac App Store:
https://itunes.apple.com/us/app/m
Excellent! That sounds like a good plan to me. I suppose someone might start
with the source release package and not have Git, but I'd rather tell them to
install Git rather than GNU Patch.
Thanks,
-Alex
From: Christofer Dutz
mailto:christofer.d...@c-ware.de>>
Date: Wednesday, June 1, 2016 a
Hi Alex,
I wanted to use the maven-patch-plugin as I didn't want to add another required
executable to the build, but it turned out that it implicitly did. The plugin
internally executes the "patch" command, which fails on windows machines per
default. I therefore replaced that with a exec-mav
I'll give it a shot tonight.
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Wednesday, June 01, 2016 10:11 AM
To: Kessler CTR Mark J; dev@flex.apache.org
Subject: [Non-DoD Source] Re: Package keyword and import class
Can you try with falcon?
Sent from my LG G3, an AT
No, what I'm trying to say is the patch I generated contains the result of
running externc with -js–root which is why it is more complex set of changes
than the ones you generated. One of the reasons to do the patch approach was
so that Maven doesn't have to run ExternC with js-root.
So, reall
Hi Alex,
I have to admit that I had problems following your second last email ... I am
sure the patch isn't 100% as I noticed some regexp replacing had changed in Ant
since I migrated them to Maven. Another reason why I like the Patch approach :-)
So do I understand you correctly? I need to r
Can you try with falcon?
Sent from my LG G3, an AT&T 4G LTE smartphone
-- Original message--
From: Kessler CTR Mark J
Date: Wed, Jun 1, 2016 4:38 AM
To: 'dev@flex.apache.org';
Subject:Package keyword and import class
Bumped into a path for a project that has a folder with "package" in th
Bumped into a path for a project that has a folder with "package" in the name
and it causes a syntax error[1]. Shouldn't the import pathing be able to
handle any folder name without keywords interfering with it? At this time,
just renaming the folder works to correct it.
Doesn't work:
impor
