Thanks Om!
That's very useful, I'll try to use that as a guide and unify with website.
I'll be posting soon the data everyone need to post to be added with the
corresponding sizes and additional info.
El mié., 24 jul. 2019 a las 21:55, OmPrakash Muppirala (<
bigosma...@gmail.com>) escribió:
> If
Hi Greg,
ok! I thought there was something more involved. About understanding better
how things work in maven plugin and know the reasons I think it could be
good to ask Chris Dutz about it, since he can give us the clues about all
of that.
Thanks!
El mié., 24 jul. 2019 a las 22:50, Greg Dove
Hi Carlos,
Just to clarify: I had wondered whether there were inconsistencies in the
framework so I checked more on that before adding my previous post in this
thread.
It seems that
true was
achieving a similar result to using 'provided' for the (inter)dependencies
inside each framework project, s
If we can mimic how the Flex showcase works, that would be a good starting
point.
http://flex.apache.org/community-showcase.html
Thanks,
Om
On Wed, Jul 24, 2019, 9:51 AM Yishay Weiss wrote:
> Sounds good, thanks.
>
>
>
>
> From: Carlos Rovira
> Sent: Wednesday
Hi,
if I understand correctly, both "runtime" and "provided" are right now
equal for the compiler, right? I'm ok to understand conceptually
"runtime" and "provided" as Greg says. At least for now, although if we can
inform the compiler to differentiate as well would be great.
In the other hand, f
Sounds good, thanks.
From: Carlos Rovira
Sent: Wednesday, July 24, 2019 7:35:54 PM
To: dev@royale.apache.org
Subject: Re: Website - create Showcase section
Hi Yishay,
good to know! ok we can start posting.
In our case, I was thinking yesterday in make white b
Hi Yishay,
good to know! ok we can start posting.
In our case, I was thinking yesterday in make white brand version of our
app to avoid conflicts with our clients, since the important thing is to
showcase and put screenshots available to browse.
For All apps we'll need some screenshots in concrete
Btw. Once I finish steps - Can I publish artefacts and start RC1 vote on
dev ? Does anything I should know at the end which is not mention ?
śr., 24 lip 2019 o 17:59 Piotr Zarzycki
napisał(a):
> By compare to dypedefs step - do you mean that I should look into Jenkins
> configuration of that st
By compare to dypedefs step - do you mean that I should look into Jenkins
configuration of that steps or something else ?
śr., 24 lip 2019 o 17:56 Alex Harui napisał(a):
> Hi Piotr,
>
> You can compare the output from previous builds and also the typedefs
> build configuration because both succe
Hi Piotr,
You can compare the output from previous builds and also the typedefs build
configuration because both successfully used the date format. The Java
documentation says that "Z" is for timezone. It shouldn't matter which one you
use, but in the typedefs you hadn't specified one at all.
Hi Alex,
I was able to overcome issue with date for typedefs. Instruction there is
saying:
MM/dd/yy HH:mm Z
> Where MM/dd/yy is the US-formatted date and HH:MM is a faked time to
> encode the release version such as:
> 2/10/19 9:06 -0800
I have typed 7/24/2019 HH (I don't remember what was that
>From the royale-asjs repo:
1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.6
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 releasesteps.xml Re
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.6-rc1
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_010 and run the following commands:
git push
git push origin org.apache.royale.framework-0.9.6-rc1
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.6
git push -u origin release/0.9.6
You will need your Apache/Github username and 2FA token.
>From the royale-typedefs repo:
1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.6
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 releasesteps.xm
Royale_Release_Step_007 - Build # 34 - Failure:
Check console output at
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_007/34/
to view the results.
Log in to the server, open a command prompt, change directory to
C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands:
git push
git push origin org.apache.royale.typedefs-0.9.6-rc1
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_005a_If_Utils and run the following
commands:
git push
You will need your Apache/Github username and 2FA token.
Royale_Release_Step_005a_If_Utils - Build # 23 - Still Failing:
Check console output at
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005a_If_Utils/23/
to view the results.
Royale_Release_Step_005a_If_Utils - Build # 22 - Failure:
Check console output at
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005a_If_Utils/22/
to view the results.
23 matches
Mail list logo
