Hi Team,
When we are trying to run the sonar-qube on the AEM project then we are getting the following error:
Solved! Go to Solution.
Views
Replies
Total Likes
Hello @PavanKu2
We have recently integrated with Sonarqube via Github Actions
Our dependency looks like:
<plugin>
<groupId>com.day.jcr.vault</groupId>
<artifactId>content-package-maven-plugin</artifactId>
<version>1.0.2</version>
<configuration>
<targetURL>http://${aem.host}:${aem.port}/crx/packmgr/service.jsp</targetURL>
<failOnError>true</failOnError>
<userId>${vault.user}</userId>
<password>${vault.password}</password>
</configuration>
</plugin>
@MukeshYadav_@Kamal_Kishor@A_H_M_Imrul@BhavaniBharani@Jangra98@anasustic@chavad@SaumyaJa@Tom_Fought@bagwanpankaj
Kindly take a moment to review this question and share your valuable insights. Your expertise would be greatly appreciated!
Views
Replies
Total Likes
Hello @PavanKu2
We have recently integrated with Sonarqube via Github Actions
Our dependency looks like:
<plugin>
<groupId>com.day.jcr.vault</groupId>
<artifactId>content-package-maven-plugin</artifactId>
<version>1.0.2</version>
<configuration>
<targetURL>http://${aem.host}:${aem.port}/crx/packmgr/service.jsp</targetURL>
<failOnError>true</failOnError>
<userId>${vault.user}</userId>
<password>${vault.password}</password>
</configuration>
</plugin>
@PavanKu2 Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
Views
Like
Replies