Community
Participate
Working Groups
In pure Java, classes must be declared in a package matching their place in the file structure, e.g. a class stored at <project root>/a/b/Foo.java must be declared to be in the package a.b - if these two do not match you get a compiler error. This is not the case in AspectJ - if package declarations and physical locations do not match there is no compiler error or warning. This is a large problem in a loadtime weaving environment, as it prevents aspect from being loaded. There is no compiler error or warning though, which makes it hard to tell why your code is not running as expected!
Is this the same as bug 45190?
Yes
*** This bug has been marked as a duplicate of 45190 ***