be careful including artifacts from untested repositories..see below
________________________________
From: aspectj-users-boun...@eclipse.org <aspectj-users-boun...@eclipse.org> on
behalf of Mikael Petterson <mikaelpetter...@hotmail.com>
Sent: Friday, March 20, 2020 3:04 AM
To: aspectj-users@eclipse.org <aspectj-users@eclipse.org>
Subject: Re: [aspectj-users] Trying to weave but get error
Hi,
I replaced mojohaus version with
<groupId>com.nickwongdev</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<version>${aspectj.maven.plugin.version}</version>
and these versions:
<aspectj.maven.plugin.version>1.12.6</aspectj.maven.plugin.version>
<aspectj.version>1.9.5</aspectj.version>
Still the same problem.
Two questions comes to my mind:
1. I my multi-module project is it possible to exclude the failing module?
Today I have added settings for aspectj in parent pom.xml
MG>if you only have one artifact to exclude try
MG>--projects '!module-to-exclude'
2. If it is a classpath problem how could it have been working before I
introduced aspectj? Would it not be possible to add generated classes to
classpath for aspectj?
MG> yes using directory parameter within configuration by executing
build-helper-maven-plugin
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>1.12</version>
<executions>
<execution>
<id>add-test-resource</id>
<phase>generate-test-sources</phase>
<goals>
<goal>add-test-resource</goal>
</goals>
<configuration>
<resources>
<resource>
<directory>path/to/additional/test/resources</directory>
<excludes>
<exclude>**/folder-to-exclude/**</exclude>
MG></snip>
MG>hth
MG>Martin
//mike
________________________________
Från: aspectj-users-boun...@eclipse.org <aspectj-users-boun...@eclipse.org> för
Alexander Kriegisch <alexan...@kriegisch.name>
Skickat: den 19 mars 2020 07:37
Till: aspectj-users@eclipse.org <aspectj-users@eclipse.org>
Ämne: Re: [aspectj-users] Trying to weave but get error
>>> The version of aspectj-maven-plugin is for jdk 11 support. It was
>>> urgent at the time.
> https://github.com/mojohaus/aspectj-maven-plugin/commit/c4164ff
No, this commit was about Java 9/10 support.
>> -- AspectJ version
> [Mikael] 1.9.1
That release also was about Java 10 support:
https://www.eclipse.org/aspectj/doc/released/README-191.html
Java 11 support came one release later:
https://www.eclipse.org/aspectj/doc/released/README-192.html
1.9.3 was Java 12, 1.9.4 had a couple of important bugfixes, 1.9.5 supports
Java 13.
My recommendation is to use this fork:
https://mvnrepository.com/artifact/com.nickwongdev/aspectj-maven-plugin/1.12.6
It should support AspectJ 1.9.5 (please also upgrade) and up to Java 13.
The Mojohaus maintainer knows about it and got a pull request. IntelliJ
IDEA's new 2020.x version will support it too for importing AspectJ
projects.
> ...\InjectedFunctionForRegressionChecker.java:6:0::0
> The import ...RegressionSetInjectableFunctionAction cannot be resolved
This rather seems to be some kind of classpath problem, maybe not even
directly related to AspectJ, but impossible to say for sure without the
MCVE.
--
Alexander Kriegisch
https://scrum-master.de
_______________________________________________
aspectj-users mailing list
aspectj-users@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________
aspectj-users mailing list
aspectj-users@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/aspectj-users
