Specifically, will submit a form while will not.
This is a breaking change to any ImageButton inside a Form.
> On Jul 12, 2020, at 5:28 PM, Harbs wrote:
>
> Why did you switch to input?
>
> IIRC, there are behavioral differences between button and input.
>
>> On Jul 12, 2020, at 5:12 PM,
Why did you switch to input?
IIRC, there are behavioral differences between button and input.
> On Jul 12, 2020, at 5:12 PM, carlosrov...@apache.org wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> carlosrovira pushed a commit to branch develop
> in repository
Hi Andrew,
I see the topics perfect. Just a question to help me to understand the big
picture. About timing, how much time we have for all sessions (global and
individual)? That seems to me long play and don't know if is the expected.
I can help with points 2 and 4 as you said. If you want to
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.
Royale_Release_Step_002 - Build # 48 - Failure:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/48/
to view the results.
I’m not sure what’s supposed to be happening here. I thought that as part of
step 1, the release/0.9.8 branch gets the poms sans the -SNAPSHOT, but they
still say 0.9.8-SNAPSHOT
I tried removing -SNAPSHOT manually, but that didn’t help either.
With -SNAPSHOT, I get an error:
[ERROR] Failed
Royale_Release_Step_002 - Build # 49 - Still Failing:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/49/
to view the results.
Royale_Release_Step_002 - Build # 50 - Still Failing:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/50/
to view the results.
Or in other words, how does maven-release-plugin work?
> On Jul 12, 2020, at 10:46 PM, Harbs wrote:
>
> I’m not sure what’s supposed to be happening here. I thought that as part of
> step 1, the release/0.9.8 branch gets the poms sans the -SNAPSHOT, but they
> still say 0.9.8-SNAPSHOT
>
> I
Any thoughts on a short, evocative title for the track? How about "Apache
Royale: Application Builder"?
On Sun, Jul 12, 2020 at 7:28 AM Carlos Rovira
wrote:
> Hi Andrew,
>
> I see the topics perfect. Just a question to help me to understand the big
> picture. About timing, how much time we have
Even BindingUtils didn't show off, RemoteObject from mx seems to be there.
The second option is enough.
"We hopefully will separate MX in libraries and will create a "jewel" config
that adds RPC and maybe others that could be needed."
That would be great.
Carlos Rovira escreveu no dia sexta,
You will have to release compiler-build-tools 1.2.1 first. A change was made
there to help with reproducible binaries. Yishay had to release
compiler-build-tools before 0.9.7.
HTH,
-Alex
On 7/12/20, 12:47 PM, "Harbs" wrote:
Or in other words, how does maven-release-plugin work?
Oh. Thanks. I’ll do that then...
> On Jul 13, 2020, at 7:22 AM, Alex Harui wrote:
>
> You will have to release compiler-build-tools 1.2.1 first. A change was made
> there to help with reproducible binaries. Yishay had to release
> compiler-build-tools before 0.9.7.
>
> HTH,
> -Alex
>
>
Log in to the server, open a command prompt, change directory to
C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the
following commands:
git push --set-upstream origin develop
git push origin org.apache.royale.compiler-build-tools-1.2.1-rc1
You will need your
14 matches
Mail list logo
