This is a known bug in the maven eclipse plugin.
A simple workaround is to specify adjtVersion in the maven-eclipse-plugin POM configuration section (or just upgrade your version: D):
<ajdtVersion>none</ajdtVersion>
EclipseClassPathWriter contains the following code:
if ( ( config.getAjdtVersion() != 0 ) &&
dep.getArtifactId().toLowerCase().indexOf( "aspectj" ) >= 0 )
{
return;
}