> But, the TLF branch was not yet cut. Right? I should continue working on
> develop. Is that correct?
That is correct. We'll cut that branch when we get to it ;-)
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Hi,
Just checked in a patch to constructFexForIDE.sh that should fix this issue on
OSX. Can someone test that on windows for me. I think some people may be
running the .sh on windows using cygwin, rather than running the
constructFexForIDE.bat file.
Thanks,
Justin
Makes sense to me.
On Dec 14, 2014, at 9:14 AM, Justin Mclean wrote:
> Hi,
>
> Given FP 16 is now out should we add support for it before releasing?
>
> It doesn't look like AIR 16 is officially out yet but I'm sure it's probably
> only a few days away.
>
> Thanks,
> Justin
I don’t see the 4.14 branch. Am I clueless, or what?
On Dec 12, 2014, at 11:08 AM, Erik de Bruin wrote:
> Hi,
>
> I just cut the release branch for the 4.14.0 release. I'm hooking that
> branch up to CI and Mustella right now, I'll update when that's done.
>
> I someone (Alex, Om?) can then ad
Never mind. I was looking in the wrong repo…
But, the TLF branch was not yet cut. Right? I should continue working on
develop. Is that correct?
On Dec 14, 2014, at 9:23 AM, Harbs wrote:
> I don’t see the 4.14 branch. Am I clueless, or what?
>
> On Dec 12, 2014, at 11:08 AM, Erik de Bruin wro
Justin, thanks for 743748429
When tested and shown to be the solution, that negates my objection to
the changes to that section of the README.
EdB
On Sun, Dec 14, 2014 at 7:45 AM, Erik de Bruin wrote:
> First there was [1], than the workaround was 'found' [2].
>
> I do not know of a more stru
Hi,
Given FP 16 is now out should we add support for it before releasing?
It doesn't look like AIR 16 is officially out yet but I'm sure it's probably
only a few days away.
Thanks,
Justin
On 12/13/14, 1:45 PM, "Gordon Smith" wrote:
>> I get the following error on a clean copy of the SDK, when I do an
>> 'ant release' ... But as soon as I did an 'ant' on 'flex-blazeds' and
>> then tried again, the problem went away ...
>> [javac]
>>/Users/erik/Documents/ApacheFlex/git/flexblazed
Hi Gordon,
On the Build VM we use:
Java: 1.7
Ant: 1.9
Maven: ?
Flash Player: 11.1
AIR: 15
On the Mustella VM we use:
Java: 1.6
Ant: 1.9
Maven: ?
Flash Player: 11.1, 11.7, 13 and 15
AIR: 3.7, 4, 15
Thanks,
EdB
On Sat, Dec 13, 2014 at 10:50 PM, Gordon Smith wrote:
> Do we document anywhere
> Can some-one else follow the steps in the README and see if they:
> a) Can correctly compile an SDK for use in an IDE by following the steps
> under "Prepare the SDK for use with an IDE"
> b) Run into the issue with AIR not being installed correctly on OSX
I've moved this discussion to it's own
First there was [1], than the workaround was 'found' [2].
I do not know of a more structural fix since then, so my position on
the workaround remaining in the README until one is applied stands.
EdB
1: http://markmail.org/message/wo2t3zxdc5vr7viy
2: http://markmail.org/message/v6adlc5qlgz5h6rp
That's some great info Gordon. Once I finish some of my current tasks I'll
look again into MXML.
I'm working with the old compiler in mind, I'd love to see Falcon finished,
and being able to use it for code completion would be great if it proves to
be fast enough. Using the compiler services is ho
Hi,
Can some-one else follow the steps in the README and see if they:
a) Can correctly compile an SDK for use in an IDE by following the steps under
"Prepare the SDK for use with an IDE"
b) Run into the issue with AIR not being installed correctly on OSX
Thanks,
Justin
Hi,
> This is one of those emails you should probably have re-read before
> sending. It's tone is rather confrontational and argumentative.
There's is no intended tone, they are just simple straight forward questions.
> I said nothing about a CI setup on Mac, so I'm not sure what you're talking
>> Do you have time to rewrite that section? That way we can "commit, then
>> review."
>
> It was a question to discuss to work out what if any changes are needed, at
> this point in time I'm not sure what exactly needs to change.
Fair enough. Please start a new thread to discuss the possible ch
>>> with (FP) versions 11.1, 11.7, 13.0 and 15.0 on Windows and Mac.
>
> So the current CI is set up to run the mustella tests on 11.1, 11.7, 13.0 and
> 15.0? And we have a CI setup on Mac that I don't know about?
This is one of those emails you should probably have re-read before
sending. It's t
>> It is required, I'm afraid. I tested that thoroughly before writing
>> that section.
>
> If it required then we have an issue. How did you install it?
>
> Perhaps related to this?
> https://issues.apache.org/jira/browse/FLEX-34460
Maybe. Possibly. Anyway, the README as it was accurately describ
Do we document anywhere the versions of Java, Ant, Maven, Flash Player, AIR,
etc. that the build/test machines are currently using? I'd like to use the same
versions.
- Gordon
> I get the following error on a clean copy of the SDK, when I do an
> 'ant release' ... But as soon as I did an 'ant' on 'flex-blazeds' and
> then tried again, the problem went away ...
> [javac]
> /Users/erik/Documents/ApacheFlex/git/flexblazeds/modules/common/src/flex/messaging/config/ApacheXPa
I have a few points to belatedly make on this thread:
1. The 'specifications' folder of the 'flex-external' repository has a spec for
MXML 2006 and 2009. It's incomplete, but it's the best one that exists. If you
find that it doesn't answer your questions about which elements are allowed
insid
HI,
> Do you have time to rewrite that section? That way we can "commit, then
> review."
It was a question to discuss to work out what if any changes are needed, at
this point in time I'm not sure what exactly needs to change.
Justin
HI,
>> with (FP) versions 11.1, 11.7, 13.0 and 15.0 on Windows and Mac.
So the current CI is set up to run the mustella tests on 11.1, 11.7, 13.0 and
15.0? And we have a CI setup on Mac that I don't know about?
Justin
Hi,
> It is required, I'm afraid. I tested that thoroughly before writing
> that section.
If it required then we have an issue. How did you install it?
Perhaps related to this?
https://issues.apache.org/jira/browse/FLEX-34460
> 'constructFlexForIDE' alone doesn't do the job on a Mac.
construct
+1 for Maven on BlazeDS. It is not something a lot of our users will be
directly using, and it will be a nice opportunity for us to get some
experience with an alternative build tool.
I would hope to see some documentation on the 'new' process on the Wiki, or
at least plenty comments in the build
Maybe we offer it via a Mavel release for those that want to build from
source, and offer a binary download. That should take care of both major
use cases, I think.
-Nick
On Sat, Dec 13, 2014 at 10:31 AM, Alex Harui wrote:
>
>
>
> On 12/13/14, 4:31 AM, "Christofer Dutz" wrote:
>
> >So if you g
On 12/13/14, 7:51 AM, "Christofer Dutz" wrote:
>Hi Alex,
>
>you mean if there is something else wrong with the current download
>mechanism breaking now and then ;-)
>I don't want to re-cite all the benefits I allready posted. For me it
>simply looks like a lot of problems we were and are having
Hi Alex,
you mean if there is something else wrong with the current download mechanism
breaking now and then ;-)
I don't want to re-cite all the benefits I allready posted. For me it simply
looks like a lot of problems we were and are having could be avoided by this.
And in my oppinion it's far
Shouldn't we make it as easy as possible for folks get BlazeDS, if we want
them to use it? If so, then it would sure help to have everything in one
zip, along with examples.
On Sat, Dec 13, 2014 at 11:31 AM, Alex Harui wrote:
>
>
>
> On 12/13/14, 4:31 AM, "Christofer Dutz" wrote:
>
> >So if you
On 12/13/14, 4:31 AM, "Christofer Dutz" wrote:
>So if you guys haven't got any objections, I would try starting the
>release process.
>But I would initiate the Maven release and not use the Ant stuff.
No objections from me, and I don’t think it matters to me whether you use
Maven or Ant, but I
Hi Chris,
I understand you aren’t suggesting a switch to Maven, but my understanding
of your proposal to use aether is that it would still require that folks
learn something about pom.xml in order to change the downloads for the ant
build, and require that folks get an external jar of ant tasks.
Hi Alex,
I'm not suggesting to switch to Maven ... all I was suggesting was to use the
part of Maven that deals with the downloading and resolving of artifacts using
maven and to keep the rest of the build. Could probably be as easy as replacing
the download.xml to not manually download the art
So if you guys haven't got any objections, I would try starting the release
process.
But I would initiate the Maven release and not use the Ant stuff.
I invested several days of fixing the testsuite a few months ago and I managed
to get all unit tests green. Also I switched all of my applicatio
I removed OSMF from NOTICE.
On 12/12/14, 10:52 PM, "e...@ixsoftware.nl" wrote:
>Hi,
>
>Moving the MPL license discussion to this thread, from the release
>DISCUSS thread.
>
>EdB
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl
33 matches
Mail list logo
