nar-maven-plugin | Native ARchive plugin for Maven | Plugin library

For some reason, I was able to make my APIs work by removing the other two casa classes and just made casa refer to the creditcard classes since they both have the same exact implementation. Although this would make the casa package dependent on the creditcard package.

Basically this is what I did. Instead of importing this for the casa package

Try Java SE 17. Java SE 8 is slowly being discontinued.

Or else try using GitHub or GitLab. that should do the trick.

there is also a free app called ci circle in Github.

it is very easy once you install it.it's free for the bonus.

it can build your apps automatically every time you commit.

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

The property is called "sonar.coverage.jacoco.xmlReportPaths" (note the "s"). Your text and your code sample specify different property names and values for this. Figure out where it is and use that. Different build configurations might put it in a different place. Look in the workspace of your build to see where the file was created.

When you do a sonar analysis using maven you don't need to configure manually.

The error (Your project contains .java files, please provide compiled classes with sonar.java.binaries property, or exclude them from the analysis with sonar.exclusions property) you are experiencing because sonar maven plugin expects the compiled classes in your target\classes folder and the class files are missing. This is due to executing the sonar analysis before the java files are compiled.

To solve this first execute mvn package and then execute maven sonar analysis.

The spring-boot-maven-plugin is running after the maven-assembly-plugin. So at the time the assembly is created, there simply is no executable JAR file available yet. To fix the execution order just move the definition of the maven-assembly-plugin below the spring-boot-maven-plugin in your POM.

Yous need the compiled class to do sonar analysis. So in your run_sonar() add package to maven command.

I believe I found the issue;

I was having multiple repositories for the same entity. For example: I had an OrdersDao and a OrderRestRepo for the Order entity which where both an repository interface. The reason for creating 2 repo's for the same entity was because I want the OrderRestRepo to utilize @preauthorize functionality, which I did not want to apply to the OrdersDao as that's also used by one my of schedulers.

When moving to a single repo, single entity I have not seen the inconsistent exposure of the endpoints (rebooted about 6 / 7 times consistently).

For the scheduler issue I'll probably reside to the solution #2 described in the following so: SecurityContext with default System authentication/user

Update: i found some defect on Spring Github which explains the exact behavior I noticed: https://github.com/spring-projects/spring-data-rest/issues/1286

It seems to be a known issue. The suggested solution is to use @Primary annotation on the exposed repositry and set the non-exposed reposity to Exported = False. From the defect listed it seems that @Primary initially did not work as expected, but this may have been fixed over time. The defect is still marked as open so i'm just gonna try the suggested and otherwise reside to the initial solution.

Update 2

So far using the @Primary to the repository which should be exposed as Rest, is working as expected. So I now have 2 repo's for the same entity.

According to source code this path is derived from the following properties:

• sonar.globalWorking.directory system property (resolved relative to settings below if not absolute),
• sonar.userHome system property,
• SONAR_USER_HOME environment variable,
• .sonar directory under user.home system property.

It seems that the last case matches your scenario. Try to set one of the above settings to select different location instead of ~/.sonar.