Re: maven-compat removal?

2024-04-30 Thread Tamás Cservenák 
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-compat (explicitly or implicitly),
Maven 4.0 is most probably too early to remove it, DESPITE we talk about
maven-compat, a module that offers Maven2 compatibility layer. OTOH, the
_presence_ of this module is becoming an impediment for us, and we do want
to get rid of it, the sooner the better. On a related note: users who were
against Maven 3.9.x emitting warnings about deprecated plugins... They
"won", all the "Maven 3.9 should prepare for 4.0 work stopped", and this is
the price now: it is not simple to detect these plugins in the wild. I
understand "they (users) cannot do anything about warnings", but that could
be at least "they (users) live with warnings and report deprecation issues
to authors of deprecated plugins"... Currently we really have no clue how
many affected (non-core) Maven plugins could be out there, that would
simply break, if maven-compat would be removed.

Thanks
T

On Wed, May 1, 2024 at 12:32 AM Basil Crow  wrote:

> 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 part of our engineering process at the design
> proposal stage:
>
>
> https://github.com/jenkinsci/jep/blob/eedd98dadbf70f69a291c9184facafc64dc82097/jep-template//README.adoc?plain=1#L150-L185
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: maven-compat removal?

2024-04-30 Thread Basil Crow 
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 part of our engineering process at the design
proposal stage:

https://github.com/jenkinsci/jep/blob/eedd98dadbf70f69a291c9184facafc64dc82097/jep-template//README.adoc?plain=1#L150-L185

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: maven-compat removal?

2024-04-30 Thread Tamás Cservenák 
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, 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 rely on it and they should be migrated to use
> > Maven 3 apis.
> > This is a required step before being able to get rid of maven-compat.
> >
> > I'm still hesitant about the time table, whether maven-compat should be
> > removed from
> > 4.0 distribution or not.  It may be slightly premature, since a few
> plugins
> > still depend on it.
> >
>
> if we could have at least core plugins (default lifecycle) ready, that
> could work, but that's some work.
> but do you have some timeline in mind for 4.0? or it's just whenever
> it;s ready :)
>
>
>
> > Le mar. 30 avr. 2024 à 02:02, Olivier Lamy  a écrit :
> > >
> > > Hi,
> > > I can see plenty of PRs with maven-compat removal.
> > > Maybe this could be explained and so more people could help for this
> task?
> > >
> > > cheers
> > > Olivier
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> >
> >
> > --
> > 
> > Guillaume Nodet
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: maven-compat removal?

2024-04-30 Thread Olivier Lamy 
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 rely on it and they should be migrated to use
> Maven 3 apis.
> This is a required step before being able to get rid of maven-compat.
>
> I'm still hesitant about the time table, whether maven-compat should be
> removed from
> 4.0 distribution or not.  It may be slightly premature, since a few plugins
> still depend on it.
>

if we could have at least core plugins (default lifecycle) ready, that
could work, but that's some work.
but do you have some timeline in mind for 4.0? or it's just whenever
it;s ready :)



> Le mar. 30 avr. 2024 à 02:02, Olivier Lamy  a écrit :
> >
> > Hi,
> > I can see plenty of PRs with maven-compat removal.
> > Maybe this could be explained and so more people could help for this task?
> >
> > cheers
> > Olivier
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
>
> --
> 
> Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Script Interpreter version 1.6

2024-04-30 Thread Sylwester Lachiewicz 
+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=12354488
> >
> > There are no more issues left in JIRA:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-script-interpreter
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-2105/
> >
> >
> https://repository.apache.org/content/repositories/maven-2105/org/apache/maven/shared/maven-script-interpreter/1.6/maven-script-interpreter-1.6-source-release.zip
> >
> > Source release checksum(s):
> > maven-script-interpreter-1.6-source-release.zip - SHA-512 :
> >
> 328a0a033952e6cecb264bf02198808c08e04b05165a72dd3bd168415055703bae1a6732c41ab61638b6e70991ff400c0f03e17d91c287c053e38a15b06c071a
> >
> > Staging site:
> >
> https://maven.apache.org/shared-archives/maven-script-interpreter-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > --
> > Sławomir Jaranowski
> >
>
>
> --
> Sławomir Jaranowski
>

Re: [VOTE] Release Apache Maven Script Interpreter version 1.6

2024-04-30 Thread Slawomir Jaranowski 
+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=12354488
>
> There are no more issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-script-interpreter
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2105/
>
> https://repository.apache.org/content/repositories/maven-2105/org/apache/maven/shared/maven-script-interpreter/1.6/maven-script-interpreter-1.6-source-release.zip
>
> Source release checksum(s):
> maven-script-interpreter-1.6-source-release.zip - SHA-512 :
> 328a0a033952e6cecb264bf02198808c08e04b05165a72dd3bd168415055703bae1a6732c41ab61638b6e70991ff400c0f03e17d91c287c053e38a15b06c071a
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-script-interpreter-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Sławomir Jaranowski
>


-- 
Sławomir Jaranowski

Re: [VOTE] Release Apache Maven Reporting Exec version 2.0.0-M13

2024-04-30 Thread Sylwester Lachiewicz 
+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=12354403
> >
> > 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%20maven-reporting-exec
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-2104/
> >
> https://repository.apache.org/content/repositories/maven-2104/org/apache/maven/reporting/maven-reporting-exec/2.0.0-M13/maven-reporting-exec-2.0.0-M13-source-release.zip
> >
> > Source release checksum(s):
> > maven-reporting-exec-2.0.0-M13-source-release.zip
> > sha512:
> >
> db391937e803543b190ed879ccec6c214041f5c40bbd9a7593097fc56037a1f0b22f68cf924ce1b7f584573f4bc89b0716e76e6d1fd01650eb52dbca686adf3a
> >
> > Staging site:
> > https://maven.apache.org/shared-archives/maven-reporting-exec-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Publish Via the Central Portal

2024-04-30 Thread Andres Almiray 
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/publish/publish-portal-api/
Sonatype's plugin may not offer source code but JReleaser does. However,
it's implementation relies on Feign. You may study and adapt the code if
you feel like it, after all it's licensed under ASL v2

https://github.com/jreleaser/jreleaser/tree/main/sdks/jreleaser-mavencentral-java-sdk

Cheers,
Andres

---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Tue, Apr 30, 2024 at 12:05 PM Romain Manni-Bucau 
wrote:

> 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 us making it obvious it will fail but
> I think it will be fixed for the final GA release.
>
> So from my small window there is no concern even if most of us using
> central outside the asf will be impacted sometime next year probably.
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le mar. 30 avr. 2024 à 10:32, Slawomir Jaranowski 
> a écrit :
>
> > 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 nexus-staging-maven-plugin and still use maven-compat ...
> > Probably it will have a problem with Maven 4 ...
> > Also Sonatype did not publish a source code for it ...
> >
> >
> https://central.sonatype.com/artifact/org.sonatype.central/central-publishing-maven-plugin
> >
> > Also Sonatype did not publish a source code for it ...
> >
> > It also looks as standard Maven deployment will not work with the new
> > Central Portal API.
> >
> > I'm surprised that Sonatype did not consult or even announce such a new
> way
> > with the Maven community.
> >
> > --
> > Sławomir Jaranowski
> >
>

Re: Publish Via the Central Portal

2024-04-30 Thread Romain Manni-Bucau 
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 us making it obvious it will fail but
I think it will be fixed for the final GA release.

So from my small window there is no concern even if most of us using
central outside the asf will be impacted sometime next year probably.

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le mar. 30 avr. 2024 à 10:32, Slawomir Jaranowski 
a écrit :

> 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 nexus-staging-maven-plugin and still use maven-compat ...
> Probably it will have a problem with Maven 4 ...
> Also Sonatype did not publish a source code for it ...
>
> https://central.sonatype.com/artifact/org.sonatype.central/central-publishing-maven-plugin
>
> Also Sonatype did not publish a source code for it ...
>
> It also looks as standard Maven deployment will not work with the new
> Central Portal API.
>
> I'm surprised that Sonatype did not consult or even announce such a new way
> with the Maven community.
>
> --
> Sławomir Jaranowski
>

Publish Via the Central Portal

2024-04-30 Thread Slawomir Jaranowski 
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 nexus-staging-maven-plugin and still use maven-compat ...
Probably it will have a problem with Maven 4 ...
Also Sonatype did not publish a source code for it ...
https://central.sonatype.com/artifact/org.sonatype.central/central-publishing-maven-plugin

Also Sonatype did not publish a source code for it ...

It also looks as standard Maven deployment will not work with the new
Central Portal API.

I'm surprised that Sonatype did not consult or even announce such a new way
with the Maven community.

-- 
Sławomir Jaranowski

Re: [VOTE] Release Apache Maven Reporting Exec version 2.0.0-M13

2024-04-30 Thread Michael Osipov 
+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=12354403
> 
> 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%20maven-reporting-exec
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2104/
> https://repository.apache.org/content/repositories/maven-2104/org/apache/maven/reporting/maven-reporting-exec/2.0.0-M13/maven-reporting-exec-2.0.0-M13-source-release.zip
> 
> Source release checksum(s):
> maven-reporting-exec-2.0.0-M13-source-release.zip
> sha512: 
> db391937e803543b190ed879ccec6c214041f5c40bbd9a7593097fc56037a1f0b22f68cf924ce1b7f584573f4bc89b0716e76e6d1fd01650eb52dbca686adf3a
> 
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-exec-LATEST/
> 
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: maven-compat removal?

2024-04-30 Thread Herve Boutemy 
it's part of the wider Maven Ecosystem Cleanup plan
https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup

Regards,

Hervé

On 2024/04/30 00:01:57 Olivier Lamy wrote:
> Hi,
> I can see plenty of PRs with maven-compat removal.
> Maybe this could be explained and so more people could help for this task?
> 
> cheers
> Olivier
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org