Log in to the server, open a command prompt, change directory to
C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands:
git push
You will need your Apache/Github username and 2FA token.
Log in to the server, open a command prompt, change directory to
C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands:
git push
git checkout release/0.9.9
git push -u origin refs/heads/release/0.9.9
You will need your Apache/Github username and 2FA token.
We may have to appeal to Carlos for instructions.
On Sun, Mar 6, 2022 at 8:24 PM Maria Jose Esteve wrote:
> Hi,
> I have not found explicit instructions for upgrading TDJ, but I have
> deduced from the upgrade instructions on the royale website [1] that you
> manually upgrade with a working
Hi,
When compiling the TDJ I noticed that the Jewel ResponsiveSize bead has
"stopped working" and the Apache logo, which is displayed on the main page, is
displayed with its original dimensions (very large)
I said "stopped working" because the TDJ displayed on the official website
seems to work
Hi,
I have not found explicit instructions for upgrading TDJ, but I have deduced
from the upgrade instructions on the royale website [1] that you manually
upgrade with a working release:
- I compiled TDJ (Maven build).
- I updated the "tourdejewel" folder in the "royale-website/tree/asf-site"
I don't know, but I will look into it today (local time) and see if I can
figure it out.
On Mon, Mar 7, 2022 at 8:19 AM Yishay Weiss wrote:
> ASDoc is failing which is blocking the build.
>
> Greg, I have found out commit 63c94366f533bc1384401cdd6ba1f20057b4d999
> breaks the ASDoc example,
ASDoc is failing which is blocking the build.
Greg, I have found out commit 63c94366f533bc1384401cdd6ba1f20057b4d999 breaks
the ASDoc example, specifically the following line:
import mx.events.ResourceEvent; ResourceEvent;
Do you (or anyone else) have a hunch why that may be?
Following the instructions [1], I access wp-admin but I have no user. I have
tried to access with my apache user (hie...@apache.org), with the github user
(hie...@github.com), with the account associated with the regisitro of royale
(mjest...@iest.com) but I imagine that this will have a
Royale_Release_Step_011 - Build # 24 - Failure:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/24/
to view the results.
Log in to the server, open a command prompt, change directory to
C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands:
git push
git push origin org.apache.royale.framework-0.9.9-rc2
You will need your Apache/Github username and 2FA token.
Log in to the server, open a command prompt, change directory to
C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands:
git push
You will need your Apache/Github username and 2FA token.
Log in to the server, open a command prompt, change directory to
C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands:
git push
git checkout release/0.9.9
git push -u origin refs/heads/release/0.9.9
You will need your Apache/Github username and 2FA token.
I had the following in my settings.xml, not sure why it was there to begin
with. Sorry for the noise.
royale-release
0.9.8
From: Yishay
13 matches
Mail list logo
