Gradle Builds

[devzbysiu]

Is your feature request related to a problem? Please describe.
In a process of simplifying AET deployment and local development, we want to introduce gradle builds which will replace maven in the future. It will make implementing automation easier.

Describe the solution you'd like
The build should create zip packages with:

• compiled bundles
• OSGi configs
• features
• report
• sample-site

Those packages should be placed in ./zip/build/packages directory. Those will be then used by the release workflow to create the release draft.

It should take versioning into account and allow to release (bump versions) AETs.

It should be able to run checks like automated tests and RAT checks (checking licenses of files). When there is a file not matching Apache 2.0, it should fail.

It should allow creating code coverage which will be then used by CI workflow.

Describe alternatives you've considered
N/A

Additional context
N/A

[devzbysiu]

This is finished developer-wise and was merged here: #617. Right now it can be tested on local environment only. Contact me in case you want to get into it.

The next steps are to:

• finish Move to Github Actions #631 and create a draft release
• deploy the release to internal env for tests

But before that, we need to take care of #624

[devzbysiu]

This #624 is done. This task is ready for QA

[pilarskie]

Test comment.

[devzbysiu]

Fix of accessibility comparator is here: https://github.com/wttech/aet/pull/640/files

[devzbysiu]

Accessibility comparator is working now

[pilarskie]

Accessibility comparator tested and accepted.

[pilarskie]

Tested and accepted.