|
||||||||
|
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-14423) Declare direct deps ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)
- [JIRA] (JENKINS-14423) Declare direct ... [email protected] (JIRA)

Client must also apparently depend on wagon-provider-api:org.apache.maven.wagon:2.2 to get AbstractWagon.getTimeout, though I am still unclear on why.