|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [JIRA] (JENKINS-15490) checkstyle plugin d... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
- [JIRA] (JENKINS-15490) checkstyle plu... zhqin...@gmail.com (JIRA)
I created a empty project with our enterprise parent pom and it has the same problem but when the pom is empty, the issue is gone.
So I remove the config item one by one to see which one is the cause and it turns out the config below:
<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-webdav-jackrabbit</artifactId>
<version>1.0</version>
</extension>
</extensions>
</build>
Just add this part into an empty pom will cause this issue. Using latest version 2.2 still cause this issue.