rmcdouga commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock/pull/31#issuecomment-1810370859
> 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](https://issues.apache.org/jira/browse/SLING-mock). Ironically, I had the opposite problem. I'm using the latest version of AEM and I am using the latest aem-mock but was stuck with the old dependencies (thanks to old dependencies in sling-testing-hamcrest). You can't please everyone. 😃 Since you can't please everyone, personally, I would aim to please the people who stay current. This makes their life easier and it puts additional pressure on the laggards to upgrade more regularly if they want the latest features (which is the "right thing to do", so while they may not like it, it's in their best interest and if they do it more regularly it will become easier). > 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. OK, will do. Thanks for reviewing this and for the detailed comments. -- 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]
