Morning Glory
Document Status | ARCHIVED |
|---|---|
Document Version | 1 |
Last TC Review Date | unknown |
Last TC Review Outcome | unknown |
Frontend
Frameworks
React ^17.0.2
Stripes ^7.1.0
Build tools
Node 12
Yarn 1
Unit test stack
Jest ^26.6.3
RTL ^12.1.2
End-to-end test stack
Cypress ^9.1.1
Backend
Languages
Java 11
Groovy 2
Frameworks
raml-module-builder 34.0.*
vertx 4.3.*
spring 2.6.2
folio-spring-base 3.0.1
Grails 4
Build tools
Maven 3.x
JDK 11
Docker
Gradle
Unit test stack / Build-time integration test stack
JUnit 4 or 5
rest-assured 4
testcontainers 1.15.1
Integration test stack
karate 1.0.1
cucumber-reporting 3.8.0
Infrastructure
Postgresql 12
Elasticsearch 7.10
Kafka
Comments
It's going to be a judgement call that the TC needs to make. IMO it really comes down to whether or not we'd fail a module during the new module tech eval process based on its use of something not on this list.
Could it be worth only specifying the major and minor version of a tool and providing general guidance that the latest patch version be used (unless otherwise specified) rather than trying to keep up with every patch version in this document?
Should S3/minio been added? https://github.com/folio-org/folio-ansible/tree/master/roles/minio-docker
How broad is the scope we are attempting to cover with this list?
For example, would assertion and mocking tools be included in the test stack section?
Quite a few modules use lombok (there are probably lots of other common libraries being used too), would that also be included?