Re: Halve the logging

[Romain Manni-Bucau]

Maybe we should just move the console listener to a logger usage with this
pattern $classname.event, this way configuring the loggers enables any
customization and we dont get fishy console outputs too depending the slf4j
binding.

Le dim. 19 févr. 2023 à 20:57, Benjamin Marwell  a
écrit :

> Sadly, --ntp also disables upload progress and ANY information associated
> with this.
> Maybe it would be beneficial to have an option for that.
>
>
>
>
> On Sun, 19 Feb 2023, 18:26 Michael Osipov,  wrote:
>
> > Am 2023-02-19 um 18:17 schrieb Romain Manni-Bucau:
> > > Not sure we can find an agreement on this topic, both opinions are very
> > > valid and depends the persona/case so let's keep our default while it
> is
> > > customizable easily it is fine IMHO.
> >
> > Good point, I could imagine that one could introduce --transfer-progress
> > , similar Tamás did with Resolver transports.
> >
> >
>

Re: [VOTE] Release Maven Plugin Tools 3.8.0

[Michael Osipov]

Am 2023-02-19 um 20:59 schrieb Guillaume Nodet:

Le dim. 19 févr. 2023 à 17:18, Michael Osipov  a
écrit :


Am 2023-02-18 um 11:34 schrieb Michael Osipov:

Am 2023-02-15 um 21:22 schrieb Guillaume Nodet:

I've staged a release candidate for Maven Plugin Tools 3.8.0.
The goal is to provide some initial support for plugins using the maven

4

api provided by maven 4.0.0-alpha-4.  The plugin can be used for both

3.x

and 4.x plugins, so there's no major version bump.

Release notes:



https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12352545


Staging repository:
https://repository.apache.org/content/repositories/maven-1875

Staging site:
https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/


I have to remove my vote and give a clear -1:
https://issues.apache.org/jira/browse/MPLUGIN-414

I have clearly written:

This change can only happen when the entire Doxia Stack moves to

Velocity 2.3 because it would override the transitive dep of Doxia Site
Renderer.

This must be reverted.



I missed that.  Could you explain why changing dependency in m-plugin-tools
would directly affect released versions of the site renderer ?  Or is that
for future versions that would also upgrade to this newer m-plugin-tools ?


Here is the problem:

[INFO] < org.apache.maven.plugins:maven-plugin-report-plugin >-
[INFO] Building Maven Plugin Report Plugin 3.8.1-SNAPSHOT   [14/14]
[INFO] [ maven-plugin ]
Downloading from apache.snapshots: 
https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-plugin-plugin/3.8.1-SNAPSHOT/maven-metadata.xml
Downloaded from apache.snapshots: 
https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-plugin-plugin/3.8.1-SNAPSHOT/maven-metadata.xml
 (793 B at 3.2 kB/s)
[INFO]
[INFO] --- maven-dependency-plugin:3.4.0:tree (default-cli) @ 
maven-plugin-report-plugin ---
...
[INFO] +- 
org.apache.maven.plugin-tools:maven-plugin-tools-generators:jar:3.8.1-SNAPSHOT:compile
[INFO] |  +- org.codehaus.plexus:plexus-velocity:jar:2.0:compile
[INFO] |  +- org.apache.velocity:velocity-engine-core:jar:2.3:compile
...
[INFO] +- org.apache.maven.reporting:maven-reporting-impl:jar:3.2.0:compile
[INFO] |  +- org.apache.maven.shared:maven-shared-utils:jar:3.3.4:compile
[INFO] |  |  \- commons-io:commons-io:jar:2.6:compile
[INFO] |  +- org.apache.maven.doxia:doxia-decoration-model:jar:1.11.1:compile
[INFO] |  +- org.apache.maven.doxia:doxia-core:jar:1.11.1:compile
[INFO] |  |  \- org.apache.commons:commons-text:jar:1.3:compile
[INFO] |  +- org.apache.maven.doxia:doxia-integration-tools:jar:1.11.1:compile
[INFO] |  |  \- org.codehaus.plexus:plexus-i18n:jar:1.0-beta-10:compile
[INFO] |  \- org.apache.maven.doxia:doxia-site-renderer:jar:1.11.1:compile
[INFO] | +- org.apache.maven.doxia:doxia-skin-model:jar:1.11.1:compile
[INFO] | +- org.apache.maven.doxia:doxia-module-xhtml:jar:1.11.1:compile
[INFO] | +- org.apache.maven.doxia:doxia-module-xhtml5:jar:1.11.1:compile
[INFO] | +- org.apache.velocity:velocity:jar:1.7:compile
[INFO] | |  \- commons-lang:commons-lang:jar:2.4:compile
[INFO] | +- org.apache.velocity:velocity-tools:jar:2.0:compile
...


You now have Velocity twice on the classpath. This will lead to any kind 
of funny behavior, failure, etc. Doxia Sitetools 1.x isn't supported 
with Velocity Engine 2.x, so aren't Velocity Tools 2.0.


Here is the exact same issue with JXR: 
https://issues.apache.org/jira/browse/JXR-166. Read the other related 
issues please.


M

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

Re: [VOTE] Release Maven Plugin Tools 3.8.0

[Guillaume Nodet]

Le dim. 19 févr. 2023 à 17:18, Michael Osipov  a
écrit :

> Am 2023-02-18 um 11:34 schrieb Michael Osipov:
> > Am 2023-02-15 um 21:22 schrieb Guillaume Nodet:
> >> I've staged a release candidate for Maven Plugin Tools 3.8.0.
> >> The goal is to provide some initial support for plugins using the maven
> 4
> >> api provided by maven 4.0.0-alpha-4.  The plugin can be used for both
> 3.x
> >> and 4.x plugins, so there's no major version bump.
> >>
> >> Release notes:
> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12352545
> >>
> >> Staging repository:
> >>https://repository.apache.org/content/repositories/maven-1875
> >>
> >> Staging site:
> >>https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/
>
> I have to remove my vote and give a clear -1:
> https://issues.apache.org/jira/browse/MPLUGIN-414
>
> I have clearly written:
> > This change can only happen when the entire Doxia Stack moves to
> Velocity 2.3 because it would override the transitive dep of Doxia Site
> Renderer.
>
> This must be reverted.
>

I missed that.  Could you explain why changing dependency in m-plugin-tools
would directly affect released versions of the site renderer ?  Or is that
for future versions that would also upgrade to this newer m-plugin-tools ?

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


-- 

Guillaume Nodet

Re: Halve the logging

[Benjamin Marwell]

Sadly, --ntp also disables upload progress and ANY information associated
with this.
Maybe it would be beneficial to have an option for that.




On Sun, 19 Feb 2023, 18:26 Michael Osipov,  wrote:

> Am 2023-02-19 um 18:17 schrieb Romain Manni-Bucau:
> > Not sure we can find an agreement on this topic, both opinions are very
> > valid and depends the persona/case so let's keep our default while it is
> > customizable easily it is fine IMHO.
>
> Good point, I could imagine that one could introduce --transfer-progress
> , similar Tamás did with Resolver transports.
>
>

Re: Halve the logging

[Michael Osipov]

Am 2023-02-19 um 18:17 schrieb Romain Manni-Bucau:

Not sure we can find an agreement on this topic, both opinions are very
valid and depends the persona/case so let's keep our default while it is
customizable easily it is fine IMHO.


Good point, I could imagine that one could introduce --transfer-progress 
, similar Tamás did with Resolver transports.

Re: Halve the logging

[Romain Manni-Bucau]

Not sure we can find an agreement on this topic, both opinions are very
valid and depends the persona/case so let's keep our default while it is
customizable easily it is fine IMHO.

Le dim. 19 févr. 2023 à 17:06, Elliotte Rusty Harold  a
écrit :

> On Sun, Feb 19, 2023 at 2:02 PM Michael Osipov 
> wrote:
>
> > Use -B or --no-transfer-progress. Cutting in half does not really work
> > unless you don't want to say that download has started and finished *or*
> > you provide a custom status listener. Consider that download starts, but
> > then fails. No way to track that.
> >
> >
>
> Sure there is. Just log a message that the download failed. As is,
> Maven spews far too much log junk making it very hard to find real
> problems. No output for non-error conditions should be the default
> behavior. But this example is especially egregious.
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Maven Plugin Testing 4.0.0-alpha-1

[Hervé Boutemy]

+1

Reproducible Builds ok: reference done with JDK 17 on *nix

Regards,

Hervé

Le mercredi 15 février 2023, 21:19:23 CET Guillaume Nodet a écrit :
> I've staged a candidate release for Maven Plugin Testing 4.0.0-alpha-1.
> The goal of this release is to provide a first set of classes to test
> plugins using the v4 api, mainly using the package at
> https://maven.apache.org/plugin-testing-archives/LATEST/maven-plugin-testing
> -harness/apidocs/org/apache/maven/api/plugin/testing/package-summary.html
> and the provided junit 5 extension.  An example usage of this extension is
> available at
> https://github.com/gnodet/maven-install-plugin/blob/m-api/src/test/java/org/
> apache/maven/plugins/install/InstallMojoTest.java Those classes are new
> classes in a new package, so there's no compatibility issue with all
> plugins using this component.
> 
> This component has not been released since a while.  The list of fixed
> issues is available at
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317720
> rsion=12352930
> 
> Staging repository:
>   https://repository.apache.org/content/repositories/maven-1874
> 
> Staging site:
>https://maven.apache.org/plugin-testing-archives/LATEST/
> 
> Please review and vote.





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

Re: [VOTE] Release Maven Plugin Tools 3.8.0

[Hervé Boutemy]

+1

Reproducible Builds ok: reference done with JDK 17 on *nix

Regards,

Hervé

Le mercredi 15 février 2023, 21:22:56 CET Guillaume Nodet a écrit :
> I've staged a release candidate for Maven Plugin Tools 3.8.0.
> The goal is to provide some initial support for plugins using the maven 4
> api provided by maven 4.0.0-alpha-4.  The plugin can be used for both 3.x
> and 4.x plugins, so there's no major version bump.
> 
> Release notes:
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820
> rsion=12352545
> 
> Staging repository:
>   https://repository.apache.org/content/repositories/maven-1875
> 
> Staging site:
>   https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/
> 
> Please review and vote !





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

Re: [VOTE] Release Maven Plugin Tools 3.8.0

[Michael Osipov]

Am 2023-02-18 um 11:34 schrieb Michael Osipov:

Am 2023-02-15 um 21:22 schrieb Guillaume Nodet:

I've staged a release candidate for Maven Plugin Tools 3.8.0.
The goal is to provide some initial support for plugins using the maven 4
api provided by maven 4.0.0-alpha-4.  The plugin can be used for both 3.x
and 4.x plugins, so there's no major version bump.

Release notes:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12352545

Staging repository:
   https://repository.apache.org/content/repositories/maven-1875

Staging site:
   https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/


I have to remove my vote and give a clear -1: 
https://issues.apache.org/jira/browse/MPLUGIN-414


I have clearly written:

This change can only happen when the entire Doxia Stack moves to Velocity 2.3 
because it would override the transitive dep of Doxia Site Renderer.


This must be reverted.

M





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

Re: Halve the logging

[Elliotte Rusty Harold]

On Sun, Feb 19, 2023 at 2:02 PM Michael Osipov  wrote:

> Use -B or --no-transfer-progress. Cutting in half does not really work
> unless you don't want to say that download has started and finished *or*
> you provide a custom status listener. Consider that download starts, but
> then fails. No way to track that.
>
>

Sure there is. Just log a message that the download failed. As is,
Maven spews far too much log junk making it very hard to find real
problems. No output for non-error conditions should be the default
behavior. But this example is especially egregious.

-- 
Elliotte Rusty Harold
elh...@ibiblio.org

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

Re: Halve the logging

[Gary Gregory]

Yeah, this is tricky IMO because I would rather know that something has
started and is taking a long time rather than staring at an apparently hung
console.

I think it is fine as it is now and --no-transfer-progress is helpful and
also -ntp work the same? AFK.

Gary

Gary

On Sun, Feb 19, 2023, 09:13 Tamás Cservenák  wrote:

> This is resolver, but the logging listener is provided by maven.
>
> I'd +1 for this, as message can be "Downloaded" or "Failed to
> download..." and imo line for starting of download is chatty, really not
> needed.
>
> T
>
> On Sun, Feb 19, 2023, 14:59 Elliotte Rusty Harold 
> wrote:
>
> > Typical log message in build:
> >
> > Downloading from central:
> >
> >
> https://repo.maven.apache.org/maven2/commons-lang/commons-lang/2.4/commons-lang-2.4.pom
> > Downloaded from central:
> >
> >
> https://repo.maven.apache.org/maven2/commons-lang/commons-lang/2.4/commons-lang-2.4.pom
> > (14 kB at 776 kB/s)
> >
> > Which plugin does this come from? Could we kill one of these messages
> > to cut the number of log line junk in half?
> >
> > --
> > Elliotte Rusty Harold
> > elh...@ibiblio.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: [VOTE] Release Apache Maven Assembly Plugin version 3.5.0

[Sylwester Lachiewicz]

+1

niedz., 19 lut 2023, 16:27 użytkownik Michael Osipov 
napisał:

> Am 2023-02-19 um 16:16 schrieb Hervé Boutemy:
> > Hi,
> >
> > We solved 1 issue:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12352065=Text
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1876/
> >
> https://repository.apache.org/content/repositories/maven-1876/org/apache/maven/plugins/maven-assembly-plugin/3.5.0/maven-assembly-plugin-3.5.0-source-release.zip
> >
> > Source release checksum(s):
> > maven-assembly-plugin-3.5.0-source-release.zip sha512:
> 1447cfa62f9a48b9c7f87ba9754789408d30690e168c49dbcae9f0dc6e35fd47c17879be05bcac2363e2bdfa55dd9396acd6562f6a4e9b8604d1719df4abde15
> >
> > Staging site:
> > https://maven.apache.org/plugins-archives/maven-assembly-plugin-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for at least 72 hours.
>
> +1
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

Re: [VOTE] Release Apache Maven Assembly Plugin version 3.5.0

[Michael Osipov]

Am 2023-02-19 um 16:16 schrieb Hervé Boutemy:

Hi,

We solved 1 issue:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12352065=Text

Staging repo:
https://repository.apache.org/content/repositories/maven-1876/
https://repository.apache.org/content/repositories/maven-1876/org/apache/maven/plugins/maven-assembly-plugin/3.5.0/maven-assembly-plugin-3.5.0-source-release.zip

Source release checksum(s):
maven-assembly-plugin-3.5.0-source-release.zip sha512: 
1447cfa62f9a48b9c7f87ba9754789408d30690e168c49dbcae9f0dc6e35fd47c17879be05bcac2363e2bdfa55dd9396acd6562f6a4e9b8604d1719df4abde15

Staging site:
https://maven.apache.org/plugins-archives/maven-assembly-plugin-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.


+1


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

[VOTE] Release Apache Maven Assembly Plugin version 3.5.0

[Hervé Boutemy]

Hi,

We solved 1 issue:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12352065=Text

Staging repo:
https://repository.apache.org/content/repositories/maven-1876/
https://repository.apache.org/content/repositories/maven-1876/org/apache/maven/plugins/maven-assembly-plugin/3.5.0/maven-assembly-plugin-3.5.0-source-release.zip

Source release checksum(s):
maven-assembly-plugin-3.5.0-source-release.zip sha512: 
1447cfa62f9a48b9c7f87ba9754789408d30690e168c49dbcae9f0dc6e35fd47c17879be05bcac2363e2bdfa55dd9396acd6562f6a4e9b8604d1719df4abde15

Staging site:
https://maven.apache.org/plugins-archives/maven-assembly-plugin-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




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

Re: Halve the logging

[Tamás Cservenák]

This is resolver, but the logging listener is provided by maven.

I'd +1 for this, as message can be "Downloaded" or "Failed to
download..." and imo line for starting of download is chatty, really not
needed.

T

On Sun, Feb 19, 2023, 14:59 Elliotte Rusty Harold 
wrote:

> Typical log message in build:
>
> Downloading from central:
>
> https://repo.maven.apache.org/maven2/commons-lang/commons-lang/2.4/commons-lang-2.4.pom
> Downloaded from central:
>
> https://repo.maven.apache.org/maven2/commons-lang/commons-lang/2.4/commons-lang-2.4.pom
> (14 kB at 776 kB/s)
>
> Which plugin does this come from? Could we kill one of these messages
> to cut the number of log line junk in half?
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Halve the logging

[Michael Osipov]

Am 2023-02-19 um 14:58 schrieb Elliotte Rusty Harold:

Typical log message in build:

Downloading from central:
https://repo.maven.apache.org/maven2/commons-lang/commons-lang/2.4/commons-lang-2.4.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/commons-lang/commons-lang/2.4/commons-lang-2.4.pom
(14 kB at 776 kB/s)

Which plugin does this come from? Could we kill one of these messages
to cut the number of log line junk in half?


Use -B or --no-transfer-progress. Cutting in half does not really work 
unless you don't want to say that download has started and finished *or* 
you provide a custom status listener. Consider that download starts, but 
then fails. No way to track that.



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

Halve the logging

[Elliotte Rusty Harold]

Typical log message in build:

Downloading from central:
https://repo.maven.apache.org/maven2/commons-lang/commons-lang/2.4/commons-lang-2.4.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/commons-lang/commons-lang/2.4/commons-lang-2.4.pom
(14 kB at 776 kB/s)

Which plugin does this come from? Could we kill one of these messages
to cut the number of log line junk in half?

-- 
Elliotte Rusty Harold
elh...@ibiblio.org

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

Re: Reverted a lot of commits on apache maven-site master

[Slawomir Jaranowski]

Anchors are still broken ... on many site like:
https://maven.apache.org/guides/plugin/guide-java-plugin-development.html

Even worse, we lost the last content changes ...

niedz., 19 lut 2023 o 14:26 Michael Osipov  napisał(a):

> Am 2023-02-19 um 13:45 schrieb Karl Heinz Marbaise:
> > Hi,
> >
> > short question why are so many reverts done  on the apache site master?
> >
> >
> >   from d7db85d3 (doc) added snippet types
> >   new f3f37282 Revert "(doc) added snippet types"
> >   new 763c0ed3 Revert "(doc) lint markdown files"
> >   new b0eb56dd Revert "[MNGSITE-509] Fix linking to anchors"
> >   new 55d05632 Revert "[MNGSITE-509] Fix linking in
> > introduction-to-the-lifecycle.md"
> >   new 917e15fd Revert "Refresh - Guide to Developing Java Plugins"
> >   new 591a1fd2 Revert "many plugins released"
> >   new 7d348a3e Revert "reformt"
> >   new be357c6d Revert "fix JIRA link, reformt"
> >   new 7bafdd42 Revert "Maven Reporting Impl 4.0.0-M4 released"
> >   new 03e99ad1 Revert "use directory, not folder"
> >   new 9c5f1ff1 Revert "surefire 3.0.0-M9"
> >   new 10d6f9d9 Revert "[MNGSITE-507] [DOXIA-692] Improve conversion
> > results - part2"
> >   new c61f169d Revert "[MNGSITE-507] [DOXIA-692] Improve conversion
> > results"
> >   new 656d36f2 Revert "[MNGSITE-507] Converted .apt documents to
> > Markdown"
> >
> >
> > Can someone explain that... what is the reason for reverting so many
> > commits on the site?
>
> Automated mess. I dare to say that we need a hard reset on master here.
>
>

-- 
Sławomir Jaranowski

Re: Reverted a lot of commits on apache maven-site master

[Sylwester Lachiewicz]

Hi,
I've merged conversion from apt to markdown and after some time we agrees
on Slack that there are many issues to be resolved on doxia/doxia convert
projects so best would be to revert those changes and make another, proper
round of review later.

Sylwester

niedz., 19 lut 2023, 13:46 użytkownik Karl Heinz Marbaise 
napisał:

> Hi,
>
> short question why are so many reverts done  on the apache site master?
>
>
>   from d7db85d3 (doc) added snippet types
>   new f3f37282 Revert "(doc) added snippet types"
>   new 763c0ed3 Revert "(doc) lint markdown files"
>   new b0eb56dd Revert "[MNGSITE-509] Fix linking to anchors"
>   new 55d05632 Revert "[MNGSITE-509] Fix linking in
> introduction-to-the-lifecycle.md"
>   new 917e15fd Revert "Refresh - Guide to Developing Java Plugins"
>   new 591a1fd2 Revert "many plugins released"
>   new 7d348a3e Revert "reformt"
>   new be357c6d Revert "fix JIRA link, reformt"
>   new 7bafdd42 Revert "Maven Reporting Impl 4.0.0-M4 released"
>   new 03e99ad1 Revert "use directory, not folder"
>   new 9c5f1ff1 Revert "surefire 3.0.0-M9"
>   new 10d6f9d9 Revert "[MNGSITE-507] [DOXIA-692] Improve conversion
> results - part2"
>   new c61f169d Revert "[MNGSITE-507] [DOXIA-692] Improve conversion
> results"
>   new 656d36f2 Revert "[MNGSITE-507] Converted .apt documents to
> Markdown"
>
>
> Can someone explain that... what is the reason for reverting so many
> commits on the site?
>
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Reverted a lot of commits on apache maven-site master

[Michael Osipov]

Am 2023-02-19 um 13:45 schrieb Karl Heinz Marbaise:

Hi,

short question why are so many reverts done  on the apache site master?


  from d7db85d3 (doc) added snippet types
  new f3f37282 Revert "(doc) added snippet types"
  new 763c0ed3 Revert "(doc) lint markdown files"
  new b0eb56dd Revert "[MNGSITE-509] Fix linking to anchors"
  new 55d05632 Revert "[MNGSITE-509] Fix linking in
introduction-to-the-lifecycle.md"
  new 917e15fd Revert "Refresh - Guide to Developing Java Plugins"
  new 591a1fd2 Revert "many plugins released"
  new 7d348a3e Revert "reformt"
  new be357c6d Revert "fix JIRA link, reformt"
  new 7bafdd42 Revert "Maven Reporting Impl 4.0.0-M4 released"
  new 03e99ad1 Revert "use directory, not folder"
  new 9c5f1ff1 Revert "surefire 3.0.0-M9"
  new 10d6f9d9 Revert "[MNGSITE-507] [DOXIA-692] Improve conversion
results - part2"
  new c61f169d Revert "[MNGSITE-507] [DOXIA-692] Improve conversion
results"
  new 656d36f2 Revert "[MNGSITE-507] Converted .apt documents to
Markdown"


Can someone explain that... what is the reason for reverting so many
commits on the site?


Automated mess. I dare to say that we need a hard reset on master here.

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Michael Osipov]

Am 2023-02-19 um 12:43 schrieb Slawomir Jaranowski:

Another question is what does 3.8.x mean?

Eg for specific plugin should we maintain matrix of all ... from 3.8.1 to
3.8.7 and so on, or simply say that the latest version from 3.8.x

So when a bug occurs in plugin X with Maven 3.8.5, but not in the same
plugin X with 3.8.7 - what we should do ... do a workaround, hack in plugin
X to mitigate bugs from Maven 3.8.5?


My understanding:
* We can absolutely require to upgrade to a new patch version of Maven
* We guarantee API compat, at the moment, not runtime compat. If there 
is a change in behavior in a plugin in regards to a Maven version, it 
has to be a case by case decision how to proceed further. Maybe a needed 
fix was applied to Maven, granted. If the behavior in the plugin has 
been changed which violates its interaction with Maven, then it's the 
plugin's fault. There is not black an white for me.



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

Reverted a lot of commits on apache maven-site master

[Karl Heinz Marbaise]

Hi,

short question why are so many reverts done  on the apache site master?


 from d7db85d3 (doc) added snippet types
 new f3f37282 Revert "(doc) added snippet types"
 new 763c0ed3 Revert "(doc) lint markdown files"
 new b0eb56dd Revert "[MNGSITE-509] Fix linking to anchors"
 new 55d05632 Revert "[MNGSITE-509] Fix linking in
introduction-to-the-lifecycle.md"
 new 917e15fd Revert "Refresh - Guide to Developing Java Plugins"
 new 591a1fd2 Revert "many plugins released"
 new 7d348a3e Revert "reformt"
 new be357c6d Revert "fix JIRA link, reformt"
 new 7bafdd42 Revert "Maven Reporting Impl 4.0.0-M4 released"
 new 03e99ad1 Revert "use directory, not folder"
 new 9c5f1ff1 Revert "surefire 3.0.0-M9"
 new 10d6f9d9 Revert "[MNGSITE-507] [DOXIA-692] Improve conversion
results - part2"
 new c61f169d Revert "[MNGSITE-507] [DOXIA-692] Improve conversion
results"
 new 656d36f2 Revert "[MNGSITE-507] Converted .apt documents to
Markdown"


Can someone explain that... what is the reason for reverting so many
commits on the site?


Kind regards
Karl Heinz Marbaise

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

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Olivier Lamy]

On Sun, 19 Feb 2023 at 9:24 pm, Sylwester Lachiewicz 
wrote:

> I hope this is question to community & Maven PMC, right?
>
> I think we all trying best to test Maven 3.9.


I haven’t said the opposite.
I’m just saying generally version x.0 could not be really considered as
stable especially without beta or alpha first


Furthermore my question concern a more general policy about what versions
do we support.


> Sylwester
>
> niedz., 19 lut 2023, 12:21 użytkownik Olivier Lamy 
> napisał:
>
> > On Sun, 19 Feb 2023 at 9:12 pm, Sylwester Lachiewicz <
> > slachiew...@gmail.com>
> > wrote:
> >
> > > From our Maven Download page:
> > >
> > > Downloading Apache Maven 3.9.0
> > >
> > > Apache Maven 3.9.0 is the latest release and recommended version for
> all
> > > users.
> > >
> > >
> > > On the history page we have only information that Maven 3.0 is EOL.
> > >
> > > https://maven.apache.org/docs/history.html
> >
> >
> > But not 3.2.5 3.3.3 etc…
> > What should we marked EOL as well?
> > Everything up to 3.8.6?
> >
> > 
> > >
> > >
> > > br
> > >
> > > Sylwester
> > >
> > > niedz., 19 lut 2023 o 12:04 Olivier Lamy 
> napisał(a):
> > >
> > > > On Sun, 19 Feb 2023 at 8:59 pm, Sylwester Lachiewicz <
> > > > slachiew...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > > I think so far we support all maven versions from 3.2.5+ and
> nothing
> > > has
> > > > > changed yet.
> > > > >
> > > > > If we have issue with specific Maven version and plugin we can
> > > add/change
> > > > > used Maven in GH action. Ofc we should use donated resources from
> > > GitHub
> > > > > effectively.
> > > > >
> > > > > I believe now focus is to test all our plugins and shared libs with
> > our
> > > > > latest and recommend Maven 3.9?
> > > >
> > > >
> > > > It might be a bit early to recommend 3.9.0?
> > > > We should probably think about what do we really support?
> > > > 3.8.x and 3.9.x?
> > > > But first what do we mean by “support”?
> > > >
> > > >
> > > > >
> > > > > Sylwester
> > > > >
> > > > > niedz., 19 lut 2023, 11:49 użytkownik Olivier Lamy <
> ol...@apache.org
> > >
> > > > > napisał:
> > > > >
> > > > > > Typically this issue is a problem on what core version do we
> > > support..
> > > > > > https://issues.apache.org/jira/browse/MENFORCER-468
> > > > > >
> > > > > > The new code is not working with 3.8.x
> > > > > >
> > > > > > On Sun, 19 Feb 2023 at 1:58 pm, Olivier Lamy 
> > > wrote:
> > > > > >
> > > > > > > This change means we do not have any more gha running with
> > anything
> > > > > > > else than 3.9.0
> > > > > > > can I understand this as an implicit we do not support anything
> > > > <3.9.0?
> > > > > > > I can't find any documentation on the website related to the
> > > > > > > version(s) we support EOL etc...
> > > > > > > Should we have some documentation to make this EOL policy
> really
> > > > clear?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Fri, 10 Feb 2023 at 06:15,  wrote:
> > > > > > > >
> > > > > > > > This is an automated email from the ASF dual-hosted git
> > > repository.
> > > > > > > >
> > > > > > > > slachiewicz pushed a commit to branch v3
> > > > > > > > in repository
> > > > > > >
> https://gitbox.apache.org/repos/asf/maven-gh-actions-shared.git
> > > > > > > >
> > > > > > > >
> > > > > > > > The following commit(s) were added to refs/heads/v3 by this
> > push:
> > > > > > > >  new 907  Switch to Maven 3.9.0
> > > > > > > > 907 is described below
> > > > > > > >
> > > > > > > > commit 9073820ea078880a0f4edc7ce2000ea4ade4
> > > > > > > > Author: Sylwester Lachiewicz 
> > > > > > > > AuthorDate: Thu Feb 9 21:15:09 2023 +0100
> > > > > > > >
> > > > > > > > Switch to Maven 3.9.0
> > > > > > > > ---
> > > > > > > >  .github/workflows/maven-verify.yml | 2 +-
> > > > > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > > > > >
> > > > > > > > diff --git a/.github/workflows/maven-verify.yml
> > > > > > > b/.github/workflows/maven-verify.yml
> > > > > > > > index 654b5b9..471053f 100644
> > > > > > > > --- a/.github/workflows/maven-verify.yml
> > > > > > > > +++ b/.github/workflows/maven-verify.yml
> > > > > > > > @@ -84,7 +84,7 @@ on:
> > > > > > > >ff-maven:
> > > > > > > >  description: The Maven version used during
> > > fail-fast-build
> > > > > job
> > > > > > > >  required: false
> > > > > > > > -default: '3.8.7'
> > > > > > > > +default: '3.9.0'
> > > > > > > >  type: string
> > > > > > > >
> > > > > > > >ff-jdk:
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Slawomir Jaranowski]

Another question is what does 3.8.x mean?

Eg for specific plugin should we maintain matrix of all ... from 3.8.1 to
3.8.7 and so on, or simply say that the latest version from 3.8.x

So when a bug occurs in plugin X with Maven 3.8.5, but not in the same
plugin X with 3.8.7 - what we should do ... do a workaround, hack in plugin
X to mitigate bugs from Maven 3.8.5?


niedz., 19 lut 2023 o 12:28 Michael Osipov  napisał(a):

> Am 2023-02-19 um 12:20 schrieb Olivier Lamy:
> > On Sun, 19 Feb 2023 at 9:12 pm, Sylwester Lachiewicz <
> slachiew...@gmail.com>
> > wrote:
> >
> >>  From our Maven Download page:
> >>
> >> Downloading Apache Maven 3.9.0
> >>
> >> Apache Maven 3.9.0 is the latest release and recommended version for all
> >> users.
> >>
> >>
> >> On the history page we have only information that Maven 3.0 is EOL.
> >>
> >> https://maven.apache.org/docs/history.html
> >
> >
> > But not 3.2.5 3.3.3 etc…
> > What should we marked EOL as well?
> > Everything up to 3.8.6?
> >
> > 
>
> I think, yes. Everything before 3.2.5 must be marked as EOL. As soon as
> we start raising the bar to 3.5.4 (first Resolver) version, then
> everything before 3.5.4 should be marked as EOL. I guess the first can
> be done in March (3.2.5+), the second one somewhere in the second half
> of the year. This will give everyone a reasonable timeframe to react.
>
> M
>
>

-- 
Sławomir Jaranowski

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Michael Osipov]

Am 2023-02-19 um 12:20 schrieb Olivier Lamy:

On Sun, 19 Feb 2023 at 9:12 pm, Sylwester Lachiewicz 
wrote:


 From our Maven Download page:

Downloading Apache Maven 3.9.0

Apache Maven 3.9.0 is the latest release and recommended version for all
users.


On the history page we have only information that Maven 3.0 is EOL.

https://maven.apache.org/docs/history.html



But not 3.2.5 3.3.3 etc…
What should we marked EOL as well?
Everything up to 3.8.6?




I think, yes. Everything before 3.2.5 must be marked as EOL. As soon as 
we start raising the bar to 3.5.4 (first Resolver) version, then 
everything before 3.5.4 should be marked as EOL. I guess the first can 
be done in March (3.2.5+), the second one somewhere in the second half 
of the year. This will give everyone a reasonable timeframe to react.


M

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Sylwester Lachiewicz]

I hope this is question to community & Maven PMC, right?

I think we all trying best to test Maven 3.9.
Sylwester

niedz., 19 lut 2023, 12:21 użytkownik Olivier Lamy 
napisał:

> On Sun, 19 Feb 2023 at 9:12 pm, Sylwester Lachiewicz <
> slachiew...@gmail.com>
> wrote:
>
> > From our Maven Download page:
> >
> > Downloading Apache Maven 3.9.0
> >
> > Apache Maven 3.9.0 is the latest release and recommended version for all
> > users.
> >
> >
> > On the history page we have only information that Maven 3.0 is EOL.
> >
> > https://maven.apache.org/docs/history.html
>
>
> But not 3.2.5 3.3.3 etc…
> What should we marked EOL as well?
> Everything up to 3.8.6?
>
> 
> >
> >
> > br
> >
> > Sylwester
> >
> > niedz., 19 lut 2023 o 12:04 Olivier Lamy  napisał(a):
> >
> > > On Sun, 19 Feb 2023 at 8:59 pm, Sylwester Lachiewicz <
> > > slachiew...@gmail.com>
> > > wrote:
> > >
> > > > Hi,
> > > > I think so far we support all maven versions from 3.2.5+ and nothing
> > has
> > > > changed yet.
> > > >
> > > > If we have issue with specific Maven version and plugin we can
> > add/change
> > > > used Maven in GH action. Ofc we should use donated resources from
> > GitHub
> > > > effectively.
> > > >
> > > > I believe now focus is to test all our plugins and shared libs with
> our
> > > > latest and recommend Maven 3.9?
> > >
> > >
> > > It might be a bit early to recommend 3.9.0?
> > > We should probably think about what do we really support?
> > > 3.8.x and 3.9.x?
> > > But first what do we mean by “support”?
> > >
> > >
> > > >
> > > > Sylwester
> > > >
> > > > niedz., 19 lut 2023, 11:49 użytkownik Olivier Lamy  >
> > > > napisał:
> > > >
> > > > > Typically this issue is a problem on what core version do we
> > support..
> > > > > https://issues.apache.org/jira/browse/MENFORCER-468
> > > > >
> > > > > The new code is not working with 3.8.x
> > > > >
> > > > > On Sun, 19 Feb 2023 at 1:58 pm, Olivier Lamy 
> > wrote:
> > > > >
> > > > > > This change means we do not have any more gha running with
> anything
> > > > > > else than 3.9.0
> > > > > > can I understand this as an implicit we do not support anything
> > > <3.9.0?
> > > > > > I can't find any documentation on the website related to the
> > > > > > version(s) we support EOL etc...
> > > > > > Should we have some documentation to make this EOL policy really
> > > clear?
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, 10 Feb 2023 at 06:15,  wrote:
> > > > > > >
> > > > > > > This is an automated email from the ASF dual-hosted git
> > repository.
> > > > > > >
> > > > > > > slachiewicz pushed a commit to branch v3
> > > > > > > in repository
> > > > > > https://gitbox.apache.org/repos/asf/maven-gh-actions-shared.git
> > > > > > >
> > > > > > >
> > > > > > > The following commit(s) were added to refs/heads/v3 by this
> push:
> > > > > > >  new 907  Switch to Maven 3.9.0
> > > > > > > 907 is described below
> > > > > > >
> > > > > > > commit 9073820ea078880a0f4edc7ce2000ea4ade4
> > > > > > > Author: Sylwester Lachiewicz 
> > > > > > > AuthorDate: Thu Feb 9 21:15:09 2023 +0100
> > > > > > >
> > > > > > > Switch to Maven 3.9.0
> > > > > > > ---
> > > > > > >  .github/workflows/maven-verify.yml | 2 +-
> > > > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > > > >
> > > > > > > diff --git a/.github/workflows/maven-verify.yml
> > > > > > b/.github/workflows/maven-verify.yml
> > > > > > > index 654b5b9..471053f 100644
> > > > > > > --- a/.github/workflows/maven-verify.yml
> > > > > > > +++ b/.github/workflows/maven-verify.yml
> > > > > > > @@ -84,7 +84,7 @@ on:
> > > > > > >ff-maven:
> > > > > > >  description: The Maven version used during
> > fail-fast-build
> > > > job
> > > > > > >  required: false
> > > > > > > -default: '3.8.7'
> > > > > > > +default: '3.9.0'
> > > > > > >  type: string
> > > > > > >
> > > > > > >ff-jdk:
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Olivier Lamy]

On Sun, 19 Feb 2023 at 9:12 pm, Sylwester Lachiewicz 
wrote:

> From our Maven Download page:
>
> Downloading Apache Maven 3.9.0
>
> Apache Maven 3.9.0 is the latest release and recommended version for all
> users.
>
>
> On the history page we have only information that Maven 3.0 is EOL.
>
> https://maven.apache.org/docs/history.html


But not 3.2.5 3.3.3 etc…
What should we marked EOL as well?
Everything up to 3.8.6?


>
>
> br
>
> Sylwester
>
> niedz., 19 lut 2023 o 12:04 Olivier Lamy  napisał(a):
>
> > On Sun, 19 Feb 2023 at 8:59 pm, Sylwester Lachiewicz <
> > slachiew...@gmail.com>
> > wrote:
> >
> > > Hi,
> > > I think so far we support all maven versions from 3.2.5+ and nothing
> has
> > > changed yet.
> > >
> > > If we have issue with specific Maven version and plugin we can
> add/change
> > > used Maven in GH action. Ofc we should use donated resources from
> GitHub
> > > effectively.
> > >
> > > I believe now focus is to test all our plugins and shared libs with our
> > > latest and recommend Maven 3.9?
> >
> >
> > It might be a bit early to recommend 3.9.0?
> > We should probably think about what do we really support?
> > 3.8.x and 3.9.x?
> > But first what do we mean by “support”?
> >
> >
> > >
> > > Sylwester
> > >
> > > niedz., 19 lut 2023, 11:49 użytkownik Olivier Lamy 
> > > napisał:
> > >
> > > > Typically this issue is a problem on what core version do we
> support..
> > > > https://issues.apache.org/jira/browse/MENFORCER-468
> > > >
> > > > The new code is not working with 3.8.x
> > > >
> > > > On Sun, 19 Feb 2023 at 1:58 pm, Olivier Lamy 
> wrote:
> > > >
> > > > > This change means we do not have any more gha running with anything
> > > > > else than 3.9.0
> > > > > can I understand this as an implicit we do not support anything
> > <3.9.0?
> > > > > I can't find any documentation on the website related to the
> > > > > version(s) we support EOL etc...
> > > > > Should we have some documentation to make this EOL policy really
> > clear?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Fri, 10 Feb 2023 at 06:15,  wrote:
> > > > > >
> > > > > > This is an automated email from the ASF dual-hosted git
> repository.
> > > > > >
> > > > > > slachiewicz pushed a commit to branch v3
> > > > > > in repository
> > > > > https://gitbox.apache.org/repos/asf/maven-gh-actions-shared.git
> > > > > >
> > > > > >
> > > > > > The following commit(s) were added to refs/heads/v3 by this push:
> > > > > >  new 907  Switch to Maven 3.9.0
> > > > > > 907 is described below
> > > > > >
> > > > > > commit 9073820ea078880a0f4edc7ce2000ea4ade4
> > > > > > Author: Sylwester Lachiewicz 
> > > > > > AuthorDate: Thu Feb 9 21:15:09 2023 +0100
> > > > > >
> > > > > > Switch to Maven 3.9.0
> > > > > > ---
> > > > > >  .github/workflows/maven-verify.yml | 2 +-
> > > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > > >
> > > > > > diff --git a/.github/workflows/maven-verify.yml
> > > > > b/.github/workflows/maven-verify.yml
> > > > > > index 654b5b9..471053f 100644
> > > > > > --- a/.github/workflows/maven-verify.yml
> > > > > > +++ b/.github/workflows/maven-verify.yml
> > > > > > @@ -84,7 +84,7 @@ on:
> > > > > >ff-maven:
> > > > > >  description: The Maven version used during
> fail-fast-build
> > > job
> > > > > >  required: false
> > > > > > -default: '3.8.7'
> > > > > > +default: '3.9.0'
> > > > > >  type: string
> > > > > >
> > > > > >ff-jdk:
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Michael Osipov]

Am 2023-02-19 um 12:12 schrieb Sylwester Lachiewicz:

From our Maven Download page:


Downloading Apache Maven 3.9.0

Apache Maven 3.9.0 is the latest release and recommended version for all
users.


Even if, it will require at least two iterations to iron out issues due 
to the amount of changes introduced in .0 release. Those, do not require 
Resolver 1.9.x features, I'd recommand to stay on 3.8.x for now.


Also looking at some open tickets now, 3.8.8 will and must also happen 
this quarter.


M


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

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Olivier Lamy]

On Sun, 19 Feb 2023 at 9:12 pm, Sylwester Lachiewicz 
wrote:

> From our Maven Download page:
>
> Downloading Apache Maven 3.9.0
>
> Apache Maven 3.9.0 is the latest release and recommended version for all
> users.


It’s just a template which has been changed without really thinking…
Do we really think we can consider 3.9.0 as really stable today?



>
> On the history page we have only information that Maven 3.0 is EOL.
>
> https://maven.apache.org/docs/history.html
>
>
> br
>
> Sylwester
>
> niedz., 19 lut 2023 o 12:04 Olivier Lamy  napisał(a):
>
> > On Sun, 19 Feb 2023 at 8:59 pm, Sylwester Lachiewicz <
> > slachiew...@gmail.com>
> > wrote:
> >
> > > Hi,
> > > I think so far we support all maven versions from 3.2.5+ and nothing
> has
> > > changed yet.
> > >
> > > If we have issue with specific Maven version and plugin we can
> add/change
> > > used Maven in GH action. Ofc we should use donated resources from
> GitHub
> > > effectively.
> > >
> > > I believe now focus is to test all our plugins and shared libs with our
> > > latest and recommend Maven 3.9?
> >
> >
> > It might be a bit early to recommend 3.9.0?
> > We should probably think about what do we really support?
> > 3.8.x and 3.9.x?
> > But first what do we mean by “support”?
> >
> >
> > >
> > > Sylwester
> > >
> > > niedz., 19 lut 2023, 11:49 użytkownik Olivier Lamy 
> > > napisał:
> > >
> > > > Typically this issue is a problem on what core version do we
> support..
> > > > https://issues.apache.org/jira/browse/MENFORCER-468
> > > >
> > > > The new code is not working with 3.8.x
> > > >
> > > > On Sun, 19 Feb 2023 at 1:58 pm, Olivier Lamy 
> wrote:
> > > >
> > > > > This change means we do not have any more gha running with anything
> > > > > else than 3.9.0
> > > > > can I understand this as an implicit we do not support anything
> > <3.9.0?
> > > > > I can't find any documentation on the website related to the
> > > > > version(s) we support EOL etc...
> > > > > Should we have some documentation to make this EOL policy really
> > clear?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Fri, 10 Feb 2023 at 06:15,  wrote:
> > > > > >
> > > > > > This is an automated email from the ASF dual-hosted git
> repository.
> > > > > >
> > > > > > slachiewicz pushed a commit to branch v3
> > > > > > in repository
> > > > > https://gitbox.apache.org/repos/asf/maven-gh-actions-shared.git
> > > > > >
> > > > > >
> > > > > > The following commit(s) were added to refs/heads/v3 by this push:
> > > > > >  new 907  Switch to Maven 3.9.0
> > > > > > 907 is described below
> > > > > >
> > > > > > commit 9073820ea078880a0f4edc7ce2000ea4ade4
> > > > > > Author: Sylwester Lachiewicz 
> > > > > > AuthorDate: Thu Feb 9 21:15:09 2023 +0100
> > > > > >
> > > > > > Switch to Maven 3.9.0
> > > > > > ---
> > > > > >  .github/workflows/maven-verify.yml | 2 +-
> > > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > > >
> > > > > > diff --git a/.github/workflows/maven-verify.yml
> > > > > b/.github/workflows/maven-verify.yml
> > > > > > index 654b5b9..471053f 100644
> > > > > > --- a/.github/workflows/maven-verify.yml
> > > > > > +++ b/.github/workflows/maven-verify.yml
> > > > > > @@ -84,7 +84,7 @@ on:
> > > > > >ff-maven:
> > > > > >  description: The Maven version used during
> fail-fast-build
> > > job
> > > > > >  required: false
> > > > > > -default: '3.8.7'
> > > > > > +default: '3.9.0'
> > > > > >  type: string
> > > > > >
> > > > > >ff-jdk:
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Sylwester Lachiewicz]

>From our Maven Download page:

Downloading Apache Maven 3.9.0

Apache Maven 3.9.0 is the latest release and recommended version for all
users.


On the history page we have only information that Maven 3.0 is EOL.

https://maven.apache.org/docs/history.html


br

Sylwester

niedz., 19 lut 2023 o 12:04 Olivier Lamy  napisał(a):

> On Sun, 19 Feb 2023 at 8:59 pm, Sylwester Lachiewicz <
> slachiew...@gmail.com>
> wrote:
>
> > Hi,
> > I think so far we support all maven versions from 3.2.5+ and nothing has
> > changed yet.
> >
> > If we have issue with specific Maven version and plugin we can add/change
> > used Maven in GH action. Ofc we should use donated resources from GitHub
> > effectively.
> >
> > I believe now focus is to test all our plugins and shared libs with our
> > latest and recommend Maven 3.9?
>
>
> It might be a bit early to recommend 3.9.0?
> We should probably think about what do we really support?
> 3.8.x and 3.9.x?
> But first what do we mean by “support”?
>
>
> >
> > Sylwester
> >
> > niedz., 19 lut 2023, 11:49 użytkownik Olivier Lamy 
> > napisał:
> >
> > > Typically this issue is a problem on what core version do we support..
> > > https://issues.apache.org/jira/browse/MENFORCER-468
> > >
> > > The new code is not working with 3.8.x
> > >
> > > On Sun, 19 Feb 2023 at 1:58 pm, Olivier Lamy  wrote:
> > >
> > > > This change means we do not have any more gha running with anything
> > > > else than 3.9.0
> > > > can I understand this as an implicit we do not support anything
> <3.9.0?
> > > > I can't find any documentation on the website related to the
> > > > version(s) we support EOL etc...
> > > > Should we have some documentation to make this EOL policy really
> clear?
> > > >
> > > >
> > > >
> > > >
> > > > On Fri, 10 Feb 2023 at 06:15,  wrote:
> > > > >
> > > > > This is an automated email from the ASF dual-hosted git repository.
> > > > >
> > > > > slachiewicz pushed a commit to branch v3
> > > > > in repository
> > > > https://gitbox.apache.org/repos/asf/maven-gh-actions-shared.git
> > > > >
> > > > >
> > > > > The following commit(s) were added to refs/heads/v3 by this push:
> > > > >  new 907  Switch to Maven 3.9.0
> > > > > 907 is described below
> > > > >
> > > > > commit 9073820ea078880a0f4edc7ce2000ea4ade4
> > > > > Author: Sylwester Lachiewicz 
> > > > > AuthorDate: Thu Feb 9 21:15:09 2023 +0100
> > > > >
> > > > > Switch to Maven 3.9.0
> > > > > ---
> > > > >  .github/workflows/maven-verify.yml | 2 +-
> > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/.github/workflows/maven-verify.yml
> > > > b/.github/workflows/maven-verify.yml
> > > > > index 654b5b9..471053f 100644
> > > > > --- a/.github/workflows/maven-verify.yml
> > > > > +++ b/.github/workflows/maven-verify.yml
> > > > > @@ -84,7 +84,7 @@ on:
> > > > >ff-maven:
> > > > >  description: The Maven version used during fail-fast-build
> > job
> > > > >  required: false
> > > > > -default: '3.8.7'
> > > > > +default: '3.9.0'
> > > > >  type: string
> > > > >
> > > > >ff-jdk:
> > > > >
> > > >
> > >
> >
>

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Olivier Lamy]

On Sun, 19 Feb 2023 at 8:59 pm, Sylwester Lachiewicz 
wrote:

> Hi,
> I think so far we support all maven versions from 3.2.5+ and nothing has
> changed yet.
>
> If we have issue with specific Maven version and plugin we can add/change
> used Maven in GH action. Ofc we should use donated resources from GitHub
> effectively.
>
> I believe now focus is to test all our plugins and shared libs with our
> latest and recommend Maven 3.9?


It might be a bit early to recommend 3.9.0?
We should probably think about what do we really support?
3.8.x and 3.9.x?
But first what do we mean by “support”?


>
> Sylwester
>
> niedz., 19 lut 2023, 11:49 użytkownik Olivier Lamy 
> napisał:
>
> > Typically this issue is a problem on what core version do we support..
> > https://issues.apache.org/jira/browse/MENFORCER-468
> >
> > The new code is not working with 3.8.x
> >
> > On Sun, 19 Feb 2023 at 1:58 pm, Olivier Lamy  wrote:
> >
> > > This change means we do not have any more gha running with anything
> > > else than 3.9.0
> > > can I understand this as an implicit we do not support anything <3.9.0?
> > > I can't find any documentation on the website related to the
> > > version(s) we support EOL etc...
> > > Should we have some documentation to make this EOL policy really clear?
> > >
> > >
> > >
> > >
> > > On Fri, 10 Feb 2023 at 06:15,  wrote:
> > > >
> > > > This is an automated email from the ASF dual-hosted git repository.
> > > >
> > > > slachiewicz pushed a commit to branch v3
> > > > in repository
> > > https://gitbox.apache.org/repos/asf/maven-gh-actions-shared.git
> > > >
> > > >
> > > > The following commit(s) were added to refs/heads/v3 by this push:
> > > >  new 907  Switch to Maven 3.9.0
> > > > 907 is described below
> > > >
> > > > commit 9073820ea078880a0f4edc7ce2000ea4ade4
> > > > Author: Sylwester Lachiewicz 
> > > > AuthorDate: Thu Feb 9 21:15:09 2023 +0100
> > > >
> > > > Switch to Maven 3.9.0
> > > > ---
> > > >  .github/workflows/maven-verify.yml | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/.github/workflows/maven-verify.yml
> > > b/.github/workflows/maven-verify.yml
> > > > index 654b5b9..471053f 100644
> > > > --- a/.github/workflows/maven-verify.yml
> > > > +++ b/.github/workflows/maven-verify.yml
> > > > @@ -84,7 +84,7 @@ on:
> > > >ff-maven:
> > > >  description: The Maven version used during fail-fast-build
> job
> > > >  required: false
> > > > -default: '3.8.7'
> > > > +default: '3.9.0'
> > > >  type: string
> > > >
> > > >ff-jdk:
> > > >
> > >
> >
>

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Sylwester Lachiewicz]

Hi,
I think so far we support all maven versions from 3.2.5+ and nothing has
changed yet.

If we have issue with specific Maven version and plugin we can add/change
used Maven in GH action. Ofc we should use donated resources from GitHub
effectively.

I believe now focus is to test all our plugins and shared libs with our
latest and recommend Maven 3.9?

Sylwester

niedz., 19 lut 2023, 11:49 użytkownik Olivier Lamy 
napisał:

> Typically this issue is a problem on what core version do we support..
> https://issues.apache.org/jira/browse/MENFORCER-468
>
> The new code is not working with 3.8.x
>
> On Sun, 19 Feb 2023 at 1:58 pm, Olivier Lamy  wrote:
>
> > This change means we do not have any more gha running with anything
> > else than 3.9.0
> > can I understand this as an implicit we do not support anything <3.9.0?
> > I can't find any documentation on the website related to the
> > version(s) we support EOL etc...
> > Should we have some documentation to make this EOL policy really clear?
> >
> >
> >
> >
> > On Fri, 10 Feb 2023 at 06:15,  wrote:
> > >
> > > This is an automated email from the ASF dual-hosted git repository.
> > >
> > > slachiewicz pushed a commit to branch v3
> > > in repository
> > https://gitbox.apache.org/repos/asf/maven-gh-actions-shared.git
> > >
> > >
> > > The following commit(s) were added to refs/heads/v3 by this push:
> > >  new 907  Switch to Maven 3.9.0
> > > 907 is described below
> > >
> > > commit 9073820ea078880a0f4edc7ce2000ea4ade4
> > > Author: Sylwester Lachiewicz 
> > > AuthorDate: Thu Feb 9 21:15:09 2023 +0100
> > >
> > > Switch to Maven 3.9.0
> > > ---
> > >  .github/workflows/maven-verify.yml | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/.github/workflows/maven-verify.yml
> > b/.github/workflows/maven-verify.yml
> > > index 654b5b9..471053f 100644
> > > --- a/.github/workflows/maven-verify.yml
> > > +++ b/.github/workflows/maven-verify.yml
> > > @@ -84,7 +84,7 @@ on:
> > >ff-maven:
> > >  description: The Maven version used during fail-fast-build job
> > >  required: false
> > > -default: '3.8.7'
> > > +default: '3.9.0'
> > >  type: string
> > >
> > >ff-jdk:
> > >
> >
>

Re: [maven-gh-actions-shared] branch v3 updated: Switch to Maven 3.9.0

[Olivier Lamy]

Typically this issue is a problem on what core version do we support..
https://issues.apache.org/jira/browse/MENFORCER-468

The new code is not working with 3.8.x

On Sun, 19 Feb 2023 at 1:58 pm, Olivier Lamy  wrote:

> This change means we do not have any more gha running with anything
> else than 3.9.0
> can I understand this as an implicit we do not support anything <3.9.0?
> I can't find any documentation on the website related to the
> version(s) we support EOL etc...
> Should we have some documentation to make this EOL policy really clear?
>
>
>
>
> On Fri, 10 Feb 2023 at 06:15,  wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > slachiewicz pushed a commit to branch v3
> > in repository
> https://gitbox.apache.org/repos/asf/maven-gh-actions-shared.git
> >
> >
> > The following commit(s) were added to refs/heads/v3 by this push:
> >  new 907  Switch to Maven 3.9.0
> > 907 is described below
> >
> > commit 9073820ea078880a0f4edc7ce2000ea4ade4
> > Author: Sylwester Lachiewicz 
> > AuthorDate: Thu Feb 9 21:15:09 2023 +0100
> >
> > Switch to Maven 3.9.0
> > ---
> >  .github/workflows/maven-verify.yml | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/.github/workflows/maven-verify.yml
> b/.github/workflows/maven-verify.yml
> > index 654b5b9..471053f 100644
> > --- a/.github/workflows/maven-verify.yml
> > +++ b/.github/workflows/maven-verify.yml
> > @@ -84,7 +84,7 @@ on:
> >ff-maven:
> >  description: The Maven version used during fail-fast-build job
> >  required: false
> > -default: '3.8.7'
> > +default: '3.9.0'
> >  type: string
> >
> >ff-jdk:
> >
>