As Guillaume said, the time table of _actual removal_ from Maven (4) Core
is still questionable.
OTOH, we do want to _ensure_ that at least Maven Core Plugins are
maven-compat free...
Personal (biased) opinion: given how much of the plugin that claims itself
to be Maven3 plugin depends on maven-co
On Tue, Apr 30, 2024 at 2:42 PM Tamás Cservenák wrote:
>
> This should have happened in last 10 years, but for some reason it didn't.
Does the Maven project have a plan for ensuring that, once started,
migrations are completed within a reasonable amount of time? In the
Jenkins project, this is pa
This should have happened in last 10 years, but for some reason it didn't.
Basically, if plugin explicitly (or implicitly) depends on maven-compat, it
is still de facto a Maven2 plugin. In 2024. Go figure!
Thanks
T
On Tue, Apr 30, 2024, 23:30 Olivier Lamy wrote:
> On Tue, 30 Apr 2024 at 15:56,
On Tue, 30 Apr 2024 at 15:56, Guillaume Nodet wrote:
>
> Maven-compat has been deprecated years ago, so the goal would be to get rid
> of it.
> For months, efforts have been made to first make maven-compat completely
> optional.
> This is now the case in maven itself.
> However, some plugins still
+1
wt., 30 kwi 2024, 12:44 użytkownik Slawomir Jaranowski <
s.jaranow...@gmail.com> napisał:
> +1
>
> pon., 29 kwi 2024 o 23:51 Slawomir Jaranowski
> napisał(a):
>
> > Hi,
> >
> > We solved 4 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=1235
+1
pon., 29 kwi 2024 o 23:51 Slawomir Jaranowski
napisał(a):
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354488
>
> There are no more issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHA
+1
wt., 30 kwi 2024, 09:43 użytkownik Michael Osipov
napisał:
> +1
>
> On 2024/04/29 19:19:38 Michael Osipov wrote:
> > Hi,
> >
> > we solved 2 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354403
> >
> > There are still a couple of issues left
Hello everyone,
In the meantime JReleaser offers support for both publishing to the Portal
and handling build poms
https://github.com/jreleaser/jreleaser/issues/1612
https://github.com/jreleaser/jreleaser/issues/1632
FWIW the Portal API is publicly available at
https://central.sonatype.org/publi
Hi,
AFAIK and if I got right the info from Brian, this is not yet promoted and
the primary solution but will become soon.
Personally I'm not that shocked we were not consulted - we build plugin API
for that exact purpose, let people do what they need to do.
About maven-compat it i mainly about u
Hi,
Does anyone try the new Sonatype Central Portal?
https://central.sonatype.org/publish-ea/publish-ea-guide/
There is a new (*) Maven plugin provided by Sonatype for deployments:
https://central.sonatype.org/publish/publish-portal-maven/
But I am afraid that this plugin will be similar
to nexu
+1
On 2024/04/29 19:19:38 Michael Osipov wrote:
> Hi,
>
> we solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354403
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20A
11 matches
Mail list logo
