|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
We use ivy version 2.3 and the inclusion of ivy 2.2 causes obscure build failures which are difficult to attribute to artifactory-plugin. Sounds like unrelated ivy issues so tracking down the root cause is most time consuming. Fix is messy!
We would suggest a configuration option which would allow us to specify which version of ivy to include in any and where to get the jar file. For us it would be fine to be server configuration rather than job configuration as we have standardized on the version of ivy which goes with our ant version (also standardized).