org.aspectj | projects using m2e , there is a special module called run | Plugin library

Unable to match type List because returning clause also restricts matching to only those method executions that return a value of the specified type (Object or it’s subtypes in this case, which will match any return value).

So, in your code, instead of:

Solved: This was a hybrid project for both mobile and web. I was able to solve it by opening the mobile project separately in intelliJ (I had to open sub directory). So this way my project was able to locate the cucumber file and Java jdk.

All columns in MySql were bigint type instead of double as I made them in coresponding entity, changed them to BigDecimal and everything works fine.

As described in the AspectJ 1.9.7 release notes, due to JEP 396 you need to add --add-opens java.base/java.lang=ALL-UNNAMED to your Java command line.

The problem you have when running your runMainWithError.sh script is documented in AspectJ issue #563710. There is an advice which ought to be inlined, but is not.

Looking at your around advice, I see that it proceeds, but it does not actually change any parameters or return values. So you can simply split it into a before/after-advice pair. Actually, you are not even doing anything after proceeding, so even a simple before-advice would suffice:

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

Remove remote from driver.name. Instead of using value appiumRemoteDriver use appiumDriver and set driverClass capability. To use device from cloud set url provided by cloud service provider as value of remote.server.

For example:

I cannot reproduce the problem because IDEA does not find the Lombok setters. Even when delegating build actions before run to Maven, I get NoSuchMethodError: '...TestEntity.setCode(java.lang.String)'. Next, I am going to try without Lombok. Please note that Lombok and AspectJ do not play nice with each other, see my answer here. Alternatively, you could also make sure that Maven does either of these:

1. First build with Javac + Lombok, then apply AspectJ binary weaving in a second step, all in one module.
2. Similar to above, but do the first build step in module A and the second one in a separate module B. Then you have an unwoven and a woven artifact, which you can both use according to your preferences. For example, you could also use the unwoven one and apply transaction aspects via load-time weaving (LTW) while starting the application. See my other answer here for both approaches #1 and #2.
3. Delombok the source code build the generated sources with the AspectJ compiler in a second build step.

I generated constructors, getters and setters in the IDE instead of using Lombok. Now the project compiles in both IDE and Maven. It behaves exactly as it should. With @Transactional, 0 entities are created, without it 2.

I am not sure if Lombok vs. AspectJ really is the problem due to non-compileability when using Lombok annotations, but it should be easy enough to try without Lombok for you. If it works in your context, too, we found the culprit and can think about implementing one of the 3 approaches mentioned above. Then you can tell me if you have any difficulty in doing so.

Update: I created the two-module version - Javac + Lombok, then Aspect weaving - for you in my fork and also issued pull request #1. I also improved testability a bit. See if that works for you.

Caveat: You cannot simply run DemoApplication from the application-lombok module, because that module is still unwoven and will not show transactional behaviour. But you can simply change the classpath for the run config to the application-aspectj module:

Update: As we found out in the comment section of the other answer, in addition to the problematic Lombok vs. AspectJ compiler configuration, the OP also simply had a problem with his IDE: Using IntelliJ IDEA Community Edition, he was first unaware of, then unable to install the AspectJ plugin, which means that IDEA does not know antyhing about the AspectJ compiler and simply overwrites anything which might have been compiled by AspectJ Maven before with plain Java classes. Therefore, transactional aspects do not work either, unless

• either pre-run compilation is disabled and mvn compile started as an additional pre-build step for the corresponding run configuration,
• or all build actions for the project are being delegated to Maven via configuration,
• the OP buys a licence of IDEA Ultimate and installs the AspectJ plugin.

It was an Intelli-J issue!

So, cleaning the Intelli-J dependency spaghetti up solved it!

1. File > Invalidate cache ... and restart. Helped a bit.
2. Closing the Intelli-J project. Then removed manually the ".idea" folder and any *.iml file.

Yes, I did option 1 previously. Especially doing action 2 solved it within a minute.

Allure jenkins install config

I found the answer by myself, this is some kind of issue in fresh versions of allure-commandline, try to :

1. install old version, for instance 2.8.0
2. then you could install any new version

Seems like in old version, while installation, it's creating path(for ubuntu in my case) in correct direction, and then just update with a new one... Or you can insert installation directory manually and initially install a new version