rmcdouga commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock/pull/31#issuecomment-1810126968
OK, I will split up the changes into multiple PRs as requested. I'm not sure I agree with the idea of using older dependency versions for compatibility with older downstream product versions. Older versions of sling-mock are still available for projects targeting these older product versions. I'm used to (and am comfortable with) projects like Spring that move to the latest versions of dependencies pretty aggressively. It encourages the whole ecosystem to continuously upgrade their dependencies. Upgrading dependencies is like exercise - the more frequently you do it, the easier it gets. Having said that, the dependencies we're talking about are only a couple of point releases old, so that's pretty current. I don't feel too bad about leaving them alone. I will split into a PR for testing dependencies in this project, one for commons-lang (but to version 3.9), and will have a look at the other projects you mention and I'll raise PRs in those projects for the testing dependencies. If that plan is acceptable, then feel free to close this PR. One more thing - How would you like to handle the JIRA issues? Should I raise separate issues for each PR or can I continue to use the same JIRA issue for all PRs? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
