Hi,
> But won't that require a new RC and a new vote? Are you okay with skipping
> that part?
Why? It what was voted on and released right?
Thanks,
Justin
On Sun, Aug 24, 2014 at 11:49 PM, Justin Mclean
wrote:
> Hi,
>
> > Are we good to push it to production?
>
> Unless anyone thinks the minor issues found so far should stop it being
> produced I'm fine for it to be pushed live.
>
>
But won't that require a new RC and a new vote? Are you okay with
On Sun, Aug 24, 2014 at 11:17 PM, Alex Harui wrote:
> And while we're on the subject of install errors. The SDK build hung
> because it couldn't download a dependency, and now all of our other builds
> will fail until the sdk build recovers.
>
> External download reliability apparently just isn'
Hi,
> Are we good to push it to production?
Unless anyone thinks the minor issues found so far should stop it being
produced I'm fine for it to be pushed live.
With a slight tweak we can change the announcement and remove the link and then
announce that next time we release.
Thanks,
Justin
Are we good to push it to production?
Thanks,
Om
On Aug 24, 2014 6:16 PM, "Justin Mclean" wrote:
> Hi,
>
> > One minor issue we probably need to change where the loading bar is
> located which is not noticeable when running locally.
> >
> > Someone mind raising a JIRA?
>
> Done - https://issues
On 8/24/14 11:29 PM, "Justin Mclean" wrote:
>>The MD5Checker seems to work, but the CI server keeps hanging saving the
>> artifacts of the flex-sdk-release build and then MD5Checker doesn't get
>>to
>> run.
>Can we make this more reliable by have it use a pre built SDK?
Currently, we only have
Hi,
> The download failure rate gets skewed when the MD5's become out of date
> because folks try again right away, maybe even more than once and get the
> same failure.
About 1/3rd of people try again, 2/3rd give up I would assume (pageview vs
unique pageview).
> The MD5Checker seems to work, b
And while we're on the subject of install errors. The SDK build hung
because it couldn't download a dependency, and now all of our other builds
will fail until the sdk build recovers.
External download reliability apparently just isn't that great.
-Alex
On 8/24/14 10:54 PM, "flex.ci.bui...@gmai
The download failure rate gets skewed when the MD5's become out of date
because folks try again right away, maybe even more than once and get the
same failure.
The MD5Checker seems to work, but the CI server keeps hanging saving the
artifacts of the flex-sdk-release build and then MD5Checker doesn
TextFieldHTMLImporter:
/** Parse the formatting element
* Calculates the new format to apply to _activeFormat and continues
parsing down the hierarchy
* @private
*/
static public function
parseStrikeThrough(importer:TextFieldHtmlImpor
Done. https://issues.apache.org/jira/browse/FLEX-34494
Thanks,
Om
On Sun, Aug 24, 2014 at 7:16 PM, Justin Mclean
wrote:
> Hi,
>
> Best to raise a JIRA so it's not forgotten about and potentially cause an
> unwanted RC cycle.
>
> Thanks,
> Justin
On Sun, Aug 24, 2014 at 6:49 PM, Justin Mclean wrote:
> Hi,
>
> Just took a look at the installer errors in the last week.
>
> Overall there here were 707 errors and 702 successful installs, that's a
> 50% error rate and the error rate is higher on windows. The good news is
> we've had 3000+ ins
Hi,
Best to raise a JIRA so it's not forgotten about and potentially cause an
unwanted RC cycle.
Thanks,
Justin
Hi,
> The good news is we've had 3000+ installs of Apache Flex4.13.0.
That's 3000+ install since we release 4.13.0 a month or so ago.
Thanks,
Justin
Hi,
Just took a look at the installer errors in the last week.
Overall there here were 707 errors and 702 successful installs, that's a 50%
error rate and the error rate is higher on windows. The good news is we've had
3000+ installs of Apache Flex4.13.0.
Here a rough total of the significan
Hi,
> One minor issue we probably need to change where the loading bar is located
> which is not noticeable when running locally.
>
> Someone mind raising a JIRA?
Done - https://issues.apache.org/jira/browse/FLEX-34493
Thanks,
Justin
Hi,
> The installer does not currently create the same thing as our releases.
We probably should change the SDK to match is in the released version, IMO
ant/lib seem a better place for it than lib.
Thanks,
Justin
Hi Andrew,
> Under Spark components > Containers there is "TitleGroup". It should be
> "TileGroup", which is the heading you see in the right panel when you
> select that item.
>
> Also, "SkinableDataContainer" should be "SkinnableDataContainer". the item
> in the menu is incorrect, and the title
It would probably be safer to say Apache Flex 4.9. I have not tested it
against Adobe Flex. There's a chance it won't even work.
-Alex
On 8/24/14 2:57 AM, "piotrz" wrote:
>Hi Alex,
>
>I have taken look into link with download FlexJS ->
>http://flex.apache.org/download-flexjs.html
>and I see t
If you build the repo or the source package, flextasks.jar is in lib. So,
IMO, in a release, the location is lib. The installer moves it to
ant/lib. The installer does not currently create the same thing as our
releases.
I generally create build scripts that run agains the repo, but feel free
t
Justin,
Have you tried creating an empty file named "MD5CheckerLog.txt"? Not sure
what would end up in there or should be in there, but if it's a log file,
then maybe the script is simply assuming it's there to log a message to it?
Chris
On Sun, Aug 24, 2014 at 8:45 AM, Alex Harui wrote:
> A
Actually this is probably the ant bug where some versions of ant error when
deleting a missing file and some don't. The ant scripts probably just need a
failonerror = false.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Alex Harui wrote:
I believe it is building fine on the CI ser
I believe it is building fine on the CI server.
On 8/24/14 2:15 AM, "Justin Mclean" wrote:
>Hi,
>
>I think we may also be missing a file?
>
>BUILD FAILED
>/Users/justinmclean/Documents/ApacheFlexUtilitiesGit/MD5Checker/build.xml:
>101:
>/Users/justinmclean/Documents/ApacheFlexUtilitiesGit/MD5Ch
Sounds right.
Also, I have checked releasecandidate.xml files into flex-falcon,
flex-asjs, flex-utilities/installer and flex-sdk. This ant script
attempts to run the release target in the build.xml for these projects and
sign them and move them to the dist server, etc. It might be a good
startin
Under Spark components > Containers there is "TitleGroup". It should be
"TileGroup", which is the heading you see in the right panel when you
select that item.
Also, "SkinableDataContainer" should be "SkinnableDataContainer". the item
in the menu is incorrect, and the title on the code view of the
I was on this as well and can't spend more time on it today, but I arrived at
the same conclusions and hate this kind of structure as well, anyway you're are
the best person to do it.
Thanks,
Frédéric THOMAS
> From: christofer.d...@c-ware.de
> To: dev@flex.apache.org
> Subject: AW: Flex PMD don
Hi Justin,
well it's not that big of a surprize as the Flexmojos artifacts are publically
available. Flexmojos is compiled against an Adobe Flex version that is also
publically available, so it will simply have automatically downloaded that old
Flex version. But I doubt it's something we should
Hi,
> While I'm at it ... currently all maven artifacts are structured in a flat
> directory and the "parents" are found using the "relativePath" tag ... I
> greatly dislike projects in this structure. Would there be any objections
> against me moving things around a little to reflect their nat
Hi Justin,
well I think this might be an issue. Maven releases need pom.xml files that
accompany the jars. There is quite a list of requirements to the content of
these poms. They then need to be signed and published to the staging repo. Then
we need to vote on the release and as soon as the vo
Hi,
> It is built with flexmojos 3.5.0 ... this is insanely old and completely
> incompatable with Apache Flex.
Surprised I managed to get anything to compile. :-)
> I also saw a lot of the Maven metadata needs updating ... the SCM the
> DistributionManagement and a lot more still point to Adob
Hi,
> Ok so would it be ok to take the released artifacts and to stage them in
> Apaches Staging Maven Repo? Or would this have to be a new release?
As they are already a release I see zero issues with that. May or may not need
a VOTE to move it into the release area? sorry but I'm not sure of
While I'm at it ... currently all maven artifacts are structured in a flat
directory and the "parents" are found using the "relativePath" tag ... I
greatly dislike projects in this structure. Would there be any objections
against me moving things around a little to reflect their natural structur
Hi Justin,
no wonder you were having a hard time with this ;-)
It is built with flexmojos 3.5.0 ... this is insanely old and completely
incompatable with Apache Flex.
Perhaps I should simply update the project to work with Flexmojos 7.0.0 and to
use Apache Flex 4.13
But as we have never released
Ok so would it be ok to take the released artifacts and to stage them in
Apaches Staging Maven Repo? Or would this have to be a new release?
Chris
-Ursprüngliche Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com]
Gesendet: Sonntag, 24. August 2014 12:49
An: dev@flex.apache
Hi,
> If FlexUnit has been released, have the Maven artifacts been released too?
I would guess not and wouldn't even know where to start on how to make that
happen. :-)
Justin
If FlexUnit has been released,
have the Maven artifacts been released too?
Chris
-Ursprüngliche Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com]
Gesendet: Sonntag, 24. August 2014 12:36
An: dev@flex.apache.org
Betreff: Re: Releasing BlazeDS, FlexUnit and Mavenizer
Hi,
>
Hi,
> - FlexUnit
FlexUnit has been officially released.[1]
> Is there anyone else willing to do at least one of these? Is there some
> "guidline for release managers" in which I could read what needs to be done?
You might want to take a look at [2] and [3] but I can also help out with s
I'll have a look at this ... usually in these cases, there's a "minimal"
profile you select to build the initial artifacts and then you can build as
normal.
Chris
-Ursprüngliche Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com]
Gesendet: Sonntag, 24. August 2014 10:42
An
Hi guys,
as it seems that noone else seems to be willing to do so, I would like to
volunteer to start releasing these parts:
- Mavenizer
- BlazeDS
- FlexUnit
I desperately need these officially released and would like to take care of the
process.
Is there anyone el
Looks ok, mine didn't point a player directory containing 14.0, the one I'm
using,
I also set
and
each time it was needed and I don't use AIR_HOME
Frédéric THOMAS
> Subject: Re: Squiggly Donation
> From: jus...@classsoftware.com
> Date: Sun, 24 Aug 2014 19:57:47 +1000
> To: dev@fl
Hi,
> I had the same issue and released that the player target / PLAYERGLOBAL_HOME
> / swf version didn't match, once aligned, Squiggly compiled fine.
What do you have PLAYERGLOBAL_HOME set to?
For me - ls $PLAYERGLOBAL_HOME gives:
10.010.211.011.211.411.611.812.0
Hi Alex,
I have taken look into link with download FlexJS ->
http://flex.apache.org/download-flexjs.html
and I see that we have in the requirements
"Apache Flex 4.6 or greater" It's probably should be "Adobe Flex 4.6 or
greater" If I am right I could change it ?
Piotr
-
Apache Flex Comm
using Apache Flex 4.13.0 FP 14 AIR 14 en_US
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: Squiggly Donation
> Date: Sun, 24 Aug 2014 10:20:13 +0100
>
> I had the same issue and released that the player target / PLAYERGLOBAL_HOME
> / swf version didn't m
I had the same issue and released that the player target / PLAYERGLOBAL_HOME /
swf version didn't match, once aligned, Squiggly compiled fine.
Frédéric THOMAS
> From: justinmcl...@me.com
> Subject: Squiggly Donation
> Date: Sun, 24 Aug 2014 18:32:11 +1000
> To: dev@flex.apache.org
>
> Hi,
>
>
Hi,
I think we may also be missing a file?
BUILD FAILED
/Users/justinmclean/Documents/ApacheFlexUtilitiesGit/MD5Checker/build.xml:101:
/Users/justinmclean/Documents/ApacheFlexUtilitiesGit/MD5Checker/MD5CheckerLog.txt
doesn't exist
Thanks,
Justin
Hi,
The Flex Utilities MD5 checker doesn't seem to be compiling on my machine.
It seems to expect to find flexTasks.jar in the $FLEX_HOME/lib directory where
in the Flex 4.13 release has the jar in ./ant/lib
Has the location changed or incorrect here? Is the installer placing it in the
correc
Hi,
I've taken a look at Flex PMD to see what it required to become a release and
can't make head or tails of the maven setup. It seem to me that each subproject
requires all the others to be already compiled - sort of a chicken and egg
issue. My knowledge about maven is minimal at best, so wou
Hi,
I was just having a quick look at the Squiggly donation and notice that it
doesn't currently compile. I get this error:
compileframework:
[java] Loading configuration file
/Users/justinmclean/Documents/ApacheFlex4.13released/frameworks/flex-config.xml
[java] Error: Inconsistant lin
Hi Justin,
thanks for that ... couldn't find the time yesterday.
Chris
-Ursprüngliche Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com]
Gesendet: Sonntag, 24. August 2014 04:46
An: dev@flex.apache.org
Betreff: Re: Draft TourDeFlex announcement
Hi,
Raised JIRAs for these
49 matches
Mail list logo
