[GitHub] [maven-shared-incremental] dependabot[bot] commented on pull request #11: Bump slf4j-api from 1.7.36 to 2.0.0

dependabot[bot] commented on PR #11: URL: https://github.com/apache/maven-shared-incremental/pull/11#issuecomment-1222819645 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or

[GitHub] [maven-shared-incremental] asfgit closed pull request #11: Bump slf4j-api from 1.7.36 to 2.0.0

asfgit closed pull request #11: Bump slf4j-api from 1.7.36 to 2.0.0 URL: https://github.com/apache/maven-shared-incremental/pull/11 -- 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

[GitHub] [maven-shared-incremental] dependabot[bot] commented on pull request #4: Bump mavenVersion from 2.2.1 to 3.8.6

dependabot[bot] commented on PR #4: URL: https://github.com/apache/maven-shared-incremental/pull/4#issuecomment-1222815824 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a

[GitHub] [maven-shared-incremental] asfgit closed pull request #4: Bump mavenVersion from 2.2.1 to 3.8.6

asfgit closed pull request #4: Bump mavenVersion from 2.2.1 to 3.8.6 URL: https://github.com/apache/maven-shared-incremental/pull/4 -- 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

[GitHub] [maven-shared-incremental] dependabot[bot] opened a new pull request, #11: Bump slf4j-api from 1.7.36 to 2.0.0

dependabot[bot] opened a new pull request, #11: URL: https://github.com/apache/maven-shared-incremental/pull/11 Bumps [slf4j-api](https://github.com/qos-ch/slf4j) from 1.7.36 to 2.0.0. Commits

Re: Integration test suite

Hi Herve, I saw your fix but I was wondering if just adding those two lines to the bootstrap.txt: +org.apache.maven.plugins:maven-dependency-plugin:3.1.1 +org.apache.maven.plugins:maven-dependency-plugin:3.3.0 wouldn't be a simpler fix. The test itself seems fine, just the deps are missing. -h

Re: Integration test suite

Hi Maarten, Thank you for the explanation! The GH actions are much more visible on Pull Requests; I was not even aware that there is a jenkins setup (as this is not surfaced anywhere for a PR). It would be good to document that implicit maven / maven-integration-testing checking; I am not

JDK 19 first Release Candidates!

Greetings! I hope you had a chance to take some time off. On our side, and despite the summer vacation, everything is on track for the Java 19 GA release on September 20th with JDK 19 now in the Release Candidate Phase [1]. If you haven't done so yet, it is time to start testing your

Re: Integration test suite

Hi all, The overall idea of the integation tests in GH Actions is this: 1. Check if the org/owner of the fork where the PR comes from _also_ has a fork of maven-integration-testing. 2. If so, check if they have a branch on that fork with the same name as the fork of maven-core. 3. If so, run

Re: Integration test suite

I did a first quick pass, but I fear there is an unexpected warning with m- antrun-p that still causes a failure: I don't time yet to fix, I need to leave, help welcome... Le lundi 22 août 2022, 07:57:31 CEST Hervé BOUTEMY a écrit : > uh, sorry, I overlooked that I broke the core ITs... > >