[MCOMPILER-561] - Add new rebuild detection for bytecode changes #219
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jorsol
force-pushed
the
MCOMPILER-561
branch
from
d9794ba
to
e7bea12
Compare
Signed-off-by: Jorge Solórzano <jorsol@gmail.com>
jorsol
force-pushed
the
MCOMPILER-561
branch
from
e7bea12
to
26d5ea0
Compare
| Map<Path, JavaClassfileVersion> pathVersionMap = walk.filter(file -> "class" | ||
| .equals(FileUtils.extension(file.getFileName().toString()))) | ||
| .limit(MAX_FILE_WALK_LIMIT) | ||
| .collect(Collectors.toMap(Function.identity(), JavaClassfileVersion::of)); |
There was a problem hiding this comment.
Maybe instead of checking bytecode of classes we can store current JDK version used to compile and next time verify if is the same.
We also should add an IT for multi-releases compilation.
There was a problem hiding this comment.
That's a really good approach, I'm making complex bytecode checks when simply storing the current JDK, and verifying next time would do the trick.
Closing this in favor of that approach (will open a new PR later).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TODO: check the scenario where two executions compiles different bytecode on the same output (MCOMPILER-275_separate-moduleinfo).
Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
[MCOMPILER-XXX] - Fixes bug in ApproximateQuantiles,where you replace
MCOMPILER-XXXwith the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the
commit message.
mvn clean verifyto make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
mvn -Prun-its clean verify).If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.