On 2/13/17, 2:50 PM, "Christofer Dutz" wrote:
>Hi Alex,
>
>Actually, it’s the sort of think I do enjoy doing … for example I did
>enjoy implmeneting the DMG decoding … but I do require format
>documentation or other pointers. If you could provide me with some more
>detailed information on this,
Hi Alex,
Actually, it’s the sort of think I do enjoy doing … for example I did enjoy
implmeneting the DMG decoding … but I do require format documentation or other
pointers. If you could provide me with some more detailed information on this,
I would consider putting that on my plate.
Chris
A
On 2/13/17, 11:25 AM, "Harbs" wrote:
>I have not been following this very closely. What does fontkit do?
Fontkit parses font files and converts them into data formats used by SWF
DefineFont tags. It's the kind of work I don't enjoy doing which is one
reason it hasn't been done. I think you c
I have not been following this very closely. What does fontkit do?
> On Feb 13, 2017, at 6:29 PM, Alex Harui wrote:
>
> +1 to replacing font kit. Are you volunteering to write the code to
> replace the font kit? I don't have the cycles.
>
> On 2/13/17, 2:23 AM, "carlos.rov...@gmail.com on beha
+1 to replacing font kit. Are you volunteering to write the code to
replace the font kit? I don't have the cycles.
On 2/13/17, 2:23 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>+1
>
>2017-02-13 10:45 GMT+01:00 Christofer Dutz :
>
>> Seriously? … download the entire Flex SDK
+1
2017-02-13 10:45 GMT+01:00 Christofer Dutz :
> Seriously? … download the entire Flex SDK for 4 Jars?
>
> Nope … not gonna happen … at least not if I have any saying in this matter.
>
> Think I’ll just drop support for the fontkit in the Mavenizer and make
> sure FlexJS’s Maven build doesn’t ne
Seriously? … download the entire Flex SDK for 4 Jars?
Nope … not gonna happen … at least not if I have any saying in this matter.
Think I’ll just drop support for the fontkit in the Mavenizer and make sure
FlexJS’s Maven build doesn’t need it. Perhaps we shouldn’t think about how we
can contin
On 2/11/17, 11:22 AM, "Josh Tynjala" wrote:
>This is also an issue for the Feathers SDK. I agree with Chris. If Adobe
>could move these files somewhere else, that would help the community a
>lot.
>The current workaround really seems like it's too cumbersome. Since the
>files are currently on So
This is also an issue for the Feathers SDK. I agree with Chris. If Adobe
could move these files somewhere else, that would help the community a lot.
The current workaround really seems like it's too cumbersome. Since the
files are currently on SourceForge, maybe a repository on Github would be
just
Well I have to make the mavenizer not stop if it’s not able to download.
I think this sucks … isn’t there a way for Adobe to host these files somewhere
else?
From my experience, if something doesn’t work out of the box and you have
people manually patch things, they lose interest. I doubt the Fle
The font kit is optional. Maybe some folks will have to go through more
steps to get it.
Saxon is available on Maven. Bundle the NOTICEs in our repo and call it
done.
My 2 cents,
-Alex
On 2/10/17, 2:00 PM, "Justin Mclean" wrote:
>Hi,
>
>> so we need our users to update the JCE, but this is
Hi,
> so we need our users to update the JCE, but this is not available outside of
> the US.
How do we get around this bit? (For context about 20% of our web site audience
is from the US). I’m not sure it's all countries however.
There seems to be serval countries where it can’t be used due
On 2/10/17, 8:10 AM, "Christofer Dutz" wrote:
>Ok so I tried to work around the problem for the largest part of the day,
>but it turns out not to be the certificate itself but the encryption
>strength sourceforge uses. It seems to require an encryption strength
>that the normal JDK simply can’t
Ok so I tried to work around the problem for the largest part of the day, but
it turns out not to be the certificate itself but the encryption strength
sourceforge uses. It seems to require an encryption strength that the normal
JDK simply can’t do, so we need our users to update the JCE, but th
So as the mavenizer is having the same error when downloading the fontkit libs,
I looked into this.
The problem is that sourceforge seems to have switched to certificates from
letsencrypt. Unfortunately, prior to 1.8.0_101 the default keystore doesn’t
trust those certificates. I don’t quite kno
On 2/7/17, 8:56 PM, "Justin Mclean" wrote:
>Hi,
>
>> Or you could say that it is "small amounts of source" and "that source
>>is
>> unmodified and unlikely to be changed" as it says in [1]. Or do you see
>> something else?
>
>I guess it falls into unlikely to be changed so probably OK but a li
Hi,
> Or you could say that it is "small amounts of source" and "that source is
> unmodified and unlikely to be changed" as it says in [1]. Or do you see
> something else?
I guess it falls into unlikely to be changed so probably OK but a little con
corded adding to our version controls.
If we
On 2/7/17, 8:35 PM, "Justin Mclean" wrote:
>Hi,
>
>> Yes, by changing the script. Any objections to checking in the files
>> currently downloaded to saxon9-NOTICES into the flex-sdk repo?
>
>Not sure we can, those file are under MPL license right? which is
>category B? [1]
The files in saxon9
I guess you can setup Maven repo at bintray (or general storage if you
prefer)
This should resolve all issues.
On Wed, Feb 8, 2017 at 11:35 AM, Justin Mclean
wrote:
> Hi,
>
> > Yes, by changing the script. Any objections to checking in the files
> > currently downloaded to saxon9-NOTICES into t
Hi,
> Yes, by changing the script. Any objections to checking in the files
> currently downloaded to saxon9-NOTICES into the flex-sdk repo?
Not sure we can, those file are under MPL license right? which is category B?
[1]
Thanks,
Justin
1. https://www.apache.org/legal/resolved#category-b
On 2/7/17, 6:44 PM, "Justin Mclean" wrote:
>Hi,
>
>> Right, so before we ship, should we tweak the script to pull the Maven
>> saxon and use notices stored in our repo?
>
>Already tried that but didn’t work as it looks like it was expecting more
>than just the jar.
>
>There may be a way around
Hi,
> Right, so before we ship, should we tweak the script to pull the Maven
> saxon and use notices stored in our repo?
Already tried that but didn’t work as it looks like it was expecting more than
just the jar.
There may be a way around it.
For the build scripts - not it unpacking a bin not
On 2/7/17, 6:20 PM, "Justin Mclean" wrote:
>Hi,
>
>> Not sure I understand. As long as the RM can download Saxon, they can
>> bundle saxon in the convenience binary and then it is no longer an
>>issue?
>
>The build script producing the artefacts currently fails so if anyone
>wanted to reproduc
Hi,
> Not sure I understand. As long as the RM can download Saxon, they can
> bundle saxon in the convenience binary and then it is no longer an issue?
The build script producing the artefacts currently fails so if anyone wanted to
reproduce the binaries from the source they may have some issue
On 2/6/17, 11:48 PM, "Justin Mclean" wrote:
>Hi,
>
>Good you could finally get to it compile.
>
>> I manually downloaded the maven jar from [1] and the build and
>>checkintests passed.
>
>That may be enough to get it to compile but it not quite enough to make a
>release. Our release bundles th
Hi,
Good you could finally get to it compile.
> I manually downloaded the maven jar from [1] and the build and checkintests
> passed.
That may be enough to get it to compile but it not quite enough to make a
release. Our release bundles the saxon LICENSE and several other files from the
zip
Oh thanks due reporting that. I'll look into it.
Chris
Von meinem Samsung Galaxy Smartphone gesendet.
Ursprüngliche Nachricht
Von: Justin Mclean
Datum: 07.02.17 03:18 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: source forge downloads failing
Hi,
BTW Chris the
Well, the adobe downloads worked, but I could not get saxon to work. It
might be time to use the Maven saxon.jar. I manually downloaded the maven
jar from [1] and the build and checkintests passed.
[1]
http://repo1.maven.org/maven2/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1
.0.8.jar
-Alex
This fixed it for me:
http://stackoverflow.com/questions/38203971/javax-net-ssl-sslhandshakeexcep
tion-received-fatal-alert-handshake-failure/38264878#38264878
See the part about jce. Not sure if it is available outside the US.
HTH,
-Alex
On 2/6/17, 6:18 PM, "Justin Mclean" wrote:
>Hi,
>
>BT
Hi,
BTW Chris the flex-sdk-converter is also failing with similar errors.
Justin
On 2/6/17, 12:44 PM, "Justin Mclean" wrote:
>Hi,
>
>> Which Java are your running? Some folks say that jdk1.8.0_66 might
>>help.
>
>1.8.0_73 (latest released on OSX)
Here are some links I saw when googling for it.
http://stackoverflow.com/questions/6353849/received-fatal-alert-handshake-f
ai
Hi,
> Which Java are your running? Some folks say that jdk1.8.0_66 might help.
1.8.0_73 (latest released on OSX)
Thanks,
Justin
I also found that update 101 of Java 8 fixes some certificate issues with
Let's Encrypt. I wouldn't expect Source Forge to be using that, but maybe
worth mentioning.
- Josh
On Feb 6, 2017 7:31 AM, "Alex Harui" wrote:
Which Java are your running? Some folks say that jdk1.8.0_66 might help.
-Al
All code and executables should be delivered over TLS.
Tom
On 06/02/17 15:20, Clint M wrote:
Would it be fine to use non https? This seems to work:
On 2/6/17, 5:07 AM, "Tom Chiverton" wrote:
>The MD5 checker Jenkins job is also hanging...
That's for a different reason (the VM runs out of memory trying to scan
the huge AIRSDK). I think I've fixed that. But thanks for noticing.
-Alex
Which Java are your running? Some folks say that jdk1.8.0_66 might help.
-Alex
On 2/6/17, 4:29 AM, "Justin Mclean" wrote:
>Hi,
>
>Just trying to make a new Flex SDK RC and we’re getting every source
>forge download failing :-(
>
>Curl with same URLs works as does the URL in a browser so it se
Would it be fine to use non https? This seems to work:
http://sourceforge.net/adobe/flexsdk/code/HEAD/tree/trunk/frameworks/libs/OSMF2_0.swc?format=raw
On Mon, Feb 6, 2017 at 4:29 AM, Justin Mclean
wrote:
> Hi,
>
> Just trying to make a new Flex SDK RC and we’re getting every source forge
> down
The MD5 checker Jenkins job is also hanging...
Tom
On 06/02/17 12:29, Justin Mclean wrote:
Hi,
Just trying to make a new Flex SDK RC and we’re getting every source forge
download failing :-(
Curl with same URLs works as does the URL in a browser so it seems to be an
ant / java issue.
For
Hi,
Just trying to make a new Flex SDK RC and we’re getting every source forge
download failing :-(
Curl with same URLs works as does the URL in a browser so it seems to be an
ant / java issue.
For instance:
download-osmf-swc:
[get] Getting:
https://sourceforge.net/adobe/flexsdk/code/
39 matches
Mail list logo
