Hi,
It is only a recent thing that you have the ability to have 'non mangled' names for the generated elements. Originally all names were mangled because the principal design was that you are expressing new members that are private 'with respect to the aspect' - so they are for the aspects use and the user code doesn't want to know they are there - if they are mangled then the user code is very unlikely to trip over them. However, more and more users wanted to use the pattern to add private members to types and not have them mangled. The first round of changes made this work for ITDs on classes. The second round of changes handled this for ITDs on interfaces - under https://bugs.eclipse.org/bugs/show_bug.cgi?id=73507 - this was in AspectJ 1.7.1. The older naming scheme can be 'forced' by using -Xset:itdVersion=1 - that will ensure all names are mangled like they used to be and is primarily still in the code for compatibility reasons (if you had legacy code that had certain expectations). There is no option to force the new naming scheme, it should be the default.
Your maven shows you as using 1.6.11 - you should probably update to 1.7.1. It may be that the builds in eclipse are using the new naming scheme whilst your maven builds are using the old naming scheme.
cheers,
Andy