royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Piotr Zarzycki <piotrzarzyck...@gmail.com>
Subject Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1
Date Mon, 08 Jan 2018 22:05:04 GMT
It would be really great if someone from PMCs who never touch Maven tried
test some application. That would be really helpful.

Thanks, Piotr

2018-01-08 23:00 GMT+01:00 Piotr Zarzycki <piotrzarzycki21@gmail.com>:

> Today I had time to test only Maven artifacts. Tomorrow hopefully will try
> ANT and building stuff. Just wanted to share with you guys instruction how
> to test Maven artifacts. My tests went well. I have build three
> applications 2 MDL and one with Basic components - Each run without the
> problem. :)
>
> Instruction:
>
> 1) Pickup some example or whatever application you have which have pom.xml
> - It can be something from our Examples
> 2) Remove -SNAPSHOT from pom. Place everywhere 0.9.0 version.
> 3) Place following file template to the folder with your pom.xml [1]
> 4) Type in console mvn clean install -s settings-template.xml
> 5) Run your application from location target/javascript/bin/js-debug
>
> All dependencies should be downloaded. If you will be able to run
> application one part of the testing is done. :)
>
> [1] https://paste.apache.org/phar
>
> Thanks, Piotr
>
>
> 2018-01-08 18:16 GMT+01:00 Alex Harui <aharui@adobe.com.invalid>:
>
>>
>>
>> On 1/8/18, 12:52 AM, "Piotr Zarzycki" <piotrzarzycki21@gmail.com> wrote:
>>
>> >Placing discussion here.
>> >
>> >Understand, so the problem actually now is in Develop, but in 0.9.0
>> >doesn't
>> >exists, cause script simply invoke creation exact what we have in
>> >"develop"
>> >branch. Once we finish release, merge released branched to develop, we
>> can
>> >simply make correction manually for the future release.
>>
>> Maven "automatically" does lots of things (makes lots of assumptions).  It
>> assumes that when you create a release branch that it should automatically
>> update the develop branch to the next release version (you can set what
>> that version is, but it defaults to updating the z in x.y.z version
>> formats).  Then at that point, the release branch still has the older
>> snapshot versions.  Another Maven release step removes the "-SNAPSHOT"
>> from the versions and does a quick check to see that there are no
>> remaining -SNAPSHOT dependencies.  However, Maven doesn't seem to
>> understand string substitution variables so we have to fix those up in the
>> Ant script that is calling all of these Maven steps.  Then Maven creates
>> and stages the artifacts and then updates the release branch to the next
>> version as well in order to make the merge work cleanly.
>>
>> It might be that we can use the distribution profile when creating the
>> branches and then Maven should find and update the version in that pom.
>> Maybe I will try that in a future release.
>>
>> The key is with this Ant script, we can hopefully automatically do
>> whatever manual steps are required to make everything work so releases
>> don't require as much human intervention.
>>
>> Thanks,
>> -Alex
>> >
>> >
>> >2018-01-08 9:28 GMT+01:00 Piotr Zarzycki <piotrzarzycki21@gmail.com>:
>> >
>> >> Hi Alex,
>> >>
>> >> My concerns about that is actually been in thread "Royale Release
>> >>Process
>> >> Philosophy". Feel free to respond here. :)
>> >>
>> >> Thanks, Piotr
>> >>
>> >>
>> >> 2018-01-08 9:14 GMT+01:00 Alex Harui <aharui@adobe.com.invalid>:
>> >>
>> >>> This is the discussion thread.
>> >>>
>> >>> The Maven artifacts are staged here:
>> >>>
>> >>>https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Freposit
>> >>>ory.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale
>> -1009&data=02%7
>> >>>C01%7Caharui%40adobe.com%7Ca178dcb9a51f45c6250008d556770f
>> f3%7Cfa7b1b5a7b
>> >>>34438794aed2c178decee1%7C0%7C0%7C636509991723063403&sdata
>> =7B5hROFXM6a%2B
>> >>>vwhhrdw8uselbRlRXvjhK%2BKomVjRlNY%3D&reserved=0
>> >>>
>> >>>
>> >>> Thanks,
>> >>> Alex Harui
>> >>>
>> >>>
>> >>
>> >>
>> >> --
>> >>
>> >> Piotr Zarzycki
>> >>
>> >> Patreon:
>> >>*https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fwww.pat
>> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
>> %7Ca178dcb9a51f
>> >>45c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6365099
>> >>91723063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S5z8%
>> 2Febivq8qKE%3D&reserv
>> >>ed=0
>> >>
>> >><https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fwww.pat
>> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
>> %7Ca178dcb9a51f
>> >>45c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6365099
>> >>91723063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S5z8%
>> 2Febivq8qKE%3D&reserv
>> >>ed=0>*
>> >>
>> >
>> >
>> >
>> >--
>> >
>> >Piotr Zarzycki
>> >
>> >Patreon:
>> >*https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fwww.patr
>> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7
>> Ca178dcb9a51f45
>> >c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%
>> 7C0%7C6365099917
>> >23063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S5z8%
>> 2Febivq8qKE%3D&reserved=0
>> ><https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fwww.patr
>> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7
>> Ca178dcb9a51f45
>> >c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%
>> 7C0%7C6365099917
>> >23063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S5z8%
>> 2Febivq8qKE%3D&reserved=0
>> >>*
>>
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message