[ANN] Apache Maven Dependency Analyzer 1.15.0 Released

2024-10-08 Thread Slawomir Jaranowski
The Apache Maven team is pleased to announce the release of the Apache Maven Dependency Analyzer, version 1.15.0 This component analyzes the dependencies of a project for undeclared or unused artifacts. https://maven.apache.org/shared/maven-dependency-analyzer/ You should specify the version in

[RESULT] [VOTE] Release Apache Maven Dependency Analyzer version 1.15.0

2024-10-08 Thread Slawomir Jaranowski
Hi, The vote has passed with the following result: +1: Herve Boutemy, Michael Osipov, Sylwester Lachiewicz, Tamás Cservenák PMC quorum: reached I will promote the source release zip file to the Apache distribution area and the artifacts to the central repo. -- Sławomir Jaranowski ---

Re: [DISCUSS] Merge ITs in maven

2024-10-08 Thread Christoph Läubrich
Maybe adding it as a git submodule would also help, then it could be fetched/build together but still retain a separate git repo. I agree that having to specify version ranges for maven version in each test looks odd if it is part of the repo itself, I always has seen this more as some kind of

Re: [DISCUSS] Merge ITs in maven

2024-10-08 Thread Xeno Amess
Sigh. This shall be a typical scenario for git submodule, but as we all know, git submodule is something designed so disaster that nearly shit, if not worse than shit. .I myself vote +1 for the merge if I have the right to, for now, but like Herve Boutemy said if we could know why guys split them

Re: [VOTE] Release Apache Maven Doxia Sitetools version 2.0.0

2024-10-08 Thread Herve Boutemy
+1 Reproducible Build ok: reference done with JDK 8 on Windows Regards, Hervé On 2024/10/06 18:49:26 Michael Osipov wrote: > Hi, > > we solved 107 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320&version=12354040 > > There are still a couple of issues left i

Re: [DISCUSS] Merge ITs in maven

2024-10-08 Thread Herve Boutemy
I understand how it adds complexity AFAIK, the interest of having a separate project of core ITs is to clear state the Maven core version range for each test, to clearly document when things were introduced / broken / fixed and even be able to run HEAD ITs against a past release is it the only

Re: [DISCUSS] Merge ITs in maven

2024-10-08 Thread Matthias Bünger
I don't know the history about WHY they are seperated, so maybe there are (or at least there were) valid reason to do so - at least in this repo. In several plugins the IT are part of the same repo as the code. In general: I think it's usefull to merge them so that the IT can be run while buildin