Re: [VOTE] Release Maven Doxia version 2.0.0-M5

2023-01-23 Thread Slawomir Jaranowski
+1

- source release contains files with CRLF line ending, so when I try to
build code on MacOs I have errors from spotless, like

[ERROR] Failed to execute goal
com.diffplug.spotless:spotless-maven-plugin:2.28.0:check (default) on
project doxia: The following files had format violations:
[ERROR] pom.xml
[ERROR] @@ -1,513 +1,513 @@
[ERROR] -\r\n
[ERROR] - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Sławomir Jaranowski


Re: Maven 3.9,0 plan

2023-01-23 Thread Mark Derricutt

On 19 Jan 2023, at 22:02, Tamás Cservenák wrote:


So, please anyone able to, test 3.9.0-SNAPSHOT if you can.



Seems to run fine for my normal projects - but crashes on in my main 
$work project, due to an internal Maven Plugin I have that uses the 
maven resolver - and I've not released a version of that which uses the 
newer dependency so gets:


```
[ERROR] Failed to execute goal 
com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps 
(default-cli) on project smx3.api: Execution default-cli of goal 
com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps failed: A 
required class was missing while executing 
com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps: 
org/eclipse/aether/connector/basic/BasicRepositoryConnectorFactory

[ERROR] -
[ERROR] realm =plugin>com.smxemail:rangeresolver-maven-plugin:1.1.58
[ERROR] strategy = 
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = 
file:/Users/amrk/.m2/repository/com/smxemail/rangeresolver-maven-plugin/1.1.58/rangeresolver-maven-plugin-1.1.58.jar
[ERROR] urls[1] = 
file:/Users/amrk/.m2/repository/com/smxemail/com.smxemail.rangeresolver/1.1.34/com.smxemail.rangeresolver-1.1.34.jar
[ERROR] urls[2] = 
file:/Users/amrk/.m2/repository/com/google/guava/guava/31.1-jre/guava-31.1-jre.jar
[ERROR] urls[3] = 
file:/Users/amrk/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar

```

Likely just requires me to update my plugin, but this will likely break 
other mojos that use aether/resolver.


Being a .0 release (even tho not a major) I think I'm fine with that - 
but it might be something we want to document?






---
"The ease with which a change can be implemented has no relevance at all 
to whether it is the right change for the (Java) Platform for all time." 
 Mark Reinhold.


Mark Derricutt
http://www.chaliceofblood.net
http://www.theoryinpractice.net
http://twitter.com/talios
http://facebook.com/mderricutt


Re: [VOTE] Release Apache Maven Reporting API version 4.0.0-M4

2023-01-23 Thread Herve Boutemy
+1

Reproducible Builds ok: reference build done with JDK 8 on Windows

Regards,

Hervé

On 2023/01/22 19:06:27 Michael Osipov wrote:
> Hi,
> 
> IMPORTANT: Requires Doxia 2.0.0-M5 vote/staging repo!
> 
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352772
> 
> 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-api
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1857/
> https://repository.apache.org/content/repositories/maven-1857/org/apache/maven/reporting/maven-reporting-api/4.0.0-M4/maven-reporting-api-4.0.0-M4-source-release.zip
> 
> Source release checksum(s):
> maven-reporting-api-4.0.0-M4-source-release.zip
> sha512: 
> 92d884e2e26616be65510b64e429efa489b59e593d288ad7877272c212a2926cb43416a992428ffd209bed4303c4955ba3cf056c4c69a801512421f6a77e293e
> 
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-api-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: [VOTE] Release Maven Doxia version 2.0.0-M5

2023-01-23 Thread Herve Boutemy
+1

Reproducible Builds ok: reference build done with JDK 8 on Windows

Regards,

Hervé

On 2023/01/22 18:47:57 Michael Osipov wrote:
> Hi,
> 
> We solved 12 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317230=12352482
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20DOXIA%20AND%20resolution%20%3D%20Unresolved
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1856/
> https://repository.apache.org/content/repositories/maven-1856/org/apache/maven/doxia/doxia/2.0.0-M5/doxia-2.0.0-M5-source-release.zip
> 
> Source release checksum(s):
> doxia-2.0.0-M5-source-release.zip
> sha512: 
> 512c2d613c13a9891de53d03c2cddc806d93f6f0afb49c5f20a9d524b063537384c009c6934d2a2c8d86d38a3226d027581f0eb34e20398e6c5f22fdfa900266
> 
> Staging site:
> https://maven.apache.org/doxia/doxia-archives/doxia-LATEST/
> 
> Guide to testing staged releases:
> http://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: Upcoming Maven Enforcer 3.2.0 release

2023-01-23 Thread Petr Široký
Hello,

great stuff! Looking forward to that release.

I gave the latest 3.2.0-SNAPSHOT (26697b16) a quick try with Quarkus repo 
(https://github.com/quarkusio/quarkus), since the project is pretty big (more 
than 1k sub-modules) and it also uses enforcer quite extensively (multiple 
executions). The current enforcer version is 3.0.0-M3, since there were 
multiple bugs in 3.1.0 which I think prevented the upgrade.

Here are my findings:
 - 'mvn validate' still succeeds, there are no enforcer errors. This is I think 
good. I obviously did not check if every rule of every module is being 
executed, but I did a quick comparison in few modules and everything _seems_ to 
be in order.

 - what seems to be very positive is the improvement in execution time. I 
compared a sequential and parallel runs, and also mvnd run (using JDK 17 + 
Maven 3.8.7 / Maven Deamon 0.8.2):

1) Sequential run:
  $ mvn validate -Dversion.enforcer.plugin=3.0.0-M3
  === Took ~140s

  $ mvn validate -Dversion.enforcer.plugin=3.2.0-SNAPSHOT
  === Took ~35s


2) Parallel run (with 8 threads):
  $ mvn validate -T8 -Dversion.enforcer.plugin=3.0.0-M3
  === Took ~30s

  $ mvn validate -T8 -Dversion.enforcer.plugin=3.2.0-SNAPSHOT
  === Took ~10s


3) Maven deamon run (with 8 threads and multiple executions to let the daemon 
"warm-up"):
  $ mvnd validate -T8 -Dversion.enforcer.plugin=3.0.0-M3
  === Took ~80s
  $ mvnd validate -T8 -Dversion.enforcer.plugin=3.2.0-SNAPSHOT
  === Took ~8s

Note: I don't quite understand why the Maven daemon run with version 3.0.0-M3 
is so much slower comparing to the non-daemon run (80s vs 35s). I would have to 
investigate further, so let's ignore those numbers for now I guess.

Are we expecting this kind of improvement? Or could this be somehow caused by 
e.g. mistakenly not executing some of the rules? I would need to again dig 
deeper, but before that it would be good to know if this is maybe something we 
are expecting.

Thanks,
Petr


--- Original Message ---
On Friday, January 20th, 2023 at 19:09, Slawomir Jaranowski 
 wrote:


> 
> 
> Hi,
> 
> I'm going to release the next version of Maven Enforcer plugin and build in
> rules.
> Probably in next week - about 24-26 of January
> 
> Prepared release note:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12351838
> 
> The most important:
> - New Enforcer API - https://issues.apache.org/jira/browse/MENFORCER-455
> - Get rid of maven-dependency-tree dependency -
> https://issues.apache.org/jira/browse/MENFORCER-435
> - Verify working with Maven 4 -
> https://issues.apache.org/jira/browse/MENFORCER-447
> 
> I will appreciate any tests on your projects.
> If something else should be added please let me know.
> 
> --
> Sławomir Jaranowski

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