[STRIPES-503] CONSIDER moving all Stripes libraries into a monorepo - FOLIO Issue Tracker

XML

Word

Printable

Details

Type: Task
Status: Closed (View Workflow)
Priority: P3
Resolution: Won't Do
Affects Version/s: None
Fix Version/s: None
Component/s: None
Labels:
- RFC
- build-release

Template:

Description

For some time, the idea has been floating around that it might be a good idea to move all the most fundamental Stripes libraries into a monorepo. I am still not convinced by a long way, but I think it's important to give this due thought – especially, now, during the post-Madrid period where other things are up in the air (switching away from yarn link to stripes-cli, establishing testing frameworks, etc.)

Here are some useful pieces advocating monorepos – and bear in mind that they are by their nature unbalanced:

TestRail: Results

Attachments

Issue Links

is blocked by

STRIPES-544 Understand all the stripes-building scenarios, and their implications for dependency management

Closed

relates to

STRIPES-543 Consider "stripes-framework" to wrap "stripes-*" dependencies

Closed

STRIPES-588 Stripes 2.0 roll-out analysis

Closed

Activity

People

Assignee:: Mike Taylor

Reporter:: Mike Taylor

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Dates

Created:: 07/Feb/18 3:01 PM

Updated:: 09/Jul/19 9:38 PM

Resolved:: 09/Jul/19 9:38 PM

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

CONSIDER moving all Stripes libraries into a monorepo