[
https://issues.apache.org/jira/browse/SLING-12000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-12000.
--
> Mocks: Update to sling-bundle-parent 52, switch to Java
-mock-oak/commit/1272b025ba25d6f7de9278ce1434980acb33c614
> Mocks: Update to sling-bundle-parent 52, switch to Java 11
> --
>
> Key: SLING-12000
> URL: https://issues.apache.org/jira/bro
stefanseifert merged PR #9:
URL:
https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/pull/9
--
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
stefanseifert merged PR #28:
URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock/pull/28
--
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,
stefanseifert merged PR #9:
URL:
https://github.com/apache/sling-org-apache-sling-testing-resourceresolver-mock/pull/9
--
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
stefanseifert merged PR #30:
URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/30
--
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,
stefanseifert merged PR #1:
URL:
https://github.com/apache/sling-org-apache-sling-testing-logging-mock/pull/1
--
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,
stefanseifert merged PR #24:
URL: https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/pull/24
--
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,
sonarcloud[bot] commented on PR #9:
URL:
https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/pull/9#issuecomment-1677382277
Kudos, SonarCloud Quality Gate passed! [![Quality Gate
sonarcloud[bot] commented on PR #28:
URL:
https://github.com/apache/sling-org-apache-sling-testing-sling-mock/pull/28#issuecomment-1677374270
Kudos, SonarCloud Quality Gate passed! [![Quality Gate
stefanseifert opened a new pull request, #9:
URL:
https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/pull/9
https://issues.apache.org/jira/browse/SLING-12000
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
sonarcloud[bot] commented on PR #24:
URL:
https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/pull/24#issuecomment-1677368006
Kudos, SonarCloud Quality Gate passed! [![Quality Gate
stefanseifert opened a new pull request, #28:
URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock/pull/28
also get rid of guava testing dependencies
https://issues.apache.org/jira/browse/SLING-12000
--
This is an automated message from the Apache Git Service.
sonarcloud[bot] commented on PR #9:
URL:
https://github.com/apache/sling-org-apache-sling-testing-resourceresolver-mock/pull/9#issuecomment-1677347432
Kudos, SonarCloud Quality Gate passed! [![Quality Gate
stefanseifert opened a new pull request, #9:
URL:
https://github.com/apache/sling-org-apache-sling-testing-resourceresolver-mock/pull/9
also get rid of guava testing dependencies
https://issues.apache.org/jira/browse/SLING-12000
--
This is an automated message from the Apache Git
sonarcloud[bot] commented on PR #30:
URL:
https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/30#issuecomment-1677302213
Kudos, SonarCloud Quality Gate passed! [![Quality Gate
stefanseifert opened a new pull request, #30:
URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/30
also get rid of guava testing dependencies
https://issues.apache.org/jira/browse/SLING-12000
--
This is an automated message from the Apache Git Service.
To
sonarcloud[bot] commented on PR #1:
URL:
https://github.com/apache/sling-org-apache-sling-testing-logging-mock/pull/1#issuecomment-1677279925
Kudos, SonarCloud Quality Gate passed! [![Quality Gate
stefanseifert opened a new pull request, #1:
URL:
https://github.com/apache/sling-org-apache-sling-testing-logging-mock/pull/1
https://issues.apache.org/jira/browse/SLING-12000
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
sonarcloud[bot] commented on PR #24:
URL:
https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/pull/24#issuecomment-1677270990
Kudos, SonarCloud Quality Gate passed! [![Quality Gate
stefanseifert opened a new pull request, #24:
URL: https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/pull/24
also get rid of guava testing dependencies
https://issues.apache.org/jira/browse/SLING-12000
--
This is an automated message from the Apache Git Service.
To
Stefan Seifert created SLING-12000:
--
Summary: Mocks: Update to sling-bundle-parent 52, switch to Java 11
Key: SLING-12000
URL: https://issues.apache.org/jira/browse/SLING-12000
Project: Sling
+1
As a first step: at least we can make sure bundles should run with 8 and 11
together
Regards,
Ashok
On 2022/06/15 15:10:53 Konrad Windszus wrote:
> Hi,
> AFAIK all our Sling bundles still target Java 8. I think for major feature
> updates we could increase this to Java 11 to leverage the
On Wednesday, 15 June 2022 17:10:53 CEST Konrad Windszus wrote:
> Hi,
> AFAIK all our Sling bundles still target Java 8. I think for major feature
> updates we could increase this to Java 11 to leverage the newly introduced
> features
On Wed, 2022-06-15 at 13:02 -0700, Eric Norman wrote:
> >
> > I think it is time now to do the shift.
> > WDYT?
>
>
> +1, though java 11 only has active support until Sep 2023, so we may
> need
> to begin thinking about the path toward java 17
I agree, we should be Java 17 ready. FWIW, we
On Wed, 2022-06-15 at 17:10 +0200, Konrad Windszus wrote:
> Hi,
> AFAIK all our Sling bundles still target Java 8. I think for major
> feature updates we could increase this to Java 11 to leverage the
> newly introduced features
> (https://www.geeksforgeeks.org/java-11-features-and-comparison/,
>
>
> I think it is time now to do the shift.
> WDYT?
+1, though java 11 only has active support until Sep 2023, so we may need
to begin thinking about the path toward java 17
Regards,
-Eric
On Wed, Jun 15, 2022 at 8:10 AM Konrad Windszus wrote:
> Hi,
> AFAIK all our Sling bundles still target
+1
Am Mi., 15. Juni 2022 um 17:10 Uhr schrieb Konrad Windszus :
> Hi,
> AFAIK all our Sling bundles still target Java 8. I think for major feature
> updates we could increase this to Java 11 to leverage the newly introduced
> features
Hi,
AFAIK all our Sling bundles still target Java 8. I think for major feature
updates we could increase this to Java 11 to leverage the newly introduced
features (https://www.geeksforgeeks.org/java-11-features-and-comparison/,
29 matches
Mail list logo