It would be nice to include
in the global parent, to make unit testing easier with the Sling Hamcrest Matchers.
the aem-global-parent currently does not declare any testing dependencies.
but we could add it as compile dependency to aem-mock so it's avialable in all projects referencing aem-mock as test dependency.
@Stefan That sounds good to me as well.
I thought one of the global parents defined AEM Mocks as a testing dependency, but maybe I’m wrong there. Wouldn’t it be a good idea to do that?
i've included it in aem-mocks as compile dependency for convenience.
i'm very hesitant adding and direct dependency to aem-global-parent directly (we only have few for static code analysis and OSGi annotations) - it forces them down on all projects depending from it, you can override them but never can get rid of them downstream.