| Re: [aspectj-users] aspectjtools fail with NPE during maven build |
|
Hi,
Thank you for response.
So far I was not able to reproduce this issue with the minimal example. The
same setup works as expected – aspects build in a separate library and then used
as a library in a different module. In a small scale project this works fine.
Please also note that this same unchanged config (as in my prev post)
worked perfectly with jdk1.8 and plugin versions: aspectj-maven-plugin v1.8,
aspectjtools v1.9.4. The issue happened after upgrade to Java 11 and plugin
versions v1.14 and v1.9.7 (keeping previous v1.9.4 for the aspectjtools does not
make any difference).
I’ve tried with simplified aspectj-maven-plugin config to see if that makes
any difference:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<version>1.14</version>
<configuration>
<complianceLevel>11</complianceLevel>
<source>11</source>
<target>11</target>
<showWeaveInfo>true</showWeaveInfo>
<verbose>true</verbose>
<aspectLibraries>
<aspectLibrary>
<groupId>xxx.xxx.xxx</groupId>
<artifactId>xxx-aspects</artifactId>
</aspectLibrary>
</aspectLibraries>
</configuration>
<executions>
<execution>
<goals>
<goal>compile</goal>
</goals>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>aspectjtools</artifactId>
<version>1.9.7</version>
<scope>compile</scope>
</dependency>
</dependencies>
</plugin>
however, issue is still present.
The project where issue happens is a large project with hundreds of modules
and >1000 dependency libraries. There is a base platform and client specific
customizations on top of it using base platform APIs. Some aspects are defined
in the base platform (xxx-aspects) and used as library in the platform
customizations for a specific client. The part with
<weaveDirectories>
<weaveDirectory>${project.build.directory}/classesToWeav</weaveDirectory>
</weaveDirectories>
simply holds class files that were extracted from the base platform jars
during the app build because they need to have client specific aspects applied
post compilation and then assembled into deployment.
I perfectly understand that without being able to reproduce issue locally
it is hard to say anything. To me issue seems more like what I call “curse of
the large systems” when factors you wouldn’t even think of may cause unexpected
problems. I’d appreciate any hints based on your knowledge about the tools that
are being used.
Thank you.
From: Alexander Kriegisch
Sent: Sunday, February 13, 2022 7:00 AM
Subject: Re: [aspectj-users] aspectjtools fail with NPE during maven
build It is a bit difficult to debug a Maven POM without any code, especially one with unusual settings like your mix of aspect library, custom includes and custom weave directory. I wonder what those are all for. I never use custom settings like those, even when using aspect libraries. So please create an MCVE on GitHub. I need something to compile (and run after I fixed the build) in order to reproduce your problem. I have never seen anything like it. Just create a minimal Maven project with just as many modules as needed to reproduce the error. In each module, there can be very simple aspect and application code, I do not need your original source code. But it should be reproducible. Then I can probably help you pinpoint the root cause and maybe suggest an alternative approach or fix something. raimondas@xxxxxxxxxx schrieb am 12.02.2022 19:38 (GMT +07:00):
_______________________________________________ aspectj-users mailing list aspectj-users@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/aspectj-users |
