For FlexJS, the build scripts in flex-asjs assume you have the flex-sdk
and flex-flexunit repos co-located and built and grab the swcs from there.
Several Apache projects create a folder called something like “deps” and
check libraries in there.
Both ideas mean that the release package needs to d
Hi All,
I was trying lately build TLF on clean machine and I had to download couple
of dependencies manually.
I would like to change build script that these dependencies will be
downloadable automatically.
The question is - Which links should I provide to download these
dependencies?
- flexuni
Hi,
We currently don't track direct downloads from the mirrors so this may not be
essential. May also need to consider http vs https issues and more importantly
recording failures.
Justin
I don't think using the track-installer.html is going to work as it needs
to render a web page and execute a javascript function that does the actual
tracking. I don't think the Mavenizer is capable of doing it?
I think we should use the REST api that Google Analytics has recently
exposed to trac
Well I'll just wait for Om to give me the specs.
Chris
Von: Alex Harui
Gesendet: Dienstag, 7. April 2015 22:03
An: dev@flex.apache.org
Betreff: Re: AW: Requirements to track downloads via Mavenizer
On 4/7/15, 12:45 PM, "Christofer Dutz" wrote:
>Yeah ..
On 4/7/15, 12:45 PM, "Christofer Dutz" wrote:
>Yeah ... sure that I can do that ... just tell me what url to hit :-)
I’d prefer to defer to Om on what to hit. The base url is
track-installer.html on flex.a.o. We may want to use additional URL
parameters to denote that it is a Maven download.
Yeah ... sure that I can do that ... just tell me what url to hit :-)
Chris
-Ursprüngliche Nachricht-
Von: Alex Harui [mailto:aha...@adobe.com]
Gesendet: Dienstag, 7. April 2015 18:43
An: dev@flex.apache.org
Betreff: Re: Requirements to track downloads via Mavenizer
On 4/7/15, 5:10 AM
I don't have any problems with such a rewrite.
But looking at the content of the core module I wan't that sattisfied with it
so I invested some time today to write some CLI tool in which the user can
describe what he wants the tool to do and it does that. I'm currently testing
the little thing
A new entry has been added to the Apache Flex showcase for the app -
SimpleDiagrams.
Showcase: http://flex.apache.org/community-showcase.html
Product website: http://www.simplediagrams.com/
Thanks,
Om
> Google has deprecated @expose so this solution may stop working some day.
I would take that deprecated bit with a grain of salt:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/closure-compiler-discuss/pZaodHd0KD0/p767zHJzWO8J
I read that thread to mean that they want
CVE-2015-1773 Apache Flex reflected XSS vulnerability
Severity: Low
Vendor: The Apache Software Foundation
Versions Affected:
All versions of Apache Flex before 4.14.1
Description:
The asdoc tool produced JavaScript code that was vulnerable to a reflected XSS
attack. A request with a specially
I am glad you were able to work it out.
Looking forward, it appears that ECMA6 has support for AS3 like (or ECMA4
;-) like )getters and setters. Example here:
http://es6-features.org/?utm_content=buffer94d31&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer#GetterSetter
I am guessing
Update: Inspired by Erik’s suggestion to use @expose, I found that I can
use @expose on the structure keys instead of having to create more
prototype slots. So the pattern now is:
Object.defineProperties(org_apache_flex_utils_BinaryData.prototype, {
/** @expose */
productService: {
/** @
On 4/7/15, 5:10 AM, "Christofer Dutz" wrote:
>?Hi,
>
>
>As the Mavenizer is able to download and convert FDKs without the
>Installer it might be good to make sure the statistics are able to
>detect/distinguish them. Currently the Mavenizers Downloader accesses the
>same xml file as the installe
On 4/6/15, 11:28 PM, "Christofer Dutz" wrote:
>Hi,
>
>I canceled the vote for the Mavenizer. As I had to re-write the README,
>which still referenced the Mavenizer before my refactoring. I took the
>chance to implement a fourth converter module "fontkit" which should deal
>with the font related
> I did notice that on the installer page [1], the version number is not
> showing up on the badge. Can anybody take a stab at that one?
Done.
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
?Hi,
As the Mavenizer is able to download and convert FDKs without the Installer it
might be good to make sure the statistics are able to detect/distinguish them.
Currently the Mavenizers Downloader accesses the same xml file as the installer
does. Should I add any headers in order for our scr
gah. Moved onto the next shiny thing and forgot.
Seems like it's pushing live now.
I did notice that on the installer page [1], the version number is not
showing up on the badge. Can anybody take a stab at that one?
-Nick
[1] http://flex.apache.org/installer.html
On Tue, Apr 7, 2015 at 3:56
On 31/03/15 12:45, Nicholas Kwiatkowski wrote:
The only thing that isn't done is asdocs. The Apache SVN was doing weird
things last night when I got to that point. I'll try again this evening.
Did you crack this problem yet ?
I'm going to be busy next week.
Tom
19 matches
Mail list logo
