Details
-
Sub-task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
-
None
Description
Get an overview of all Maven profiles we have in the core codebase (platform, platform-ee, webapp). Understand what they are used for. Remove those that are not necessary.
For example, with CAM-11970 we can probably delete the distro, distro-ce, etc. profiles as we no longer need to run them independently.
Idea for restructuring:
- There are no profiles that are activated by default
- Without profiles, all artifacts are built (this is also important for release builds that need to update the POM versions); unit tests are executed, integration tests are not executed
- There are profiles to control which tests are executed
- Which integration tests
- Which app server
- Which database
- There are profiles for convenience to build only some of the artifacts (e.g. only the distros, only the engine, only spring boot, etc.)
- All profiles are documented in the project readme
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- is related to
-
CAM-11964 Spring Boot Starter QA parent POM references are not updated during release
-
- Closed
-