[GitHub] [maven-artifact-transfer] cstamas commented on pull request #23: [MSHARED-987] Drop legacy, prepare for future

cstamas commented on pull request #23: URL: https://github.com/apache/maven-artifact-transfer/pull/23#issuecomment-828981376 This is the pattern I want to implement: https://github.com/cstamas/providers basically new "api" module, as many provider we want (maven3.0, maven3.1, ...) a

Re: [VOTE] Release Apache Maven Shared Utils version 3.3.4

+1 On Tue, 27 Apr 2021 at 03:59, Maarten Mulders wrote: > Hi, > > We solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12350122&styleName=Text > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=

[GitHub] [maven-artifact-transfer] cstamas commented on pull request #23: [MSHARED-987] Drop legacy, prepare for future

cstamas commented on pull request #23: URL: https://github.com/apache/maven-artifact-transfer/pull/23#issuecomment-828750815 So, in the meanwhile (as we "facilitate" the Apéritif), the plan in short: * return maven 3.0 support * explode m-a-t into modules: m-a-t contains "api" and hav

[GitHub] [maven-site-plugin] qualitesys commented on pull request #48: [MSITE-872] Set the Content-Type header

qualitesys commented on pull request #48: URL: https://github.com/apache/maven-site-plugin/pull/48#issuecomment-828723284 Tested ok in standalone mode and ok in the CI chain -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [maven-artifact-transfer] cstamas commented on pull request #23: [MSHARED-987] Drop legacy, prepare for future

cstamas commented on pull request #23: URL: https://github.com/apache/maven-artifact-transfer/pull/23#issuecomment-828682507 I think this deserves a new Maven Apéritif... Where I could explain why I think we need to keep m-a-t, but not in today's form (but with minimal, ideally no API cha

[GitHub] [maven-artifact-transfer] slachiewicz commented on pull request #23: [MSHARED-987] Drop legacy, prepare for future

slachiewicz commented on pull request #23: URL: https://github.com/apache/maven-artifact-transfer/pull/23#issuecomment-828679562 not wort to reopen.. see here https://github.com/apache/maven-artifact-transfer/pull/20 -- This is an automated message from the Apache Git Service. To respon

Re: [VOTE] Release Maven Project Info Reports Plugin version 3.1.2

+1 from me Kind regards Karl Heinz Marbaise On 25.04.21 21:46, Michael Osipov wrote: Hi, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12349521 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MPI

Re: [VOTE] Release Apache Maven Shared Utils version 3.3.4

+1 from me. Kind regards Karl Heinz Marbaise On 26.04.21 19:59, Maarten Mulders wrote: Hi, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12350122&styleName=Text There are still a couple of issues left in JIRA: https://issues.apache.org/

Re: [VOTE] Release Apache Maven Shared Utils version 3.3.4

+1 On 26-4-2021 19:59:53, Maarten Mulders wrote: Hi, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12350122&styleName=Text There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%

[GitHub] [maven-artifact-transfer] cstamas opened a new pull request #23: [MSHARED-987] Drop legacy, prepare for future

cstamas opened a new pull request #23: URL: https://github.com/apache/maven-artifact-transfer/pull/23 In general, support Maven 3.1+ only (drop Maven 3.0 support). https://issues.apache.org/jira/browse/MSHARED-987 -- This is an automated message from the Apache Git Service. To resp