If you use a custom ROYALE_COMPILER_HOME, like I do (on Windows), then
very few of the build.xml files handle it properly. Most of them ignore
the environment variable and just use ${ROYALE_HOME}/js, as you can see
in what I wrote earlier.
(ROYALE_COMPILER_REPO is not enough, at least on
Right, but how do you create the resource bundles and dynamically load
the locales?
It seems like it's very different in Royale.
On 11/26/2020 1:58 AM, Yishay Weiss wrote:
> In emulation components it’s similar to the Flex syntax. We have seen bugs
> however with the @ annotator syntax in
IIRC, on your local machine, if you clone the repo and run "mvn clean install",
it should allow you to type a response and then that machine should be ok to
use after that.
-Alex
On 11/26/20, 1:46 PM, "Harbs" wrote:
That’s on my local machine. Passing the Dcom option to the ant script
Harbs,
I can send you off the list tomorrow and you can put it to a proper dir ;)
It’s a hack :) You will do that once and forgot about that. Of course if we
are talking about Maven:)
Thanks,
Piotr
On Thu, 26 Nov 2020 at 22:46, Harbs wrote:
> That’s on my local machine. Passing the Dcom
That’s on my local machine. Passing the Dcom option to the ant script doesn’t
help.
How would I manually get the Adobe artifacts on my machine?
> On Nov 26, 2020, at 11:18 PM, Christofer Dutz
> wrote:
>
> I can tell you what’s going on here.
>
> You are building on a system where the Adobe
I can tell you what’s going on here.
You are building on a system where the Adobe artifacts aren’t available in the
maven local repo.
So the mavenizer (AKA maven extension I built to make non maven artifacts
available as Maven artifacts) is kicking in. It expects a user to accept the
license
I don’t get it. I’m getting an endless loop of:
[exec] The Adobe SDK license agreement applies to the Adobe Flash Player
playerglobal.swc. Do you want to install the Adobe Flash Player
playerglobal.swc?
[exec] (In a non-interactive build such as a CI server build,
alternatively to
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
Log in to the server, open a command prompt, change directory to
C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands:
git push
git push origin org.apache.royale.compiler-0.9.8-rc1
You will need your Apache/Github username and 2FA token.
I needed to do git pull on C:\jenkins\workspace\Royale_Release_Step_001 since I
fixed this after step 1...
> On Nov 26, 2020, at 8:10 PM, Harbs wrote:
>
> Any ideas why this is failing?
>
> I’m pretty sure I updated the repo to reference the new released version of
> compiler-build-tools,
Hi,
I count 4 binding votes ;)
congrats!
El jue, 26 nov 2020 a las 13:53, Harbs () escribió:
> The vote passed with 3 binding and one non-binding votes.
>
> Thanks!
> Harbs
>
--
Carlos Rovira
Apache Member & Apache Royale PMC
*Apache Software Foundation*
http://about.me/carlosrovira
Any ideas why this is failing?
I’m pretty sure I updated the repo to reference the new released version of
compiler-build-tools, but it seems to be picking up 1.2.1-SNAPSHOT instead of
1.2.1.
> On Nov 26, 2020, at 7:31 PM, apacheroyal...@gmail.com wrote:
>
> Royale_Release_Step_002 - Build #
Royale_Release_Step_002 - Build # 54 - Still Failing:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/54/
to view the results.
Royale_Release_Step_002 - Build # 53 - Still Failing:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/53/
to view the results.
Royale_Release_Step_002 - Build # 52 - Still Failing:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/52/
to view the results.
Royale_Release_Step_002 - Build # 51 - Still Failing:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/51/
to view the results.
Log in to the server, open a command prompt, change directory to
C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands:
git push
git checkout release/0.9.8
git push -u origin release/0.9.8
You will need your Apache/Github username and 2FA token.
The vote passed with 3 binding and one non-binding votes.
Thanks!
Harbs
And mine:
+1
Package
https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.1/rc1/apache-royale-compiler-build-tools-1.2.1-source-release.zip
Java 1.8
OS: Mac OS X x86_64 10.15.6
Source kit signatures match: y
Source kit builds: y
README is ok: ${readme.ok}
RELEASE_NOTES is ok:
You shouldn’t need to adjust anything, and no, it’s not generated.
I have the following env vars set:
#!/bin/sh
export ROYALE_COMPILER_REPO=/Apache/royale-compiler
export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
export
Are the build.xml files automatically generated from some other files?
Many of them are not seeing the ROYALE_COMPILER_HOME environment variable, so I
have to manually adjust this:
to this:
And there are a lot of files to modify each time I do
21 matches
Mail list logo
