Thanks Ryan, I found out it was because some code deeper down was creating a
parser each time. I think you might be right as the parser created a
hashmap each time. It's very frustrating this takes over 100 times longer
on the server though, the specs are quite similar between my server and
I have one more doubt... I am adding aspects to hadoop source code and I
imported one of the package and created aspect aj file but while running I
have to choose main function but it seems no class of this package have main
function...What I have to do?...Plz help me...
--
View this message in
can you share a link or any other on how to create a configuration
manually...also is it mandatory to mention the main class in the
configuration?
--
View this message in context:
http://aspectj.2085585.n4.nabble.com/Aspectj-in-weaving-a-jar-file-tp4651584p4651607.html
Sent from the AspectJ -
Hi,
I have a project which is using aspectj and it is building fine with Java
1.6. When I update it to Java 1.7 I'm seeing following error.
[INFO] Molva the Destroyer Aspects ... FAILURE [2.324s]
[INFO] Molva The Destroyer Client SKIPPED
[INFO] Molva
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
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).
--
Alexander Kriegisch
I forgot to mention that AspectJ Maven Plugin 1.7 automatically uses
aspectjtools 1.8.2 by default, see
http://mojo.codehaus.org/aspectj-maven-plugin/dependencies.html
Am 14.10.2014 um 23:19 schrieb Alexander Kriegisch alexan...@kriegisch.name:
Yes, the default compliance level is 1.4
