-
Notifications
You must be signed in to change notification settings - Fork 2
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
Inner Classes Attribute Causes Compilation Errors #589
Labels
bug
Something isn't working
Comments
volodya-lombrozo
added a commit
to volodya-lombrozo/jeo-maven-plugin
that referenced
this issue
May 14, 2024
volodya-lombrozo
added a commit
to volodya-lombrozo/jeo-maven-plugin
that referenced
this issue
May 14, 2024
volodya-lombrozo
added a commit
to volodya-lombrozo/jeo-maven-plugin
that referenced
this issue
May 14, 2024
volodya-lombrozo
added a commit
to volodya-lombrozo/jeo-maven-plugin
that referenced
this issue
May 14, 2024
volodya-lombrozo
added a commit
to volodya-lombrozo/jeo-maven-plugin
that referenced
this issue
May 14, 2024
volodya-lombrozo
added a commit
to volodya-lombrozo/jeo-maven-plugin
that referenced
this issue
May 14, 2024
This was referenced May 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Despite that bytecode attributes are optional for bytecode execution, the absence of
InnerClasses
attributes causes compilation errors. I runspring-fat
integration test inopeo-manen-plugin
and faced with the following exception:The content of
FactorialApplicationTest.java
is following:As you can see it uses
SpringBootTest.WebEnvironment.RANDOM_PORT
class. Actually it is theSpringBootTest
class with the inner enumWebEnvironment
. If I replaceSpringBootTest
which we disassembled/assembled with the original one (from jar), the compilation works correctly without any errors.So I apply bytecode representation of failed
SpringBootTest
class and an original one:failed.txt
working.txt
As you can see, the main difference in
InnerClasses
attributes. So most probably it is a cause of the bug.The text was updated successfully, but these errors were encountered: