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
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:
Those packages should be placed in
./zip/build/packagesdirectory. 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