M2 in ibiblio nor in JBoss repository. Could not resolve dependencies for project com. Solution to fix your maven build:. Now I'm getting the problem on another abstract class If so, it is obviously more likely to be an AJ bug than a VM issue. 
| Uploader: | Meztilar |
| Date Added: | 20 March 2012 |
| File Size: | 68.79 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 44511 |
| Price: | Free* [*Free Regsitration Required] |
If so, it is obviously more likely to be an AJ bug than a VM issue.
I can possibly imagine moving from the 1. If you don't need this exact version of aspectjrt then try changing it to 1. Prior to doing this, I was receiving warnings in the maven build as follows: Things were all fine with this project in the past though I'm still looking at things closer.
Search everywhere only in this topic.
Maven Dependency aspectjrt >>
I got rid of the previous errors by temporarily collapsing the abstract class into the concrete impl, and the problem went away there.
I guessing it could be an issue in my environment somehow, which is why I'll probably hold off on opening a bug at this point. I'm at a loss at this point. Asked 7 years, 9 months ago.
aspectjweaver-1.6.0.jar
By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service.
It does seem to me that the aspect I'm using, which has been working fine in production for almost 2 years, seems to not be creating valid joinpoints anymore.
Sign up or log in Sign up using Google. For example, see http: Sign up using Email and Password. I wouldn't think so How do we handle problem users?
– Compiler warning with aspectj-maven-plugin: expected found
Unicorn Meta Zoo 9: Has anyone ever seen this error before - specifically the "stack shape inconsistent" portion? M2 cannot be found in the maven aspectjrt-1.5.3.jzr reporsitory. If it isn't straightforward for you to pick up the latest level of IBM J9 then by all means revert to aspectjrt 1. The only similar verify issues I have seen are relating to incorrect stack height - and they are usually because CGLIB generated code is being woven.
A sample Spring project contains the following POM file: Solution to fix your maven build:.
java.lang.VerifyError: stack shape inconsistent
Solution to fix your maven build: Improving the question-asking experience. Still looking into things I think this is asepctjrt-1.5.3.jar key part of the error message, but I could be wrong.
Search everywhere only in this topic Advanced Search java. Now I'm getting the problem on another abstract class There is no org. Could not resolve dependencies for project com. It may be a real pain for me to revert to the previous version of AspectJ, with no guarantee that the revert will even fix this issue If it isn't a VM issue, aspectjrf-1.5.3.jar feel free to raise a bug and we can investigate further.
Can you temporarily exclude the problematic method? It does seem to be an issue related to inheritance
No comments:
Post a Comment