Skip to content
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

chore: fix for local dev rebuilding ftl-runtime.jar on every run #1049

Merged
merged 1 commit into from
Mar 8, 2024

Conversation

alecthomas
Copy link
Collaborator

This was occurring because frontend/local.go was calling npm install explicitly on every run, resulting in changes to the frontend that invalidated some of the dependencies of the JAR file.

The fix is to use bit to build the frontend as well, resulting in its dependency cache being correct.

This was occurring because frontend/local.go was calling `npm install`
explicitly on every run, resulting in changes to the frontend that
invalidated some of the dependencies of the JAR file.

The fix is to use `bit` to build the frontend as well, resulting in its
dependency cache being correct.
@alecthomas alecthomas mentioned this pull request Mar 8, 2024
@alecthomas alecthomas merged commit 759b2f3 into main Mar 8, 2024
12 checks passed
@alecthomas alecthomas deleted the aat/fix-dev-jar-build branch March 8, 2024 05:27
@@ -114,7 +114,7 @@ kotlin-runtime/external-module-template.zip: kotlin-runtime/external-module-temp
# TODO: Figure out how to make Maven build completely offline. Bizarrely "-o" does not do this.
build:
mvn -B -N install
mvn -B -pl :ftl-runtime install
mvn -Dmaven.test.skip=true -B -pl :ftl-runtime install
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's so strange to me that the default is to run tests when building. mvn is weird.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely agree, super weird...and irritating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants