Re: [VOTE] Release Apache Maven Reporting API version 4.0.0-M6

Am 2023-04-09 um 11:24 schrieb Michael Osipov: Hi, we solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12353111 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution

Re: [VOTE] Release Maven Site Plugin version 4.0.0-M7

Am 2023-04-08 um 18:34 schrieb Michael Osipov: Hi, we solved 12 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923&version=12353048 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution

Re: Upcoming Maven Resolver 1.9.8

I think so, assuming there's a new cut On Wed, Apr 5, 2023 at 11:58 AM Tamás Cservenák wrote: > > Eliotte, > > I hope all your concerns are addressed. > Please approve PR if so, and with that, assume you "lifted" your -1 :) > > Thanks > T > > On Wed, Apr 5, 2023 at 1:35 PM Guillaume Nodet wrote:

[GitHub] [maven-jarsigner] elharo commented on pull request #2: [MJARSIGNER-65][MJARSIGNER-66][MJARSIGNER-67] Update parent POM to 39, Java minimum to 1.8, maven minimum to 3.2.5

elharo commented on PR #2: URL: https://github.com/apache/maven-jarsigner/pull/2#issuecomment-1501151024 Maybe that would work. I'm not sure. My general approach is that anything that gets pulled in as a requirement of whatever I'm trying to do (upgrade to 39) is fine as part of that upgrad

[GitHub] [maven-jarsigner] slachiewicz commented on pull request #2: [MJARSIGNER-65][MJARSIGNER-66][MJARSIGNER-67] Update parent POM to 39, Java minimum to 1.8, maven minimum to 3.2.5

slachiewicz commented on PR #2: URL: https://github.com/apache/maven-jarsigner/pull/2#issuecomment-1501129794 Or if @michael-o says that this PR is ok - ok, no need to correct. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [maven-jarsigner] slachiewicz commented on pull request #2: [MJARSIGNER-65][MJARSIGNER-66][MJARSIGNER-67] Update parent POM to 39, Java minimum to 1.8, maven minimum to 3.2.5

slachiewicz commented on PR #2: URL: https://github.com/apache/maven-jarsigner/pull/2#issuecomment-1501129583 About Java 8 upgrade - also separate from parent upgrade to avoid user confusion - agreed long time ago with Robert and followed in other repos. -- This is an automated message fr

[GitHub] [maven-jarsigner] slachiewicz commented on pull request #2: [MJARSIGNER-65][MJARSIGNER-66][MJARSIGNER-67] Update parent POM to 39, Java minimum to 1.8, maven minimum to 3.2.5

slachiewicz commented on PR #2: URL: https://github.com/apache/maven-jarsigner/pull/2#issuecomment-1501129108 https://user-images.githubusercontent.com/6705942/230775330-98df7425-e0f7-4448-b94d-7be22aff0d20.png";> and 3th commit: https://github.com/apache/maven/commit/19c897de6fea72e023a5

[GitHub] [maven-jarsigner] slachiewicz commented on pull request #2: [MJARSIGNER-65][MJARSIGNER-66][MJARSIGNER-67] Update parent POM to 39, Java minimum to 1.8, maven minimum to 3.2.5

slachiewicz commented on PR #2: URL: https://github.com/apache/maven-jarsigner/pull/2#issuecomment-1501128571 we have different practice in other our repos. First commit with parent update - usualy also cleanup to plugins, remove redundant after upgrade entries. Then Fix commit with ref

[GitHub] [maven-jarsigner] elharo commented on pull request #2: [MJARSIGNER-65][MJARSIGNER-66] Update parent POM to 39, Java minimum to 1.8, maven minimum to 3.2.5

elharo commented on PR #2: URL: https://github.com/apache/maven-jarsigner/pull/2#issuecomment-1501114911 Reformatting is, perhaps unfortunately, a fundamental and unavoidable part of the upgrade to parent pom 39 due to the way the new parent pom is configured. Without the reformat the build

Re: [VOTE] Release Apache Maven Reporting API version 4.0.0-M6

+1 niedz., 9 kwi 2023, 11:24 użytkownik Michael Osipov napisał: > Hi, > > we solved 1 issue: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12353111 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%

[VOTE] Release Apache Maven Reporting API version 4.0.0-M6

Hi, we solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12353111 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20ma

[GitHub] [maven-jarsigner] slachiewicz commented on pull request #2: [MJARSIGNER-65][MJARSIGNER-66] Update parent POM to 39, Java minimum to 1.8, maven minimum to 3.2.5

slachiewicz commented on PR #2: URL: https://github.com/apache/maven-jarsigner/pull/2#issuecomment-1501066045 Missing Jira in commit message - not only in PR header. We add one commit to change pom, one another to reformat and then another to ignore formatting. Squash will merge all commi