[GitHub] [sling-org-apache-sling-jcr-repoinit] reschke commented on pull request #39: SLING-11621: Update JCR dependencies

2023-01-11 Thread GitBox
reschke commented on PR #39: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/39#issuecomment-1378443481 The issue seems to be caused by those ITs trying to bind to jackrabbit artefacts (like rmi) that are not present with the version number being asked for. I assume

[GitHub] [sling-org-apache-sling-jcr-repoinit] reschke commented on pull request #39: SLING-11621: Update JCR dependencies

2023-01-10 Thread GitBox
reschke commented on PR #39: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/39#issuecomment-1378358483 Ok, will have a look. -- 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

[GitHub] [sling-org-apache-sling-jcr-repoinit] reschke commented on pull request #39: SLING-11621: Update JCR dependencies

2022-12-15 Thread GitBox
reschke commented on PR #39: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/39#issuecomment-1353215184 Dependencies should be complete and correct now. Sorry for the inconvenience. I still have test failures, but those iccur on master as well and are likely p