[SERVER-49357] Re-organize handling of license files across community and enterprise Created: 08/Jul/20  Updated: 27/Oct/23  Resolved: 27/Oct/23

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-47277 Remove support for non-hygienic builds Closed
Assigned Teams:
Server Development Platform
Backwards Compatibility: Fully Compatible
Sprint: Dev Platform 2020-08-10
Participants:

 Description   

The handling and placement of various license files, third party notices, etc is currently fairly confusing. Some are in the top-level of the community repo, some are (duplicated) in a distsrc directory. Handing for the license file in community is conditioned on the presence of the enterprise module. With SERVER-47277 completed, the organization and handling of these files can be improved and simplified.



 Comments   
Comment by Ryan Egesdahl (Inactive) [ 21/Jul/20 ]

I think there's a larger question to be answered here - how do we include modules into the codebase but make any modifications the responsibility of the main tree? I have some ideas on that one based on how Python modules work. Perhaps we should discuss this more.

Generated at Thu Feb 08 05:19:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.