Skip to end of banner
Go to start of banner

DR-000019 - Spring Way Equivalent of Edge-common

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Submitted Date

 

Approved Dateyyyy-mm-dd
StatusACCEPTED
ImpactHIGH/MEDIUM/LOW

 

Overrides/Supersedes 

This decision was migrated from the Tech Leads Decision Log as part of a consolidation process.  The original decision record can be found here.

RFC 

N/A

Stakeholders

@mention individual(s) who has vested interest in the DR. This helps us to identify who needs to be aware of the decision

Contributors

List individual(s) sposnoring/advocating for the decision

Approvers

This decision was made by the Tech Leads group prior to the adoption of current decision making processes within the FOLIO project.

Background/Context

Explain the need that triggered the need for making a decision

Assumptions

N/A

Constraints

N/A

Rationale

N/A

Decision

Create a spring way equivalent/port of edge-common, and pull share/common classes/utils into an edge-api-utils library which can be used from both edge-common and the spring way equivalent (edge-common-spring). 

Implications

  • Pros
    • N/A
  • Cons
    • N/A

Other Related Resources

  • No labels