-
Type:
Task
-
Status: Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: 7.0.0 DXP FP86, 7.0.10.12 DXP SP12, 7.0.X, 7.1.10 DXP FP14, 7.1.X, 7.2.10 DXP FP17, 7.2.10.6 DXP SP6, 7.2.X, 7.3.X, Master
-
Component/s: Dev Tools > Gradle Plugins
-
Branch Version/s:7.3.x, 7.2.x, 7.1.x, 7.0.x
-
Backported to Branch:Committed
-
Git Pull Request:
Motivation: the Commerce team was seeing a lot of churn in their build scripts caused by changes in other portal modules.
Solution: create a release api jar that contains the exported packages from each portal jar so developers can replace every dependency with a single line. Developers can use this for their own apps to reduce dependency complexity.
Alternate approach: target platform + BOM with Workspace.
Testing is difficult to do before release, since the release api jar can't be built until modules have been released. We might be able to mock it. Greg will follow up on testing this.
- causes
-
LPS-107580 Trim jar generated by portalArtifactsJar
-
- Closed
-
- relates
-
LPS-121538 release*.api-javadoc.jar does not contain all of the javadocs
- Resolved
-
LPS-116492 api jar should not include unpublished modules
-
- Closed
-