Adding BIRT runtime to spring-boot project dependencies breaks QueryDSL code generation. How to overcome?

Question

Java

Good day.
There is a spring-boot project that uses QueryDSL JPA, and code generation works in it through annotation processing. When added as a birt-runtime project dependency, generation breaks. Details below:
Code generation configuration:

<plugin>
    <groupId>com.mysema.maven</groupId>
    <artifactId>apt-maven-plugin</artifactId>
    <version>1.1.3</version>
    <executions>
        <execution>
            <phase>generate-sources</phase>
            <goals>
                <goal>process</goal>
            </goals>
            <configuration>
                <outputDirectory>${project.build.directory}/generated-sources</outputDirectory>
                <processor>com.querydsl.apt.jpa.JPAAnnotationProcessor</processor>
            </configuration>
        </execution>
    </executions>
    <dependencies>
        <dependency>
            <groupId>com.querydsl</groupId>
            <artifactId>querydsl-apt</artifactId>
            <version>${querydsl.version}</version>
        </dependency>
    </dependencies>
</plugin>

When adding this dependency, everything breaks:

<dependency>
    <groupId>org.eclipse.birt.runtime</groupId>
    <artifactId>org.eclipse.birt.runtime</artifactId>
    <version>4.6.0-20160607</version>
</dependency>

Build message:

[INFO] --- apt-maven-plugin:1.1.3:process (default) @ project---
error: Could not instantiate an instance of processor 'com.querydsl.apt.jpa.JPAAnnotationProcessor'
1 error

As a result, Q* classes are not generated, and a build error occurs further.
Is there any way to fix this, and if so, how?
UPD
It turned out that:
1) The penultimate version does not break anything.
2) The penultimate one is not signed, the last one is signed. After removing signed files from jar file, annotation-processing stops breaking and all is well.
Pls advise maven-way way to remove signature from jar file nicely...