| 
| Why do advice-precedence warnings not go away? [message #67159] | Fri, 06 October 2006 09:39  |  | 
| Eclipse User  |  |  |  |  | I have two aspects, both of which declare additional fields one some types and hence I also advised the toString() method to emit these
 additional fields (for easier debugging).
 
 But now I keep getting about a dozen of warning messages like:
 
 "at this shadow method-execution(<class> <class>.<method>(<paramTypes>))
 no precedence is specified between advice applying from aspect <aspect1>
 and aspect <aspect2> [Xlint:unorderedAdviceAtShadow]  <project> line 113
 1160141369265 9464183"
 
 even though first to one and then even to BOTH aspects I added:
 -----------------
 public aspect <aspectN> {
 declared precedence: <aspect1>, <aspect2>;
 ...
 }
 -----------------
 
 Why does this not rectify the problem? Why do I still get these
 warnings???
 
 Michael
 |  |  |  | 
| 
| Re: Why do advice-precedence warnings not go away? [message #67178 is a reply to message #67159] | Fri, 06 October 2006 12:36  |  | 
| Eclipse User  |  |  |  |  | sounds like an incremental compilation bug.  And I thought that xlint option was off by default, I presume you have turned it on?
 
 Andy.
 
 Michael Moser wrote:
 > I have two aspects, both of which declare additional fields one some
 > types and hence I also advised the toString() method to emit these
 > additional fields (for easier debugging).
 >
 > But now I keep getting about a dozen of warning messages like:
 >
 > "at this shadow method-execution(<class> <class>.<method>(<paramTypes>))
 > no precedence is specified between advice applying from aspect <aspect1>
 > and aspect <aspect2> [Xlint:unorderedAdviceAtShadow]  <project> line 113
 > 1160141369265 9464183"
 >
 > even though first to one and then even to BOTH aspects I added:
 > -----------------
 > public aspect <aspectN> {
 >    declared precedence: <aspect1>, <aspect2>;
 >    ...
 > }
 > -----------------
 >
 > Why does this not rectify the problem? Why do I still get these warnings???
 >
 > Michael
 >
 |  |  |  | 
| 
| Re: Why do advice-precedence warnings not go away? [message #594954 is a reply to message #67159] | Fri, 06 October 2006 12:36  |  | 
| Eclipse User  |  |  |  |  | sounds like an incremental compilation bug.  And I thought that xlint option was off by default, I presume you have turned it on?
 
 Andy.
 
 Michael Moser wrote:
 > I have two aspects, both of which declare additional fields one some
 > types and hence I also advised the toString() method to emit these
 > additional fields (for easier debugging).
 >
 > But now I keep getting about a dozen of warning messages like:
 >
 > "at this shadow method-execution(<class> <class>.<method>(<paramTypes>))
 > no precedence is specified between advice applying from aspect <aspect1>
 > and aspect <aspect2> [Xlint:unorderedAdviceAtShadow]  <project> line 113
 > 1160141369265 9464183"
 >
 > even though first to one and then even to BOTH aspects I added:
 > -----------------
 > public aspect <aspectN> {
 >    declared precedence: <aspect1>, <aspect2>;
 >    ...
 > }
 > -----------------
 >
 > Why does this not rectify the problem? Why do I still get these warnings???
 >
 > Michael
 >
 |  |  |  | 
Powered by 
FUDForum. Page generated in 0.03886 seconds