On Tue, Oct 14, 2014 at 2:19 PM, Alexander Kriegisch <
alexan...@kriegisch.name> wrote:

> Yes, the default compliance level is 1.4 according to
> http://mojo.codehaus.org/aspectj-maven-plugin/compile-mojo.html#complianceLevel,
> even in the current plugin version 1.7 (you still use 1.5, I recommend an
> update there as well, not just in the AspectJ runtime).
>
Will do. Thank you.


> --
> Alexander Kriegisch
> http://scrum-master.de
>
>
> Am 14.10.2014 um 23:08 schrieb Heshan Suriyaarachchi <
> heshan.suriyaarach...@gmail.com>:
>
> Thank you for the quick feedback guys.
>
> I tried updating to the latest aspectj jars too. Still I saw the same
> error. Then I found out the error. I was missing the <complianceLevel> tag
> in my plugin configuration.
>
> Pasting the updated aspectj-maven-plugin configuration in case someone
> runs into the same issue that I ran into.
>
>              <plugin>
>                 <groupId>org.codehaus.mojo</groupId>
>                 <artifactId>aspectj-maven-plugin</artifactId>
>                 <version>1.5</version>
>                 <configuration>
>                     <complianceLevel>1.7</complianceLevel>
>                     <source>1.7</source>
>                     <target>1.7</target>
>                 </configuration>
>                 <executions>
>                     <execution>
>                         <!--<phase>process-sources</phase>-->
>                         <goals>
>                             <goal>compile</goal>
>                             <goal>test-compile</goal>
>                         </goals>
>                     </execution>
>                 </executions>
>             </plugin>
>
> Thanks,
> Heshan.
>
> On Tue, Oct 14, 2014 at 1:43 PM, Frank Pavageau <frank.pavag...@gmail.com>
> wrote:
>
>> 2014-10-14 21:28 GMT+02:00 Andy Clement <andrew.clem...@gmail.com>:
>>>
>>> I’d recommend updating to a more recent AspectJ.  Older AspectJs did
>>> have issues with making mistakes generating stack map frames.  The option
>>> to use split verifier was only possible with JDK1.6 I think, with 1.7 they
>>> removed that capability so the stack map frames needed to be correct.
>>>
>>
>> For the record, -XX:-UseSplitVerifier is available in the Hotspot JVM 7
>> to disable the "new" verifier which needs correct stack map frames. It's
>> not available in the Hotspot JVM 8 anymore.
>>
>> Frank
>>
>> _______________________________________________
>> aspectj-users mailing list
>> aspectj-users@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>>
>
>
>
> --
> Regards,
> Heshan Suriyaarachchi
>
> http://heshans.blogspot.com/
> http://www.linkedin.com/in/heshan
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>



-- 
Regards,
Heshan Suriyaarachchi

http://heshans.blogspot.com/
http://www.linkedin.com/in/heshan
_______________________________________________
aspectj-users mailing list
aspectj-users@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Reply via email to