Aspectj-maven-plugin 1.15.0 includes all of the project's dependencies (except pom-type) to the -classpath parameter for AJC (see here).
In our project we use some dependencies that have yaml packaging type and they are added to the classpath, resulting in a compilation errors like this:

Failed to init Classpath for jar file /home/user/.m2/repository/<artifact_path>.yaml
java.util.zip.ZipException: zip END header not found
at
....
at org.codehaus.mojo.aspectj.AbstractAjcCompiler.execute(AbstractAjcCompiler.java:568)

It would be great if there was an option to filter out dependency types other than pom to prevent them from including in classpath (or, more general, a classpath customization/filtering feature).