We don't provide any support at all, we do maintenance. Support is paid.
On 2025/02/22 11:57:08 Matthias Bünger wrote:
> Hi,
> during the last days / weeks the topic of (end of) support of Maven and
> it's plugins came up several times in Slack.
>
> On the history page it is stated that we suppor
Hi Gary,
On 23.02.2025 22:27, Gary Gregory wrote:
On Sun, Feb 23, 2025, 15:00 Piotr P. Karwasz
wrote:
Regarding Maven dependencies, did you notice that Maven 3.9.x:
* depends on `maven-resolver-tranport-http` version 1.9.x (supported),
* which depends on HttpClient 4.5 (supported),
* which
Hi,
We solved 7 issues:
https://github.com/apache/maven-install-plugin/milestone/1?closed=1
There are no issues in GitHub:
https://github.com/apache/maven-install-plugin/issues
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINSTALL%20
Hi,
We solved 21 issues:
https://github.com/apache/maven-install-plugin/milestone/2?closed=1
There are no issues in GitHub:
https://github.com/apache/maven-install-plugin/issues
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINSTALL%2
On Sun, Feb 23, 2025, 15:00 Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On 23.02.2025 16:24, Gary Gregory wrote:
> > FWIW, a policy I would consider OK is something like "we support A and B
> > actively and would only consider a release of C for a severe security
> CVE,
> > but D is EOL and OB to furt
Hi Gary,
On 23.02.2025 16:24, Gary Gregory wrote:
FWIW, a policy I would consider OK is something like "we support A and B
actively and would only consider a release of C for a severe security CVE,
but D is EOL and OB to further releases."
Yes, it would be nice to have a well-defined set of le
+1
niedz., 23 lut 2025, 18:32 użytkownik Slawomir Jaranowski <
s.jaranow...@gmail.com> napisał:
> Hi,
>
> We solved 7 issues:
> https://github.com/apache/maven-deploy-plugin/milestone/3?closed=1
>
> There are no issues in GitHub:
> https://github.com/apache/maven-deploy-plugin/issues
>
> There ar
Hi,
We solved 7 issues:
https://github.com/apache/maven-deploy-plugin/milestone/3?closed=1
There are no issues in GitHub:
https://github.com/apache/maven-deploy-plugin/issues
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MDEPLOY%20AND
We solved 18 issues:
https://github.com/apache/maven-deploy-plugin/milestone/2?closed=1
There are no issues in GitHub:
https://github.com/apache/maven-deploy-plugin/issues
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MDEPLOY%20AND%20r
+1
niedz., 23 lut 2025, 17:26 użytkownik Slawomir Jaranowski <
s.jaranow...@gmail.com> napisał:
> Hi,
>
> We solved 12 issues:
>
> https://github.com/apache/maven-project-info-reports-plugin/milestone/1?closed=1
>
> There are no issues in GitHub:
> https://github.com/apache/maven-project-info-rep
Hi,
We solved 12 issues:
https://github.com/apache/maven-project-info-reports-plugin/milestone/1?closed=1
There are no issues in GitHub:
https://github.com/apache/maven-project-info-reports-plugin/issues
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=
FWIW, a policy I would consider OK is something like "we support A and B
actively and would only consider a release of C for a severe security CVE,
but D is EOL and OB to further releases."
Gary
On Sun, Feb 23, 2025, 09:25 Elliotte Rusty Harold
wrote:
> Given available developer time and the sl
Given available developer time and the slow speed at which Maven
evolves, I'm not sure a generic policy is best. Practically we're not
really supporting 3.8.x now. I'd be OK with a policy stating, "We
support 3.9 and no other versions." That's not necessarily what we
want but it is what we do.
Whe
+1
Regards,
Hervé
Le samedi 22 février 2025, 09:43:42 CET Matthias Bünger a écrit :
> Good morning everybody,
> ten days ago I started a discussion about the Maven PDF plugin, asking
> who is using it, if people have switched over to other tools and what
> everybody is thinking about archiving t
or just keep the policy as we have, as it has been wisely worded: once 4 will
be GA, 3.8 will de-facto be EOL'ed as per policy intent
no need to change policy, the currently one perfectly does the job:
https://maven.apache.org/docs/history.html
Reagrds,
Hervé
Le dimanche 23 février 2025, 09:12
I think we should start by declaring maven 3.8.x EOL in preparation for
maven 4.
/Anders
On Sat, Feb 22, 2025 at 12:57 PM Matthias Bünger
wrote:
> Hi,
> during the last days / weeks the topic of (end of) support of Maven and
> it's plugins came up several times in Slack.
>
> On the history page
16 matches
Mail list logo