You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to my analysis in codehaus-plexus/plexus-compiler#347 (comment), Sisu silently swallows errors caused by UnsupportedClassVersionError. Projects using Sisu Inject cannot react to such problems, because they have no way to find out that anything went wrong. The exception is caught and logged to the debug channel:
The only way to see anything on the console is MAVEN_OPTS=-Dsisu.debug, but that only helps in the analysis, not in fixing the problem.
Ironically, the ASM class visitor parsing the target class as such would be able to do so, given that the internal ASM version of Sisu can read the corresponding class file. The UnsupportedClassVersionError does not come from parsing the class, but from trying to load it, which I am not sure is even necessary at this point. Even if it is, consuming projects should have a way to find out about any problems occurring in Sisu and be able to handle them according to their own needs, e.g. by issuing a comprehensive error, log a warning or whatever.
The text was updated successfully, but these errors were encountered:
Relates to codehaus-plexus/plexus-compiler#347.
According to my analysis in codehaus-plexus/plexus-compiler#347 (comment), Sisu silently swallows errors caused by
UnsupportedClassVersionError
. Projects using Sisu Inject cannot react to such problems, because they have no way to find out that anything went wrong. The exception is caught and logged to the debug channel:https://github.com/eclipse/sisu.inject/blob/550bd96afa244d22ea0fc84bef5d9b0a356bac25/org.eclipse.sisu.inject/src/main/java/org/eclipse/sisu/space/SpaceScanner.java#L113-L116
The only way to see anything on the console is
MAVEN_OPTS=-Dsisu.debug
, but that only helps in the analysis, not in fixing the problem.Ironically, the ASM class visitor parsing the target class as such would be able to do so, given that the internal ASM version of Sisu can read the corresponding class file. The
UnsupportedClassVersionError
does not come from parsing the class, but from trying to load it, which I am not sure is even necessary at this point. Even if it is, consuming projects should have a way to find out about any problems occurring in Sisu and be able to handle them according to their own needs, e.g. by issuing a comprehensive error, log a warning or whatever.The text was updated successfully, but these errors were encountered: