feat(#6): copy integration test from jeo repository #7
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
|
The original discussion: objectionary/jeo-maven-plugin#264 |
|
@yegor256 Could you take a look, please? |
|
@yegor256 reminder |
|
@rultor merge |
@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here |
@volodya-lombrozo Done! FYI, the full log is here (took me 2min) |
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.
I copied the integration tests that we created to define our goals (what we want to get from bytecode transformation in order to provide simple inlining optimization.)
Closes: #6.
PR-Codex overview
Detailed summary
jucsinpom.xmlfor testing purposes.Application,A, andBin thecom.examplepackage.Application,A, andBin thecom.examplepackage.package-infoandTrasformationPacksTestin theitpackage.