stefanseifert commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock/pull/31#issuecomment-1810204110
> 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](https://issues.apache.org/jira/browse/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. in general i'm completely on your side, but if you are e.g. stuck in an older AEM 6.5 project, you are bound to work with a certain set of outdated 3rdparty dependencies - but still may want to use the latest features provided by sling-mock. > 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? normally we prefer separate JIRA issues for separate topics and PRs, but in this case it's fine to link them to the already existing ticket as they are all related to dependency updates. -- 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]
