-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved build process #1566
Improved build process #1566
Conversation
64464ea
to
1449005
Compare
35f4f81
to
a47e49b
Compare
a47e49b
to
7278bcd
Compare
@jonathonherbert thanks for that. Looks like it's not bundling the JSPM deps... |
Fixed this morning :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested:
- V2 client (fronts edits, proof an edition)
- V1 client (config, treats)
- Breaking news (sent notification)
Bloomin' lovely. A few non-blocking comments.
import sbt.Resolver | ||
|
||
debianPackageDependencies := Seq("openjdk-8-jre-headless") | ||
debianPackageDependencies := Seq("java11-runtime-headless") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just FMI as I'm sure it is – why is this necessary? Doesn't the AMI provide a Java runtime?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically it's not necessary - but it's good practise when building a java-based DEB to have a generic JRE dependency
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Andy is correct that technically it isn't necessary. But if this line is present, it needs to be correct. AFAIK if you left this as openjdk-8-jre-headless the package would fail to install.
What's changed?
Implementation notes
None
Checklist
Things that still need checking:
There are errors being reported of files not found during the frontend v2 integration tests. These do not fail the tests and I have a suspicion that they relate to the Webpack->Vite migration but not sure.[FIXED in https://github.com/Remove red ink in integration test runs #1568]General
Client