I agree. All signs are green. The license issues have been fixed and
no further ones have been raised. The RSL issue was fixed. The
consensus on the Installer issue is that it's minor, with a workaround
and will be short-lived.
I'll start my engines (= lot's of morning coffee) and turn out the RC
I have completed all the tests I normally run before voting. I’m good to
go for this release.
-Alex
On 1/22/15, 9:13 AM, "Alex Harui" wrote:
>
>
>On 1/22/15, 7:41 AM, "Erik de Bruin" wrote:
>
>>Status:
>>
>>1) License issue: Alex took care of this, right?
>
>IMO, even if it isn’t perfect, it
> Do you have any idea why this is happening?
Yes, and a fix is already submitted to the Installer repo.
I will make a note in the announcement that, until a new Installer is
released (which Om already told us he'll take care of), changing the
locale at any point after the main screen may give p
Hi,
> -Portions of SAxon9 are derived from classes placed in the
> +Portions of Saxon9 are derived from classes placed in the
"SAxon9" was what was in their notice file but not a big deal either way.
Justin
Do you have any idea why this is happening?
On Jan 23, 2015, at 1:35 AM, Justin Mclean wrote:
> HI,
>
>> Did you prove that 4.13 installs correctly with the exact same steps?
>
> Yes 4.13 has no issues, this only effects 4.14.
>
> Justin
HI,
> Did you prove that 4.13 installs correctly with the exact same steps?
Yes 4.13 has no issues, this only effects 4.14.
Justin
I think it’s somewhere between a minor and major issue (probably leaning
towards minor), but either way, it seems like an installer issue, so I don’t
see why it should be a blocker for the 4.14 release.
On Jan 23, 2015, at 1:14 AM, Justin Mclean wrote:
> Hi,
>
>> IMO, any scenario where chang
On 1/22/15, 3:14 PM, "Justin Mclean" wrote:
>Hi,
>
>> IMO, any scenario where changing the locale isn’t the first thing you do
>> doesn’t concern me for the release of SDK 4.14.0.
>
>Given that's it likely that the majority of users change the locale, I
>think we need to carefully consider this
Hi,
> IMO, any scenario where changing the locale isn’t the first thing you do
> doesn’t concern me for the release of SDK 4.14.0.
Given that's it likely that the majority of users change the locale, I think we
need to carefully consider this before releasing. What do other PMC member
think?
J
IMO, any scenario where changing the locale isn’t the first thing you do
doesn’t concern me for the release of SDK 4.14.0.
-Alex
On 1/22/15, 2:58 PM, "Justin Mclean" wrote:
>Hi,
>
>We have (IMO) a fairly serious issue with the installer and 4.14.
>
>To reproduce do this:
>1. Run installer
>2. S
Hi,
Just noticed something odd in an installed SDK we have:
./frameworks/locale/de_DE/playerglobal_rb.swc
./frameworks/locale/en_US/playerglobal_rb.swc
./frameworks/locale/fr_FR/playerglobal_rb.swc
./frameworks/locale/ja_JP/playerglobal_rb.swc
./frameworks/locale/ru_RU/playerglobal_rb.swc
./frame
Hi,
We have (IMO) a fairly serious issue with the installer and 4.14.
To reproduce do this:
1. Run installer
2. Select dev build and select 4.14 RC hit next
3. Select directory and hit next
4. Change locale
5. Check all licenses (shows wrong list for 4.14) and hit next
6. Installation completes
flex-sdk_release-candidate - Build #81 - Failure
Changes since last build:
[erik] Fix RSLs 'versioning' issue in *-config.xml files
For more information, check the console output at
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/81/.
On 1/22/15, 7:41 AM, "Erik de Bruin" wrote:
>Status:
>
>1) License issue: Alex took care of this, right?
IMO, even if it isn’t perfect, it is good enough.
>
>I'll give it another day or so, then I'll assume everyone (esp. PMC
>members!) checked the nightlies and concluded that the above issue
> OK, good to know. I think there may be a cases where, if someone doesn’t
> run frameworks-rsls in the same calendar day they run installer.xml it
> will still not do the right thing, but that is probably not worth
> addressing.
I knew you were gonna say that!
I think we have reduced an already
OK, good to know. I think there may be a cases where, if someone doesn’t
run frameworks-rsls in the same calendar day they run installer.xml it
will still not do the right thing, but that is probably not worth
addressing.
On 1/22/15, 6:51 AM, "Erik de Bruin" wrote:
>I tested this. The token tha
Status:
1) License issue: Alex took care of this, right?
2) locale "issue": will be fixed in next installer release, and it is
not really a blocker...
3) RSL: 'installer.xml' has been fixed, it now correctly replaces
tokens when building an IDE-compatible SDK from a source package?
I'll give it a
Spark (Default)
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/4-14-0-Nightly-build-79-width-height-bug-in-BusyIndicatorSkin-as-tp44488p44514.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
I tested this. The token that is replaced with the current date in the
new code is not present in the binary release. Ergo, nothing is
replaced when 'installer.xml' is run on a binary release...
EdB
On Thu, Jan 22, 2015 at 3:47 PM, Alex Harui wrote:
> I looked at the commit, and while I would
I looked at the commit, and while I would expect it work for the scenario
in question, I’m worried it will break the main install.
The issue is that the RSLs are stamped with a date and time. The main
install is going to run at a much later date and time. It may be more of
a question of parsing
>> vote +1 whether Erik fixes it or not.
>
> Pretty sure I have a fix, checking it now on a clean source package.
The fix is in ;-)
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
On 22/01/15 14:10, Alex Harui wrote:
Except:
>a) Linux users can't use the binary to install
Has anyone tried it? Linux users and anyone not wanting to use the
Installer should be able to take the convenience binary package, expand it
into a folder and run “ant -f installer.xml” and everything
> vote +1 whether Erik fixes it or not.
Pretty sure I have a fix, checking it now on a clean source package.
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
On 1/22/15, 4:24 AM, "Justin Mclean" wrote:
>Hi,
>
>
>> We use the sdk binary package to do our app development and the RSLs
>>are already built in it.
>
>Except:
>a) Linux users can't use the binary to install
Has anyone tried it? Linux users and anyone not wanting to use the
Installer shoul
> These files are ignored by version control.
Not true. My bad. Looking further...
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Ah, I think I have it. Justin probably ran
'ide/flashbuilder/makeApacheFlexForIDE.sh' as the final step of the
4.13 style IDE preparation. This copies the *-config.xml files from
'ide/flashbuilder/config' over the config files in 'frameworks/'.
These files are ignored by version control. I'm now l
> For instance if you followed the READEME instructions in 4.13 you get:
Would you mind listing the steps you took for the 4.13 build, like you
did for 4.14?
Thanks,
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
By binaries, I mean the sdk binaries [1]. We don't use the installer and we
don't use the IDE scripts. I was under the impression the linux users could
use the sdk binaries with just the standard setup.
[1] http://flex.apache.org/download-binaries.html
-Mark
-Original Message-
From
> So basically the README instructions are incorrect. How would they need to
> change in order to not have this issue?
I'd say the scripts are incorrect. I can look into it, if you're not
doing that already?
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I
Hi,
> Installer.xml is probably expecting some properties to match up. It was
> designed to work with the binary package generated in the same run that
> creates the source package.
So basically the README instructions are incorrect. How would they need to
change in order to not have this issue
Hi,
> We use the sdk binary package to do our app development and the RSLs are
> already built in it.
Except:
a) Linux users can't use the binary to install
b) Apache projects release source not binaries
But despite that the PMC can vote on a RC as they see fit (as long as it
follows Apache r
We use the sdk binary package to do our app development and the RSLs are
already built in it. I would say it's not a blocker for this release, but
would be good to fix before the next release.
-Mark
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Thursday, January
Thanks for the ideas.
verbose was already true.
if I set haltonfailure to true, it won't even produce a report for a
test that throws an error.
I just realised it: I didn't have flash player debugger for IE (only
for the other browsers), which was the browser it launched the tests
in. Now that I
33 matches
Mail list logo
