-
Notifications
You must be signed in to change notification settings - Fork 246
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
feat(pacmak/java): isolate maven repositories #1709
Conversation
When preparing a Java package using Maven, `jsii-pacmak` now configures a dedicated `localRepository` for it's own use. This prevents artifacts cached from previous builds as well as local build artifacts to possibly interfere with the compilation process. This has the side-effect to force a re-download of all dependencies on each build (except those that are generated as part of the same build), which results in a performance degradation. It should be possible to make the local repository location user-configurable so this impact can be mitigated on a case-by-case basis.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
@@ -1,3 +1,4 @@ | |||
.m2 |
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.
Why oh why not in a tempdir somewhere?
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.
Because local iterations will be much faster for not re-downloading things every single time. You can nuke this directory when you need it...
Additionally, I don't like dropping temporary directories somewhere where I will not be able to clean them up. I consider this is loitering.
Thank you for contributing! ❤️ I will now look into making sure the PR is up-to-date, then proceed to try and merge it! |
Merging (with squash)... |
When preparing a Java package using Maven,
jsii-pacmak
now configuresa dedicated
localRepository
for its own use. This prevents artifactscached from previous builds as well as local build artifacts to possibly
interfere with the compilation process.
This has the side-effect to force a re-download of all dependencies on
each build (except those that are generated as part of the same build),
which results in a performance degradation. It should be possible to
make the local repository location user-configurable so this impact can
be mitigated on a case-by-case basis.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.