Re: Request for Enhancement: Dependency Overrides

Hi Enno, 2 things. I'd want to emphasise that the resolution of dependency management info and the dependency overrides (more like a reactor management concern) are independent of one another. Can achieve by promoting the tag to project. Then why not use the existing dependency tag to define the

Re: [maven-enforcer] branch master updated (3047f7f -> e3f2f27)

Hi, I'm new to this group and would like to contribute. How best can I do that? Please advise, Thanks, Asha On Sat, Nov 20, 2021 at 8:03 PM wrote: > This is an automated email from the ASF dual-hosted git repository. > > slachiewicz pushed a change to branch master > in repository https://gitb

Re: Request for Enhancement: Dependency Overrides

Hello, it's been a while and I've made some progress regarding overrides/replacements and wanted to share the current state. What's implemented/changed: * The POM version has been upgraded to 4.1.0 and will accept /project/dependencyManagement/dependencyOverrides which in turn can take the

[VOTE] Release Maven Resolver Ant Tasks version 1.4.0

Hi, We solved 13 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12350366 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%20%

[GitHub] [maven-site] manuelbl opened a new pull request #275: Version requirement for versions before next major release

manuelbl opened a new pull request #275: URL: https://github.com/apache/maven-site/pull/275 In a POM, one would often like to restrict a dependency to a version before the next major release (incl. pre-releases). This does not work as most people would expect. So the proposed paragraph exp

[GitHub] [maven-wrapper-plugin] rfscholte commented on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

rfscholte commented on pull request #1: URL: https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-974682770 This commit touches 75 files, and after MWRAPPER-16 a lot of them are removed. Keep in mind that I moved it to maven-core due to the huge overlap of scripts, but

[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

hboutemy edited a comment on pull request #1: URL: https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-974664732 wrong logic: not merging MWRAPPER-14 (and not releasing a usable wrapper) does not help on evolving with MWRAPPER-16 please think again: scripts released a

[GitHub] [maven-wrapper-plugin] jvanzyl commented on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

jvanzyl commented on pull request #1: URL: https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-974671779 @rfscholte are you fine with a first step of dynamically importing the scripts and implementing the more sophisticated https://issues.apache.org/jira/browse/MWRAPPER-16

[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

hboutemy edited a comment on pull request #1: URL: https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-974664732 wrong logic: not merging MWRAPPER-14 (and not releasing a usable wrapper) does not help on evolving with MWRAPPER-16 please think again: scripts released a

[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

hboutemy edited a comment on pull request #1: URL: https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-974664732 wrong logic: not merging MWRAPPER-14 (and not releasing a usable wrapper) does not help on evolving with MWRAPPER-16 please think again: scripts released a

[GitHub] [maven-wrapper-plugin] hboutemy commented on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

hboutemy commented on pull request #1: URL: https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-974664732 wrong logic: not merging MWRAPPER-14 (and not releasing a usable wrapper) does not help on evolving with MWRAPPER-16 please think again: scripts released as part

[GitHub] [maven-site] michael-o merged pull request #274: Add release notes for Maven 3.8.4

michael-o merged pull request #274: URL: https://github.com/apache/maven-site/pull/274 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubsc

[ANN] Apache Maven 3.8.4 released

The Apache Maven team is pleased to announce the release of the Apache Maven 3.8.4 Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece o

[RESULT] [VOTE] Release Apache Maven version 3.8.4

Hi, The vote has passed with the following result: +1: Karl Heinz Marbaise, Romain Manni-Bucau, Mickael Istria, Tamás Cservenák, Arnaud Héritier, Enrico Olivelli, Tibor Digana, Sylwester Lachiewicz, Jason van Zyl, Hervé Boutemy, Olivier Lamy, Guillaume Nodet PMC quorum: reached I will promo

[GitHub] [maven-wrapper-plugin] rfscholte commented on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

rfscholte commented on pull request #1: URL: https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-974648100 it still contains the copy of the original scripts, right? Then I'm -1. -- This is an automated message from the Apache Git Service. To respond to the message, please