[jira] [Commented] (MDEP-532) Undeclared test resources fail build despite 'ignoreNonCompile'
[
https://issues.apache.org/jira/browse/MDEP-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892659#comment-17892659
]
Alexander Kriegisch commented on MDEP-532:
--
Just to clarify and confirm what is already written in the README of
https://github.com/kriegaex/MDEP-532: I do not run any goals manually, the
plugin is executed during its default phase when calling {{mvn clean verify}}.
A default execution name is *not* the issue here.
> Undeclared test resources fail build despite 'ignoreNonCompile'
> ---
>
> Key: MDEP-532
> URL: https://issues.apache.org/jira/browse/MDEP-532
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 2.10
> Environment: Windows 7 Pro 64-bit, Java OpenSDK 8, Maven 3.3.9
>Reporter: Alexander Kriegisch
>Assignee: Elliotte Rusty Harold
>Priority: Minor
> Labels: S2
>
> I have this plugin in my project's root POM:
> {code}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 2.10
>
>
> analyze
>
> analyze-only
>
>
> true
> true
>
> *
>
>
>
>
> {code}
> Even though I want to ignore used undeclared test dependencies via
> {{true}}, my build fails like this in
> several modules:
> {code}
> [INFO] --- maven-dependency-plugin:2.10:analyze-only (analyze) @ xxx.yyy ---
> [WARNING] Used undeclared dependencies found:
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven:jar:2.2.0:test
> [WARNING]org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.3:test
> [WARNING]
> org.jboss.arquillian.container:arquillian-container-test-api:jar:1.1.11.Final:test
> [WARNING]
> org.jboss.arquillian.spock:arquillian-spock-core:jar:1.0.0.RC4_XXX:test
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven-archive:jar:2.2.0:test
> (...)
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project xxx.yyy: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project yyy.zzz: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project zzz.aaa: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project aaa.bbb: Dependency problems found -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MDEP-532) Undeclared test resources fail build despite 'ignoreNonCompile'
[
https://issues.apache.org/jira/browse/MDEP-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892659#comment-17892659
]
Alexander Kriegisch edited comment on MDEP-532 at 10/25/24 4:17 AM:
Just to clarify and confirm what is already written in the README of
https://github.com/kriegaex/MDEP-532: I do not run any goals manually, the
plugin is executed during its default phase when calling {{mvn clean verify}}.
A default execution name is *not* the issue here.
Even when using {{default-cli}} and manually calling {{mvn
dependency:analyze}} or {{mvn dependency:analyze-only}}, the issue with
{{commons-logging}} still being falsely reported despite
{{true}} remains. A bug is a bug is a bug.
was (Author: kriegaex):
Just to clarify and confirm what is already written in the README of
https://github.com/kriegaex/MDEP-532: I do not run any goals manually, the
plugin is executed during its default phase when calling {{mvn clean verify}}.
A default execution name is *not* the issue here.
> Undeclared test resources fail build despite 'ignoreNonCompile'
> ---
>
> Key: MDEP-532
> URL: https://issues.apache.org/jira/browse/MDEP-532
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 2.10
> Environment: Windows 7 Pro 64-bit, Java OpenSDK 8, Maven 3.3.9
>Reporter: Alexander Kriegisch
>Assignee: Elliotte Rusty Harold
>Priority: Minor
> Labels: S2
>
> I have this plugin in my project's root POM:
> {code}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 2.10
>
>
> analyze
>
> analyze-only
>
>
> true
> true
>
> *
>
>
>
>
> {code}
> Even though I want to ignore used undeclared test dependencies via
> {{true}}, my build fails like this in
> several modules:
> {code}
> [INFO] --- maven-dependency-plugin:2.10:analyze-only (analyze) @ xxx.yyy ---
> [WARNING] Used undeclared dependencies found:
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven:jar:2.2.0:test
> [WARNING]org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.3:test
> [WARNING]
> org.jboss.arquillian.container:arquillian-container-test-api:jar:1.1.11.Final:test
> [WARNING]
> org.jboss.arquillian.spock:arquillian-spock-core:jar:1.0.0.RC4_XXX:test
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven-archive:jar:2.2.0:test
> (...)
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project xxx.yyy: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project yyy.zzz: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project zzz.aaa: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project aaa.bbb: Dependency problems found -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-8300) [REGRESSION] colorized transfer messages broken
[
https://issues.apache.org/jira/browse/MNG-8300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892670#comment-17892670
]
Herve Boutemy edited comment on MNG-8300 at 10/25/24 6:26 AM:
--
ok, it looks my terminal does not display a different color for [ANSI
faint|https://gist.github.com/fnky/458719343aabd01cfb17a3a4f7296797#colors--graphics-mode]:
{noformat}echo -e "\e[0mReset\e[0m" "\e[1mBold\e[0m" "\e[2mDim/faint\e[0m"
"\e[3mItalic\e[0m" "\e[4mUnderline\e[0m" "\e[5mBlinking\e[0m"
"\e[7mInverse/reverse\e[0m" "\e[8mHidden/invisible\e[0m"
"\e[9mStrikethrough\e[0m"{noformat}
Dim/faint is rendered exactly as Reset...
ok, not fully a Maven issue but related to terminal ANSI support level: now I
remember why I did not use faint when I wrote all these ansi codes, I did not
know that my terminal rendering was more the exception than the norm :) I'd be
interested to know if it is ok on Windows
I need to look at what other tools do regarding this faint ANSI mode: I feel
they avoid using it, as it it not supported everywhere. But I'll come back with
more facts about it...
was (Author: hboutemy):
ok, it looks my terminal does not display a different color for [ANSI
faint|https://gist.github.com/fnky/458719343aabd01cfb17a3a4f7296797#colors--graphics-mode]:
{noformat}echo -e "\e[0mReset\e[0m" "\e[1mBold\e[0m" "\e[2mDim/faint\e[0m"
"\e[3mItalic\e[0m" "\e[4mUnderline\e[0m" "\e[5mBlinking\e[0m"
"\e[7mInverse/reverse\e[0m" "\e[8mHidden/invisible\e[0m"
"\e[9mStrikethrough\e[0m"{noformat}
Dim/faint is rendered exactly as Reset...
ok, not fully a Maven issue but related to terminal ANSI support level: now I
remember why I did not use faint when I wrote all these ansi codes, I did not
know that my terminal rendering was more the exception than the norm :)
I need to look at what other tools do regarding this faint ANSI mode: I feel
they avoid using it, as it it not supported everywhere. But I'll come back with
more facts about it...
> [REGRESSION] colorized transfer messages broken
> ---
>
> Key: MNG-8300
> URL: https://issues.apache.org/jira/browse/MNG-8300
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-12, 4.0.0-beta-4
>Reporter: Herve Boutemy
>Priority: Minor
> Fix For: 4.0.0-beta-6
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png,
> screenshot-4.png, screenshot-5.png, screenshot-6.png
>
>
> colorized transfer messages implemented in Maven 4.0.0-alpha-8 in MNG-7875
> but it seems MNG-7995 in Maven 4.0.0-alpha-11 broke it, and went unnoticed
> until now 4.0.0-beta-4
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-8300) [REGRESSION] colorized transfer messages broken
[
https://issues.apache.org/jira/browse/MNG-8300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892670#comment-17892670
]
Herve Boutemy edited comment on MNG-8300 at 10/25/24 6:25 AM:
--
ok, it looks my terminal does not display a different color for [ANSI
faint|https://gist.github.com/fnky/458719343aabd01cfb17a3a4f7296797#colors--graphics-mode]:
{noformat}echo -e "\e[0mReset\e[0m" "\e[1mBold\e[0m" "\e[2mDim/faint\e[0m"
"\e[3mItalic\e[0m" "\e[4mUnderline\e[0m" "\e[5mBlinking\e[0m"
"\e[7mInverse/reverse\e[0m" "\e[8mHidden/invisible\e[0m"
"\e[9mStrikethrough\e[0m"{noformat}
Dim/faint is rendered exactly as Reset...
ok, not fully a Maven issue but related to terminal ANSI support level: now I
remember why I did not use faint when I wrote all these ansi codes, I did not
know that my terminal rendering was more the exception than the norm :)
I need to look at what other tools do regarding this faint ANSI mode: I feel
they avoid using it, as it it not supported everywhere. But I'll come back with
more facts about it...
was (Author: hboutemy):
ok, it looks my terminal does not display a different color for [ANSI
faint|https://gist.github.com/fnky/458719343aabd01cfb17a3a4f7296797#colors--graphics-mode]:
{noformat}echo -e "\e[0mReset\e[0m" "\e[1mBold\e[0m" "\e[2mDim/faint\e[0m"
"\e[3mItalic\e[0m" "\e[4mUnderline\e[0m" "\e[5mBlinking\e[0m"
"\e[7mInverse/reverse\e[0m" "\e[8mHidden/invisible\e[0m"
"\e[9mStrikethrough\e[0m"{noformat}
Dim/faint is rendered exactly as Reset...
ok, not a Maven issue but terminal: now I remember why i did not use faint when
I wrote all these ansi codes, I did not know that my terminal rendering was
more the exception than the norm :)
> [REGRESSION] colorized transfer messages broken
> ---
>
> Key: MNG-8300
> URL: https://issues.apache.org/jira/browse/MNG-8300
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-12, 4.0.0-beta-4
>Reporter: Herve Boutemy
>Priority: Minor
> Fix For: 4.0.0-beta-6
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png,
> screenshot-4.png, screenshot-5.png, screenshot-6.png
>
>
> colorized transfer messages implemented in Maven 4.0.0-alpha-8 in MNG-7875
> but it seems MNG-7995 in Maven 4.0.0-alpha-11 broke it, and went unnoticed
> until now 4.0.0-beta-4
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8337) aggregator goal called from CLI shows an additional module at end (= first module twice)
[
https://issues.apache.org/jira/browse/MNG-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892675#comment-17892675
]
Herve Boutemy commented on MNG-8337:
yes, the report is relatedd to default single-threaded builder: the parallel
builder has completely different output, I suppose your feedback is not
specific to any precise Maven version but the parallel builder
> aggregator goal called from CLI shows an additional module at end (= first
> module twice)
>
>
> Key: MNG-8337
> URL: https://issues.apache.org/jira/browse/MNG-8337
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.3, 3.9.9, 4.0.0-beta-5
>Reporter: Herve Boutemy
>Priority: Major
>
> example with this surprising {{{}[13/12]{}}}:
> {noformat}
> [INFO] --< eu.maveniverse.maven.nisse:nisse
> >--
> [INFO] Building eu.maveniverse.maven.nisse:nisse 0.3.3
> [1/12]
> [INFO] from pom.xml
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- clean:3.4.0:clean (default-clean) @ nisse ---
> ...
> [INFO] --< eu.maveniverse.maven.nisse:nisse
> >--
> [INFO] Building eu.maveniverse.maven.nisse:nisse 0.3.3
> [13/12]
> [INFO] from pom.xml
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- artifact:3.5.2:describe-build-output (default-cli) @ nisse ---
> {noformat}
> in fact, it is not a 13th module but the first module where an aggregator
> goal has to run ({{{}artifact:describe-build-output{}}}), without any other
> lifecycle goal as they already have been executed on {{[1/12]}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-8300) [REGRESSION] colorized transfer messages broken
[
https://issues.apache.org/jira/browse/MNG-8300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892670#comment-17892670
]
Herve Boutemy edited comment on MNG-8300 at 10/25/24 5:51 AM:
--
ok, it looks my terminal does not display a different color for [ANSI
faint|https://gist.github.com/fnky/458719343aabd01cfb17a3a4f7296797#colors--graphics-mode]:
{noformat}echo -e "\e[0mReset\e[0m" "\e[1mBold\e[0m" "\e[2mDim/faint\e[0m"
"\e[3mItalic\e[0m" "\e[4mUnderline\e[0m" "\e[5mBlinking\e[0m"
"\e[7mInverse/reverse\e[0m" "\e[8mHidden/invisible\e[0m"
"\e[9mStrikethrough\e[0m"{noformat}
Dim/faint is rendered exactly as Reset...
ok, not a Maven issue but terminal: now I remember why i did not use faint when
I wrote all these ansi codes, I did not know that my terminal rendering was
more the exception than the norm :)
was (Author: hboutemy):
ok, it looks my terminal does not display a different color for ANSI faint:
{noformat}echo -e "\e[0mReset\e[0m" "\e[1mBold\e[0m" "\e[2mDim/faint\e[0m"
"\e[3mItalic\e[0m" "\e[4mUnderline\e[0m" "\e[5mBlinking\e[0m"
"\e[7mInverse/reverse\e[0m" "\e[8mHidden/invisible\e[0m"
"\e[9mStrikethrough\e[0m"{noformat}
Dim/faint is rendered exactly as Reset...
ok, not a Maven issue but terminal: now I remember why i did not use faint when
I wrote all these ansi codes, I did not know that my terminal rendering was
more the exception than the norm :)
> [REGRESSION] colorized transfer messages broken
> ---
>
> Key: MNG-8300
> URL: https://issues.apache.org/jira/browse/MNG-8300
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-12, 4.0.0-beta-4
>Reporter: Herve Boutemy
>Priority: Minor
> Fix For: 4.0.0-beta-6
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png,
> screenshot-4.png, screenshot-5.png, screenshot-6.png
>
>
> colorized transfer messages implemented in Maven 4.0.0-alpha-8 in MNG-7875
> but it seems MNG-7995 in Maven 4.0.0-alpha-11 broke it, and went unnoticed
> until now 4.0.0-beta-4
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump org.codehaus.plexus:plexus-xml from 3.0.1 to 4.0.4 [maven-resolver]
dependabot[bot] opened a new pull request, #592: URL: https://github.com/apache/maven-resolver/pull/592 Bumps [org.codehaus.plexus:plexus-xml](https://github.com/codehaus-plexus/plexus-xml) from 3.0.1 to 4.0.4. Release notes Sourced from https://github.com/codehaus-plexus/plexus-xml/releases";>org.codehaus.plexus:plexus-xml's releases. 4.0.4 🐛 Bug Fixes Allow nulls for write elements in MXSerializer (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/29";>#29) https://github.com/garydgregory";>@garydgregory Remove special chars from xml output (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/28";>#28) https://github.com/slawekjaranowski";>@slawekjaranowski 📦 Dependency updates Bump org.codehaus.plexus:plexus from 17 to 18 (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/39";>#39) https://github.com/dependabot";>@dependabot Bump org.codehaus.plexus:plexus from 16 to 17 (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/35";>#35) https://github.com/dependabot";>@dependabot Bump org.codehaus.plexus:plexus-utils from 4.0.0 to 4.0.1 (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/37";>#37) https://github.com/dependabot";>@dependabot Bump release-drafter/release-drafter from 5 to 6 (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/34";>#34) https://github.com/dependabot";>@dependabot 4.0.3 What's Changed explain 3 vs 4 by https://github.com/hboutemy";>@hboutemy in https://redirect.github.com/codehaus-plexus/plexus-xml/pull/24";>codehaus-plexus/plexus-xml#24 Update dependencies by https://github.com/cstamas";>@cstamas in https://redirect.github.com/codehaus-plexus/plexus-xml/pull/26";>codehaus-plexus/plexus-xml#26 Upgrade to Maven 4.0.0-alpha-9 by https://github.com/gnodet";>@gnodet in https://redirect.github.com/codehaus-plexus/plexus-xml/pull/27";>codehaus-plexus/plexus-xml#27 New Contributors https://github.com/cstamas";>@cstamas made their first contribution in https://redirect.github.com/codehaus-plexus/plexus-xml/pull/26";>codehaus-plexus/plexus-xml#26 Full Changelog: https://github.com/codehaus-plexus/plexus-xml/compare/plexus-xml-4.0.2...plexus-xml-4.0.3";>https://github.com/codehaus-plexus/plexus-xml/compare/plexus-xml-4.0.2...plexus-xml-4.0.3 4.0.2 What's Changed Cleanup after parent pom upgrade by https://github.com/slachiewicz";>@slachiewicz in https://redirect.github.com/codehaus-plexus/plexus-xml/pull/22";>codehaus-plexus/plexus-xml#22 Upgrade to 4.0.0-alpha-7 and exclude dependency to sisu (fixes https://redirect.github.com/codehaus-plexus/plexus-xml/issues/17";>#17) by https://github.com/gnodet";>@gnodet in https://redirect.github.com/codehaus-plexus/plexus-xml/pull/23";>codehaus-plexus/plexus-xml#23 New Contributors https://github.com/slachiewicz";>@slachiewicz made their first contribution in https://redirect.github.com/codehaus-plexus/plexus-xml/pull/22";>codehaus-plexus/plexus-xml#22 Full Changelog: https://github.com/codehaus-plexus/plexus-xml/compare/plexus-xml-4.0.1...plexus-xml-4.0.2";>https://github.com/codehaus-plexus/plexus-xml/compare/plexus-xml-4.0.1...plexus-xml-4.0.2 4.0.0 Use spotless (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/8";>#8) https://github.com/gnodet";>@gnodet Fix site generation (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/15";>#15) https://github.com/gnodet";>@gnodet Switch build ci workflow to master branch (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/14";>#14) https://github.com/gnodet";>@gnodet Fix SCM urls (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/13";>#13) https://github.com/gnodet";>@gnodet MXParser tokenization fails when PI is before first tag (fixes https://redirect.github.com/codehaus-plexus/plexus-xml/issues/7";>#7) (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/12";>#12) https://github.com/gnodet";>@gnodet Deprecate Xpp3DomUtils (fixes https://redirect.github.com/codehaus-plexus/plexus-xml/issues/6";>#6) (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/9";>#9) https://github.com/gnodet";>@gnodet Use a ArrayDeque (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/5";>#5) https://github.com/gnodet";>@gnodet Upgrade plugins and clean build warnings (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/4";>#4) https://github.com/gnodet";>@gnodet Switch to junit 5 (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/2";>#2) https://github.com/gnodet";>@gnodet Fix parsing an UTF-8 file without BOM and ISO-8859-1 encoding (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/1";>#1) https://github.com/gnodet";>@gnodet Commits https://github.com/codehaus-plexus/plexus-xml/commit/f25521bc31d321c2ffb57cf26ae17f745c2c35a6";>f25521b
[PR] Bump io.minio:minio from 8.5.12 to 8.5.13 [maven-resolver]
dependabot[bot] opened a new pull request, #593: URL: https://github.com/apache/maven-resolver/pull/593 Bumps [io.minio:minio](https://github.com/minio/minio-java) from 8.5.12 to 8.5.13. Release notes Sourced from https://github.com/minio/minio-java/releases";>io.minio:minio's releases. Bugfix Release What's Changed add httpclient close option to minio client builder by https://github.com/SerhiiKryvokin";>@SerhiiKryvokin in https://redirect.github.com/minio/minio-java/pull/1587";>minio/minio-java#1587 upgrade gradle and dependencies by https://github.com/balamurugana";>@balamurugana in https://redirect.github.com/minio/minio-java/pull/1579";>minio/minio-java#1579 New Contributors https://github.com/SerhiiKryvokin";>@SerhiiKryvokin made their first contribution in https://redirect.github.com/minio/minio-java/pull/1587";>minio/minio-java#1587 Full Changelog: https://github.com/minio/minio-java/compare/8.5.12...8.5.13";>https://github.com/minio/minio-java/compare/8.5.12...8.5.13 Commits https://github.com/minio/minio-java/commit/922175bda1f7f379e5f4b2c18e0685c0f5b351e5";>922175b Release version 8.5.13 https://github.com/minio/minio-java/commit/d76a580185f8fc4c79bf21291e50fd626e0667ec";>d76a580 upgrade gradle and dependencies (https://redirect.github.com/minio/minio-java/issues/1579";>#1579) https://github.com/minio/minio-java/commit/fd5192f50f13e43149c9ffe096c6a18a99e57656";>fd5192f add httpclient close option to minio client builder (https://redirect.github.com/minio/minio-java/issues/1587";>#1587) https://github.com/minio/minio-java/commit/ef85db96a0ac02a201ccc3b5fdd7964f076e017a";>ef85db9 Update version to next release See full diff in https://github.com/minio/minio-java/compare/8.5.12...8.5.13";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (MNG-8300) [REGRESSION] colorized transfer messages broken
[
https://issues.apache.org/jira/browse/MNG-8300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892670#comment-17892670
]
Herve Boutemy edited comment on MNG-8300 at 10/25/24 5:50 AM:
--
ok, it looks my terminal does not display a different color for ANSI faint:
{noformat}echo -e "\e[0mReset\e[0m" "\e[1mBold\e[0m" "\e[2mDim/faint\e[0m"
"\e[3mItalic\e[0m" "\e[4mUnderline\e[0m" "\e[5mBlinking\e[0m"
"\e[7mInverse/reverse\e[0m" "\e[8mHidden/invisible\e[0m"
"\e[9mStrikethrough\e[0m"{noformat}
Dim/faint is rendered exactly as Reset...
ok, not a Maven issue but terminal: now I remember why i did not use faint when
I wrote all these ansi codes, I did not know that my terminal rendering was
more the exception than the norm :)
was (Author: hboutemy):
ok, it looks my terminal does not display a different color for ANSI faint:
{{noformat}}echo -e "\e[0mReset\e[0m" "\e[1mBold\e[0m" "\e[2mDim/faint\e[0m"
"\e[3mItalic\e[0m" "\e[4mUnderline\e[0m" "\e[5mBlinking\e[0m"
"\e[7mInverse/reverse\e[0m" "\e[8mHidden/invisible\e[0m"
"\e[9mStrikethrough\e[0m"{{noformat}}
Dim/faint is rendered exactly as Reset...
ok, not a Maven issue but terminal: now I remember why i did not use faint when
I wrote all these ansi codes, I did not know that my terminal rendering was
more the exception than the norm :)
> [REGRESSION] colorized transfer messages broken
> ---
>
> Key: MNG-8300
> URL: https://issues.apache.org/jira/browse/MNG-8300
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-12, 4.0.0-beta-4
>Reporter: Herve Boutemy
>Priority: Minor
> Fix For: 4.0.0-beta-6
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png,
> screenshot-4.png, screenshot-5.png, screenshot-6.png
>
>
> colorized transfer messages implemented in Maven 4.0.0-alpha-8 in MNG-7875
> but it seems MNG-7995 in Maven 4.0.0-alpha-11 broke it, and went unnoticed
> until now 4.0.0-beta-4
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8300) [REGRESSION] colorized transfer messages broken
[
https://issues.apache.org/jira/browse/MNG-8300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892670#comment-17892670
]
Herve Boutemy commented on MNG-8300:
ok, it looks my terminal does not display a different color for ANSI faint:
{{noformat}}echo -e "\e[0mReset\e[0m" "\e[1mBold\e[0m" "\e[2mDim/faint\e[0m"
"\e[3mItalic\e[0m" "\e[4mUnderline\e[0m" "\e[5mBlinking\e[0m"
"\e[7mInverse/reverse\e[0m" "\e[8mHidden/invisible\e[0m"
"\e[9mStrikethrough\e[0m"{{noformat}}
Dim/faint is rendered exactly as Reset...
ok, not a Maven issue but terminal: now I remember why i did not use faint when
I wrote all these ansi codes, I did not know that my terminal rendering was
more the exception than the norm :)
> [REGRESSION] colorized transfer messages broken
> ---
>
> Key: MNG-8300
> URL: https://issues.apache.org/jira/browse/MNG-8300
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-12, 4.0.0-beta-4
>Reporter: Herve Boutemy
>Priority: Minor
> Fix For: 4.0.0-beta-6
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png,
> screenshot-4.png, screenshot-5.png, screenshot-6.png
>
>
> colorized transfer messages implemented in Maven 4.0.0-alpha-8 in MNG-7875
> but it seems MNG-7995 in Maven 4.0.0-alpha-11 broke it, and went unnoticed
> until now 4.0.0-beta-4
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump com.google.guava:guava from 32.0.1-jre to 33.3.1-jre [maven-compiler-plugin]
dependabot[bot] commented on PR #262: URL: https://github.com/apache/maven-compiler-plugin/pull/262#issuecomment-2436413593 OK, I won't notify you about com.google.guava:guava again, unless you re-open this PR. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-7354) Refactor MavenCli to ease extensibility
[
https://issues.apache.org/jira/browse/MNG-7354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-7354.
Resolution: Duplicate
> Refactor MavenCli to ease extensibility
> ---
>
> Key: MNG-7354
> URL: https://issues.apache.org/jira/browse/MNG-7354
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Priority: Major
>
> {{mvnd}} has to fully rewrite {{MavenCli}} in order to extend / slightly
> alter its behavior.
> The goal is to avoid code duplication and ease maintenance for mvnd when
> upgrading maven.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-7367) Make the EventSpyDispatcher somehow public
[
https://issues.apache.org/jira/browse/MNG-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-7367.
Resolution: Won't Fix
> Make the EventSpyDispatcher somehow public
> --
>
> Key: MNG-7367
> URL: https://issues.apache.org/jira/browse/MNG-7367
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Priority: Major
>
> The object can be retrieved on the {{MavenExecutionRequest}} but it's in a
> private package.
> Some unusual use cases do require adding spies from plugins.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-7157] [MNG-6843] Provide a better design for obtaining artifacts… [maven]
gnodet closed pull request #475: [MNG-7157] [MNG-6843] Provide a better design for obtaining artifacts… URL: https://github.com/apache/maven/pull/475 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-7873) Export missing Xpp3DomBuilder
[ https://issues.apache.org/jira/browse/MNG-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-7873. Resolution: Invalid > Export missing Xpp3DomBuilder > - > > Key: MNG-7873 > URL: https://issues.apache.org/jira/browse/MNG-7873 > Project: Maven > Issue Type: Bug > Components: Core >Reporter: Guillaume Nodet >Priority: Major > > See https://lists.apache.org/thread/ltd1g1dbv0lqqdw5q941gmrkfyn6m87m -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-622) Maven 4.0.0-beta-5
[ https://issues.apache.org/jira/browse/MRESOLVER-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-622. - Resolution: Fixed > Maven 4.0.0-beta-5 > -- > > Key: MRESOLVER-622 > URL: https://issues.apache.org/jira/browse/MRESOLVER-622 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-618) (build) Bump org.mockito:mockito-core from 5.14.1 to 5.14.2
Tamas Cservenak created MRESOLVER-618: - Summary: (build) Bump org.mockito:mockito-core from 5.14.1 to 5.14.2 Key: MRESOLVER-618 URL: https://issues.apache.org/jira/browse/MRESOLVER-618 Project: Maven Resolver Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 2.0.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8353] Bump com.fasterxml.woodstox:woodstox-core from 7.0.0 to 7.1.0 [maven]
gnodet merged PR #1834: URL: https://github.com/apache/maven/pull/1834 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8354) Bump org.junit:junit-bom from 5.11.2 to 5.11.3
[ https://issues.apache.org/jira/browse/MNG-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8354. Assignee: Guillaume Nodet Resolution: Fixed > Bump org.junit:junit-bom from 5.11.2 to 5.11.3 > -- > > Key: MNG-8354 > URL: https://issues.apache.org/jira/browse/MNG-8354 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-6 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1830 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8353) Bump com.fasterxml.woodstox:woodstox-core from 7.0.0 to 7.1.0
[ https://issues.apache.org/jira/browse/MNG-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8353. Fix Version/s: 4.0.0-beta-6 Assignee: Guillaume Nodet Resolution: Fixed > Bump com.fasterxml.woodstox:woodstox-core from 7.0.0 to 7.1.0 > - > > Key: MNG-8353 > URL: https://issues.apache.org/jira/browse/MNG-8353 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-6 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1834 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8355) Bump org.apache.velocity:velocity-engine-core from 2.4 to 2.4.1
[ https://issues.apache.org/jira/browse/MNG-8355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8355. Fix Version/s: 4.0.0-beta-6 Assignee: Guillaume Nodet Resolution: Fixed > Bump org.apache.velocity:velocity-engine-core from 2.4 to 2.4.1 > --- > > Key: MNG-8355 > URL: https://issues.apache.org/jira/browse/MNG-8355 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-6 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1831 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8354) Bump org.junit:junit-bom from 5.11.2 to 5.11.3
[ https://issues.apache.org/jira/browse/MNG-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8354: - Fix Version/s: 4.0.0-beta-6 > Bump org.junit:junit-bom from 5.11.2 to 5.11.3 > -- > > Key: MNG-8354 > URL: https://issues.apache.org/jira/browse/MNG-8354 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-6 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1830 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8352) Bump net.bytebuddy:byte-buddy from 1.15.5 to 1.15.7
[ https://issues.apache.org/jira/browse/MNG-8352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8352. Fix Version/s: 4.0.0-beta-6 Assignee: Guillaume Nodet Resolution: Fixed > Bump net.bytebuddy:byte-buddy from 1.15.5 to 1.15.7 > --- > > Key: MNG-8352 > URL: https://issues.apache.org/jira/browse/MNG-8352 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-6 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1845 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8357] Bump org.codehaus.mojo:exec-maven-plugin from 3.4.1 to 3.5.0 [maven]
gnodet merged PR #1833: URL: https://github.com/apache/maven/pull/1833 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-614) Collector applies depMgt entries coming from a self onto itself
[
https://issues.apache.org/jira/browse/MRESOLVER-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892609#comment-17892609
]
ASF GitHub Bot commented on MRESOLVER-614:
--
cstamas merged PR #588:
URL: https://github.com/apache/maven-resolver/pull/588
> Collector applies depMgt entries coming from a self onto itself
> ---
>
> Key: MRESOLVER-614
> URL: https://issues.apache.org/jira/browse/MRESOLVER-614
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 2.0.2
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.3
>
>
> In Maven3 this was not a problem, as Maven3 could add depMgt only on "root
> level".
> In Maven4 with use of new/old transitive Dependency Managers this became a
> problem. The dependency manager first receives depMgt entries for currently
> processed node, and then applies it onto same entry, overriding direct
> dependency versions.
> Example with Maven beta-5: it cannot build Resolver master
> (88a96ac0606d4d2372452a677d9f93c0b55105a4) as bnd-maven-plugin do depend on
> plexus-utils via path of {{bnd-maven-plugin > build-api > plexus-utils}} as
> it explodes due lack of org.plexus.utils.Scanner on classpath. This class was
> introduced in plexus-utils 1.5.8, and build-api do depend on it. But alas,
> build-api parent contains depMgt entry for plexus-utils 1.5.5 and is applied
> onto build-api overriding it's own dependency version.
> Basically current resolver code is NOT prepared for any "transitive
> dependency management" (despite DependencyManagers are there) as node would
> apply it's own depManagement rules onto itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MRESOLVER-614) Collector applies depMgt entries coming from a self onto itself
[
https://issues.apache.org/jira/browse/MRESOLVER-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MRESOLVER-614.
-
Resolution: Fixed
> Collector applies depMgt entries coming from a self onto itself
> ---
>
> Key: MRESOLVER-614
> URL: https://issues.apache.org/jira/browse/MRESOLVER-614
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 2.0.2
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.3
>
>
> In Maven3 this was not a problem, as Maven3 could add depMgt only on "root
> level".
> In Maven4 with use of new/old transitive Dependency Managers this became a
> problem. The dependency manager first receives depMgt entries for currently
> processed node, and then applies it onto same entry, overriding direct
> dependency versions.
> Example with Maven beta-5: it cannot build Resolver master
> (88a96ac0606d4d2372452a677d9f93c0b55105a4) as bnd-maven-plugin do depend on
> plexus-utils via path of {{bnd-maven-plugin > build-api > plexus-utils}} as
> it explodes due lack of org.plexus.utils.Scanner on classpath. This class was
> introduced in plexus-utils 1.5.8, and build-api do depend on it. But alas,
> build-api parent contains depMgt entry for plexus-utils 1.5.5 and is applied
> onto build-api overriding it's own dependency version.
> Basically current resolver code is NOT prepared for any "transitive
> dependency management" (despite DependencyManagers are there) as node would
> apply it's own depManagement rules onto itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MRESOLVER-614] Do not apply depMgt onto itself [maven-resolver]
cstamas merged PR #588: URL: https://github.com/apache/maven-resolver/pull/588 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8358) Semi-generated dependency graph
[ https://issues.apache.org/jira/browse/MNG-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8358. Fix Version/s: 4.0.0-beta-6 Assignee: Guillaume Nodet Resolution: Fixed > Semi-generated dependency graph > --- > > Key: MNG-8358 > URL: https://issues.apache.org/jira/browse/MNG-8358 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-6 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1829 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8328] Clean up assembly from Jansi remains and add JLine native libraries [maven]
gnodet merged PR #1839: URL: https://github.com/apache/maven/pull/1839 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8358] Semi-generated dependency graph [maven]
gnodet merged PR #1829: URL: https://github.com/apache/maven/pull/1829 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8357) Bump org.codehaus.mojo:exec-maven-plugin from 3.4.1 to 3.5.0
[ https://issues.apache.org/jira/browse/MNG-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8357. Fix Version/s: 4.0.0-beta-6 Assignee: Guillaume Nodet Resolution: Fixed > Bump org.codehaus.mojo:exec-maven-plugin from 3.4.1 to 3.5.0 > > > Key: MNG-8357 > URL: https://issues.apache.org/jira/browse/MNG-8357 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-6 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1833 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8265) Dependency should inherit properties like parent
[
https://issues.apache.org/jira/browse/MNG-8265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
abccbaandy updated MNG-8265:
Description:
Now only parent have these feature, but sometimes we need some properties from
the dependency too.
For ex:
We have a spring project
{code:xml}
org.springframework.boot
spring-boot-starter-parent
3.3.4
org.springframework.boot
spring-boot-starter-data-neo4j
org.neo4j
neo4j-cypher-dsl-parser
${cypher-dsl.version}
{code}
If I want reuse the properties in the child of
`spring-boot-starter-data-neo4j`, it's not possible right now.
The {{cypher-dsl.version}} is from {{spring-boot-starter-data-neo4j}}
https://github.com/spring-projects/spring-data-neo4j/blob/7.3.3/pom.xml#L79
was:
Now only parent have these feature, but sometimes we need some properties from
the dependency too.
For ex:
We have a spring project
{code:xml}
org.springframework.boot
spring-boot-starter-parent
3.3.4
org.springframework.boot
spring-boot-starter-data-neo4j
{code}
If I want reuse the properties in the child of
`spring-boot-starter-data-neo4j`, it's not possible right now.
> Dependency should inherit properties like parent
>
>
> Key: MNG-8265
> URL: https://issues.apache.org/jira/browse/MNG-8265
> Project: Maven
> Issue Type: Improvement
>Reporter: abccbaandy
>Priority: Major
>
> Now only parent have these feature, but sometimes we need some properties
> from the dependency too.
> For ex:
> We have a spring project
> {code:xml}
>
> org.springframework.boot
> spring-boot-starter-parent
> 3.3.4
>
>
>
>
> org.springframework.boot
> spring-boot-starter-data-neo4j
>
>
>org.neo4j
>neo4j-cypher-dsl-parser
>${cypher-dsl.version}
>
>
> {code}
> If I want reuse the properties in the child of
> `spring-boot-starter-data-neo4j`, it's not possible right now.
> The {{cypher-dsl.version}} is from {{spring-boot-starter-data-neo4j}}
> https://github.com/spring-projects/spring-data-neo4j/blob/7.3.3/pom.xml#L79
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8265) Dependency should inherit properties like parent
[
https://issues.apache.org/jira/browse/MNG-8265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892479#comment-17892479
]
abccbaandy commented on MNG-8265:
-
I have update the description, hope it's explain my issue more clearly.
> Dependency should inherit properties like parent
>
>
> Key: MNG-8265
> URL: https://issues.apache.org/jira/browse/MNG-8265
> Project: Maven
> Issue Type: Improvement
>Reporter: abccbaandy
>Priority: Major
>
> Now only parent have these feature, but sometimes we need some properties
> from the dependency too.
> For ex:
> We have a spring project
> {code:xml}
>
> org.springframework.boot
> spring-boot-starter-parent
> 3.3.4
>
>
>
>
> org.springframework.boot
> spring-boot-starter-data-neo4j
>
>
>org.neo4j
>neo4j-cypher-dsl-parser
>${cypher-dsl.version}
>
>
> {code}
> If I want reuse the properties in the child of
> `spring-boot-starter-data-neo4j`, it's not possible right now.
> The {{cypher-dsl.version}} is from {{spring-boot-starter-data-neo4j}}
> https://github.com/spring-projects/spring-data-neo4j/blob/7.3.3/pom.xml#L79
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MRESOLVER-620) (build) Bump exec-maven-plugin to 3.5.0
[ https://issues.apache.org/jira/browse/MRESOLVER-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-620. - Resolution: Fixed > (build) Bump exec-maven-plugin to 3.5.0 > --- > > Key: MRESOLVER-620 > URL: https://issues.apache.org/jira/browse/MRESOLVER-620 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Updates [maven-resolver]
cstamas merged PR #589: URL: https://github.com/apache/maven-resolver/pull/589 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (MRESOLVER-616) (build) Bump testcontainersVersion from 1.20.2 to 1.20.3
[ https://issues.apache.org/jira/browse/MRESOLVER-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-616: - Assignee: Tamas Cservenak > (build) Bump testcontainersVersion from 1.20.2 to 1.20.3 > > > Key: MRESOLVER-616 > URL: https://issues.apache.org/jira/browse/MRESOLVER-616 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-617) Bump org.apache.velocity:velocity-engine-core from 2.4 to 2.4.1
[ https://issues.apache.org/jira/browse/MRESOLVER-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-617. - Resolution: Fixed > Bump org.apache.velocity:velocity-engine-core from 2.4 to 2.4.1 > --- > > Key: MRESOLVER-617 > URL: https://issues.apache.org/jira/browse/MRESOLVER-617 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-617) Bump org.apache.velocity:velocity-engine-core from 2.4 to 2.4.1
[ https://issues.apache.org/jira/browse/MRESOLVER-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-617: - Assignee: Tamas Cservenak > Bump org.apache.velocity:velocity-engine-core from 2.4 to 2.4.1 > --- > > Key: MRESOLVER-617 > URL: https://issues.apache.org/jira/browse/MRESOLVER-617 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-616) (build) Bump testcontainersVersion from 1.20.2 to 1.20.3
[ https://issues.apache.org/jira/browse/MRESOLVER-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-616. - Resolution: Fixed > (build) Bump testcontainersVersion from 1.20.2 to 1.20.3 > > > Key: MRESOLVER-616 > URL: https://issues.apache.org/jira/browse/MRESOLVER-616 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-618) (build) Bump org.mockito:mockito-core from 5.14.1 to 5.14.2
[ https://issues.apache.org/jira/browse/MRESOLVER-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-618: - Assignee: Tamas Cservenak > (build) Bump org.mockito:mockito-core from 5.14.1 to 5.14.2 > --- > > Key: MRESOLVER-618 > URL: https://issues.apache.org/jira/browse/MRESOLVER-618 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-618) (build) Bump org.mockito:mockito-core from 5.14.1 to 5.14.2
[ https://issues.apache.org/jira/browse/MRESOLVER-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-618. - Resolution: Fixed > (build) Bump org.mockito:mockito-core from 5.14.1 to 5.14.2 > --- > > Key: MRESOLVER-618 > URL: https://issues.apache.org/jira/browse/MRESOLVER-618 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-615) Increase default HTTP timeouts
[
https://issues.apache.org/jira/browse/MRESOLVER-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-615:
--
Description: Increased connect timeout from 10sec to 30sec. (was: As with
apache transport that was hidden so far (see MRESOLVER-612), but with new HTTP
Transports like JDK or Jetty which both obey
{{org.eclipse.aether.ConfigurationProperties#REQUEST_TIMEOUT}} it proves short.)
> Increase default HTTP timeouts
> --
>
> Key: MRESOLVER-615
> URL: https://issues.apache.org/jira/browse/MRESOLVER-615
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.3
>
>
> Increased connect timeout from 10sec to 30sec.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MRESOLVER-619) Bump org.codehaus.plexus:plexus-xml from 3.0.1 to 4.0.4
[ https://issues.apache.org/jira/browse/MRESOLVER-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-619. - Resolution: Won't Fix > Bump org.codehaus.plexus:plexus-xml from 3.0.1 to 4.0.4 > --- > > Key: MRESOLVER-619 > URL: https://issues.apache.org/jira/browse/MRESOLVER-619 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-619) Bump org.codehaus.plexus:plexus-xml from 3.0.1 to 4.0.4
[ https://issues.apache.org/jira/browse/MRESOLVER-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-619: -- Fix Version/s: (was: 2.0.3) > Bump org.codehaus.plexus:plexus-xml from 3.0.1 to 4.0.4 > --- > > Key: MRESOLVER-619 > URL: https://issues.apache.org/jira/browse/MRESOLVER-619 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-619) Bump org.codehaus.plexus:plexus-xml from 3.0.1 to 4.0.4
[ https://issues.apache.org/jira/browse/MRESOLVER-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892437#comment-17892437 ] Tamas Cservenak commented on MRESOLVER-619: --- Merged then undone, not doing this in 2.0.3. > Bump org.codehaus.plexus:plexus-xml from 3.0.1 to 4.0.4 > --- > > Key: MRESOLVER-619 > URL: https://issues.apache.org/jira/browse/MRESOLVER-619 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-7554) Lift JDK minimum to JDK 11
[ https://issues.apache.org/jira/browse/MNG-7554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-7554. Resolution: Duplicate > Lift JDK minimum to JDK 11 > -- > > Key: MNG-7554 > URL: https://issues.apache.org/jira/browse/MNG-7554 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-612) Align connect and request timeout interpretation by HTTP transports
[
https://issues.apache.org/jira/browse/MRESOLVER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892514#comment-17892514
]
ASF GitHub Bot commented on MRESOLVER-612:
--
cstamas merged PR #587:
URL: https://github.com/apache/maven-resolver/pull/587
> Align connect and request timeout interpretation by HTTP transports
> ---
>
> Key: MRESOLVER-612
> URL: https://issues.apache.org/jira/browse/MRESOLVER-612
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.3
>
>
> By default, {{jetty}} and {{jdk}} are fully (almost) aligned how they
> interpret these two timeouts, but {{apache}} was totally off.
> Make sure all HTTP transport can work in same way, as regards timeouts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNGSITE-393) Remove references to Maven 2.x
[ https://issues.apache.org/jira/browse/MNGSITE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892612#comment-17892612 ] ASF GitHub Bot commented on MNGSITE-393: elharo merged PR #565: URL: https://github.com/apache/maven-site/pull/565 > Remove references to Maven 2.x > -- > > Key: MNGSITE-393 > URL: https://issues.apache.org/jira/browse/MNGSITE-393 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > Time Spent: 4h > Remaining Estimate: 0h > > Maven 3.x is over a decade old now and we're talking about Maven 4. It's time > to clean out all the random discussion here and there about how Maven 2.x did > things, differences between Maven 2 and 3, what works in Maven 3 but not 2, > etc. > Assume Maven 3.0 as the minimum, probably Maven 3.1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNGSITE-393) Remove references to Maven 2.x
[ https://issues.apache.org/jira/browse/MNGSITE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892613#comment-17892613 ] ASF GitHub Bot commented on MNGSITE-393: elharo merged PR #567: URL: https://github.com/apache/maven-site/pull/567 > Remove references to Maven 2.x > -- > > Key: MNGSITE-393 > URL: https://issues.apache.org/jira/browse/MNGSITE-393 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > Time Spent: 4h > Remaining Estimate: 0h > > Maven 3.x is over a decade old now and we're talking about Maven 4. It's time > to clean out all the random discussion here and there about how Maven 2.x did > things, differences between Maven 2 and 3, what works in Maven 3 but not 2, > etc. > Assume Maven 3.0 as the minimum, probably Maven 3.1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNGSITE-393] Remove Maven 2.0 content [maven-site]
elharo merged PR #565: URL: https://github.com/apache/maven-site/pull/565 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] We almost use exclusively use Github PRs nowadays instead of patches [maven-site]
elharo closed pull request #570: We almost use exclusively use Github PRs nowadays instead of patches URL: https://github.com/apache/maven-site/pull/570 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MNG-8360) Profile activation regression in beta5
Matt Nelson created MNG-8360:
Summary: Profile activation regression in beta5
Key: MNG-8360
URL: https://issues.apache.org/jira/browse/MNG-8360
Project: Maven
Issue Type: Bug
Affects Versions: 4.0.0-beta-5
Reporter: Matt Nelson
Profile activation for submodules is no longer working with 4.0.0-beta-5, it
was working with 4.0.0-beta-4.
Reproducer
https://github.com/mattnelson/maven-examples/tree/profile_activation
beta4
{noformat}
[INFO] --- help:3.5.1:active-profiles (default-cli) @ profiles ---
[INFO]
Active Profiles for Project 'com.github.mattnelson:profiles:pom:1.0.0-SNAPSHOT':
The following profiles are active:
- settings-xml-activeProfiles (source: external)
- profile_active_from_mvn_config (source:
/Users/Shared/DevBuild/code/maven-examples/pom.xml)
Active Profiles for Project 'com.github.mattnelson:module1:pom:1.0.0-SNAPSHOT':
The following profiles are active:
- settings-xml-activeProfiles (source: external)
- profile_active_from_mvn_config (source:
/Users/Shared/DevBuild/code/maven-examples/pom.xml)
{noformat}
beta5
{noformat}
[INFO] --- help:3.5.1:active-profiles (default-cli) @ profiles ---
[INFO]
Active Profiles for Project 'com.github.mattnelson:profiles:pom:1.0.0-SNAPSHOT':
The following profiles are active:
- settings-xml-activeProfiles (source: external)
- profile_active_from_mvn_config (source:
com.github.mattnelson:profiles:pom:1.0.0-SNAPSHOT)
- profile_active_from_condition (source:
com.github.mattnelson:profiles:pom:1.0.0-SNAPSHOT)
Active Profiles for Project 'com.github.mattnelson:module1:pom:1.0.0-SNAPSHOT':
The following profiles are active:
- settings-xml-activeProfiles (source: external)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRESOLVER-614) Collector applies depMgt entries coming from a self onto itself
[
https://issues.apache.org/jira/browse/MRESOLVER-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892566#comment-17892566
]
Tamas Cservenak commented on MRESOLVER-614:
---
Since then reproducer updated with multiple examples, and explanations. This
will make an IT.
> Collector applies depMgt entries coming from a self onto itself
> ---
>
> Key: MRESOLVER-614
> URL: https://issues.apache.org/jira/browse/MRESOLVER-614
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 2.0.2
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.3
>
>
> In Maven3 this was not a problem, as Maven3 could add depMgt only on "root
> level".
> In Maven4 with use of new/old transitive Dependency Managers this became a
> problem. The dependency manager first receives depMgt entries for currently
> processed node, and then applies it onto same entry, overriding direct
> dependency versions.
> Example with Maven beta-5: it cannot build Resolver master
> (88a96ac0606d4d2372452a677d9f93c0b55105a4) as bnd-maven-plugin do depend on
> plexus-utils via path of {{bnd-maven-plugin > build-api > plexus-utils}} as
> it explodes due lack of org.plexus.utils.Scanner on classpath. This class was
> introduced in plexus-utils 1.5.8, and build-api do depend on it. But alas,
> build-api parent contains depMgt entry for plexus-utils 1.5.5 and is applied
> onto build-api overriding it's own dependency version.
> Basically current resolver code is NOT prepared for any "transitive
> dependency management" (despite DependencyManagers are there) as node would
> apply it's own depManagement rules onto itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MRESOLVER-618) (build) Bump org.mockito:mockito-core from 5.14.1 to 5.14.2
[ https://issues.apache.org/jira/browse/MRESOLVER-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-618: -- Component/s: Resolver > (build) Bump org.mockito:mockito-core from 5.14.1 to 5.14.2 > --- > > Key: MRESOLVER-618 > URL: https://issues.apache.org/jira/browse/MRESOLVER-618 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-614) Collector applies depMgt entries coming from a self onto itself
[
https://issues.apache.org/jira/browse/MRESOLVER-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892546#comment-17892546
]
Tamas Cservenak commented on MRESOLVER-614:
---
So here is a reproducer:
https://github.com/cstamas/MRESOLVER-614
Notice how 3.9.9 claims level3 is 1.0.0, while 4.0.0-beta-5 says is 1.0.1 --
wrongly. As there is this:
https://github.com/cstamas/MRESOLVER-614/blob/main/local-repo/org/apache/maven/it/mresolver614/level2/1.0.0/level2-1.0.0.pom
So what happens is that level2 depMgt overrides its own dep definitions.
Basically "in parent" does not matter, just like I assumed.
> Collector applies depMgt entries coming from a self onto itself
> ---
>
> Key: MRESOLVER-614
> URL: https://issues.apache.org/jira/browse/MRESOLVER-614
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 2.0.2
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.3
>
>
> In Maven3 this was not a problem, as Maven3 could add depMgt only on "root
> level".
> In Maven4 with use of new/old transitive Dependency Managers this became a
> problem. The dependency manager first receives depMgt entries for currently
> processed node, and then applies it onto same entry, overriding direct
> dependency versions.
> Example with Maven beta-5: it cannot build Resolver master
> (88a96ac0606d4d2372452a677d9f93c0b55105a4) as bnd-maven-plugin do depend on
> plexus-utils via path of {{bnd-maven-plugin > build-api > plexus-utils}} as
> it explodes due lack of org.plexus.utils.Scanner on classpath. This class was
> introduced in plexus-utils 1.5.8, and build-api do depend on it. But alas,
> build-api parent contains depMgt entry for plexus-utils 1.5.5 and is applied
> onto build-api overriding it's own dependency version.
> Basically current resolver code is NOT prepared for any "transitive
> dependency management" (despite DependencyManagers are there) as node would
> apply it's own depManagement rules onto itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MRESOLVER-612] Align timeout interpretations across HTTP transports [maven-resolver]
cstamas merged PR #587: URL: https://github.com/apache/maven-resolver/pull/587 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-614) Collector applies depMgt entries coming from a self onto itself
[
https://issues.apache.org/jira/browse/MRESOLVER-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892535#comment-17892535
]
Tamas Cservenak commented on MRESOLVER-614:
---
No, I disagree with your assessment, and while true that we see "slight"
differences between (non-transitive) Maven3 and (transitive) Maven4, I am
pretty much sure it is due this issue. In general, transitive depMgt handling
should just improve things IMO.
When I say "in parent", I literally meant "in parent POM", but resolver
receives model builder built POM (hence, same would be true, if a POM is at
n-depth, and contains depMgt entry for Dv1 while it contains dep entry for
Dv2... Dv1 would "won". Resolver is not aware that depMgt is "in parent" nor is
important. The important bit is that depMgt from node at n-depth should be
applied only on n+1 and below depth (to children, so to say, so it's own
dependency dependencies, just like in your POM, the depMgt is not overriding
your deps).
Anyway, the PR looks good IMO and also seems to work (due this issue, Maven 4
beta-5 is unable to build Maven Resolver master, with this patch it can).
> Collector applies depMgt entries coming from a self onto itself
> ---
>
> Key: MRESOLVER-614
> URL: https://issues.apache.org/jira/browse/MRESOLVER-614
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 2.0.2
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.3
>
>
> In Maven3 this was not a problem, as Maven3 could add depMgt only on "root
> level".
> In Maven4 with use of new/old transitive Dependency Managers this became a
> problem. The dependency manager first receives depMgt entries for currently
> processed node, and then applies it onto same entry, overriding direct
> dependency versions.
> Example with Maven beta-5: it cannot build Resolver master
> (88a96ac0606d4d2372452a677d9f93c0b55105a4) as bnd-maven-plugin do depend on
> plexus-utils via path of {{bnd-maven-plugin > build-api > plexus-utils}} as
> it explodes due lack of org.plexus.utils.Scanner on classpath. This class was
> introduced in plexus-utils 1.5.8, and build-api do depend on it. But alas,
> build-api parent contains depMgt entry for plexus-utils 1.5.5 and is applied
> onto build-api overriding it's own dependency version.
> Basically current resolver code is NOT prepared for any "transitive
> dependency management" (despite DependencyManagers are there) as node would
> apply it's own depManagement rules onto itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-8345] Maven generates both settings 1.3.0 and 2.0.0 [maven]
gnodet merged PR #1835: URL: https://github.com/apache/maven/pull/1835 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-8300) [REGRESSION] colorized transfer messages broken
[ https://issues.apache.org/jira/browse/MNG-8300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8300: - Priority: Minor (was: Major) > [REGRESSION] colorized transfer messages broken > --- > > Key: MNG-8300 > URL: https://issues.apache.org/jira/browse/MNG-8300 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-12, 4.0.0-beta-4 >Reporter: Herve Boutemy >Priority: Minor > Fix For: 4.0.0-beta-6 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, > screenshot-4.png, screenshot-5.png, screenshot-6.png > > > colorized transfer messages implemented in Maven 4.0.0-alpha-8 in MNG-7875 > but it seems MNG-7995 in Maven 4.0.0-alpha-11 broke it, and went unnoticed > until now 4.0.0-beta-4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8359) Merged Docgen tool with Resolver one
Tamas Cservenak created MNG-8359: Summary: Merged Docgen tool with Resolver one Key: MNG-8359 URL: https://issues.apache.org/jira/browse/MNG-8359 Project: Maven Issue Type: Task Components: Sites & Reporting Reporter: Tamas Cservenak Fix For: 4.0.0-beta-6 As currently they are diverged copy-paste -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8349] Avoid exceptions with invalid modelVersion [maven]
gnodet merged PR #1848: URL: https://github.com/apache/maven/pull/1848 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8350] Improve storage and computation of locations in model objects [maven]
gnodet merged PR #1847: URL: https://github.com/apache/maven/pull/1847 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MRESOLVER-623) Merge Docgen tool with Maven one
[ https://issues.apache.org/jira/browse/MRESOLVER-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-623: -- Summary: Merge Docgen tool with Maven one (was: Merged Docgen tool with Maven one) > Merge Docgen tool with Maven one > > > Key: MRESOLVER-623 > URL: https://issues.apache.org/jira/browse/MRESOLVER-623 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > > As currently they are diverged copy-paste -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8359) Merge Docgen tool with Resolver one
[ https://issues.apache.org/jira/browse/MNG-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8359: - Summary: Merge Docgen tool with Resolver one (was: Merged Docgen tool with Resolver one) > Merge Docgen tool with Resolver one > --- > > Key: MNG-8359 > URL: https://issues.apache.org/jira/browse/MNG-8359 > Project: Maven > Issue Type: Task > Components: Sites & Reporting >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-beta-6 > > > As currently they are diverged copy-paste -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8349) NumberFormatException during model building
[
https://issues.apache.org/jira/browse/MNG-8349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8349.
Resolution: Fixed
> NumberFormatException during model building
> ---
>
> Key: MNG-8349
> URL: https://issues.apache.org/jira/browse/MNG-8349
> Project: Maven
> Issue Type: Bug
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-beta-6
>
>
> {code}
>
> 4..0.0
> org.test
> foo
> 1.0-SNAPSHOT
> jar
>
> {code}
> The above pom.xml leads to the following error:
> {code}
> [INFO] Scanning for projects...
> [ERROR] Internal error: java.lang.NumberFormatException: For input string: ""
> -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NumberFormatException: For input string: ""
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:157)
> at
> org.apache.maven.cling.invoker.mvn.DefaultMavenInvoker.doExecute(DefaultMavenInvoker.java:496)
> at
> org.apache.maven.cling.invoker.mvn.DefaultMavenInvoker.execute(DefaultMavenInvoker.java:113)
> at
> org.apache.maven.cling.invoker.mvn.DefaultMavenInvoker.execute(DefaultMavenInvoker.java:80)
> at
> org.apache.maven.cling.invoker.LookupInvoker.doInvoke(LookupInvoker.java:235)
> at
> org.apache.maven.cling.invoker.LookupInvoker.invoke(LookupInvoker.java:210)
> at org.apache.maven.cling.ClingSupport.run(ClingSupport.java:68)
> at org.apache.maven.cling.MavenCling.main(MavenCling.java:51)
> at
> jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke(Method.java:580)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:255)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:201)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:361)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:314)
> Caused by: java.lang.NumberFormatException: For input string: ""
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:67)
> at java.lang.Long.parseLong(Long.java:719)
> at java.lang.Long.valueOf(Long.java:1157)
> at
> org.apache.maven.internal.impl.model.DefaultModelValidator.compareModelVersions(DefaultModelValidator.java:1967)
> at
> org.apache.maven.internal.impl.model.DefaultModelValidator.validateModelVersion(DefaultModelValidator.java:1911)
> at
> org.apache.maven.internal.impl.model.DefaultModelValidator.validateFileModel(DefaultModelValidator.java:367)
> at
> org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.doReadFileModel(DefaultModelBuilder.java:1434)
> at
> org.apache.maven.internal.impl.model.DefaultModelCache$CachingSupplier.get(DefaultModelCache.java:178)
> at
> org.apache.maven.internal.impl.model.DefaultModelCache.computeIfAbsent(DefaultModelCache.java:65)
> at
> org.apache.maven.internal.impl.model.DefaultModelCache.computeIfAbsent(DefaultModelCache.java:56)
> at
> org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.cache(DefaultModelBuilder.java:1734)
> at
> org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.readFileModel(DefaultModelBuilder.java:1239)
> at
> org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.loadFilePom(DefaultModelBuilder.java:733)
> at
> org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.loadFromRoot(DefaultModelBuilder.java:711)
> at
> org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.buildBuildPom(DefaultModelBuilder.java:658)
> at
> org.apache.maven.internal.impl.model.DefaultModelBuilder$1.build(DefaultModelBuilder.java:226)
> at
> org.apache.maven.project.DefaultProjectBuilder$BuildSession.build(DefaultProjectBuilder.java:497)
> at
> org.apache.maven.project.DefaultProjectBuilder$BuildSession.lambda$doBuild$5(DefaultProjectBuilder.java:474)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at java.util.Collections$2.tryAdvance(Collections.java:5073)
> at java.util.Collections$2.forEachRemaining(Collections.java:5081)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
> at
> java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java
[jira] [Closed] (MNG-8350) Improve storage and computation of locations in model objects
[
https://issues.apache.org/jira/browse/MNG-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8350.
Fix Version/s: 4.0.0-beta-6
Resolution: Fixed
> Improve storage and computation of locations in model objects
> -
>
> Key: MNG-8350
> URL: https://issues.apache.org/jira/browse/MNG-8350
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-beta-5
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-beta-6
>
>
> The {{Build}} constructor has the following code:
> {code}
> Map newlocs = builder.locations != null ?
> builder.locations : Collections.emptyMap();
> Map oldlocs = builder.base != null &&
> builder.base.locations != null ? builder.base.locations :
> Collections.emptyMap();
> Map mutableLocations = new
> HashMap<>(super.locations);
> mutableLocations.put("sourceDirectory",
> newlocs.containsKey("sourceDirectory") ? newlocs.get("sourceDirectory") :
> oldlocs.get("sourceDirectory"));
> mutableLocations.put("scriptSourceDirectory",
> newlocs.containsKey("scriptSourceDirectory") ?
> newlocs.get("scriptSourceDirectory") : oldlocs.get("scriptSourceDirectory"));
> mutableLocations.put("testSourceDirectory",
> newlocs.containsKey("testSourceDirectory") ?
> newlocs.get("testSourceDirectory") : oldlocs.get("testSourceDirectory"));
> mutableLocations.put("outputDirectory",
> newlocs.containsKey("outputDirectory") ? newlocs.get("outputDirectory") :
> oldlocs.get("outputDirectory"));
> mutableLocations.put("testOutputDirectory",
> newlocs.containsKey("testOutputDirectory") ?
> newlocs.get("testOutputDirectory") : oldlocs.get("testOutputDirectory"));
> mutableLocations.put("extensions", newlocs.containsKey("extensions")
> ? newlocs.get("extensions") : oldlocs.get("extensions"));
> this.locations = Collections.unmodifiableMap(mutableLocations);
> {code}
> This is inefficient, especially when building models programmatically, in
> which cases locations are usually not set. The code will always store a
> {{null}} value for each key, whereas an empty map could be sufficient if
> there's no actual values.
> The generator code is located at:
> https://github.com/apache/maven/blob/b370e5e9299813e6df483bac049ec162b86fb7e8/src/mdo/model.vm#L174-L186
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-623) Merge Docgen tool with Maven one
[ https://issues.apache.org/jira/browse/MRESOLVER-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-623: - Assignee: Tamas Cservenak > Merge Docgen tool with Maven one > > > Key: MRESOLVER-623 > URL: https://issues.apache.org/jira/browse/MRESOLVER-623 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.3 > > > As currently they are diverged copy-paste -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8189) Warn about plugin versions not pinned for all lifecycles
[
https://issues.apache.org/jira/browse/MNG-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8189.
Resolution: Fixed
> Warn about plugin versions not pinned for all lifecycles
>
>
> Key: MNG-8189
> URL: https://issues.apache.org/jira/browse/MNG-8189
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Affects Versions: 4.0.0-beta-3
>Reporter: Karl Heinz Marbaise
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-beta-6
>
>
> h3. Context
> Based on [MNG-6562|https://issues.apache.org/jira/browse/MNG-6562] Maven will
> produce a WARNING if plugin(s) are not defined with version in
> pluginManagement.
> h3. Problem
> If Maven is called like this:
> {code}
> mvn clean
> {code}
> there is no such WARNING emitted (for example for the maven-clean-plugin).
> h3. Goal
> We should emit a warning(s) for each life cycle {{clean}} and also for
> {{site}} life cycle in such cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MNG-8359) Merge Docgen tool with Resolver one
[ https://issues.apache.org/jira/browse/MNG-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8359: Assignee: Tamas Cservenak > Merge Docgen tool with Resolver one > --- > > Key: MNG-8359 > URL: https://issues.apache.org/jira/browse/MNG-8359 > Project: Maven > Issue Type: Task > Components: Sites & Reporting >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-beta-6 > > > As currently they are diverged copy-paste -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8189] Warn about plugin versions not pinned for all lifecycles [maven]
gnodet merged PR #1846: URL: https://github.com/apache/maven/pull/1846 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOURCES-237) Resource plugin's handling of symbolic links changed in 3.0.x, broke existing behavior
[
https://issues.apache.org/jira/browse/MRESOURCES-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892543#comment-17892543
]
Eduardo Rodrigues commented on MRESOURCES-237:
--
I'm facing this very same issue as well, and I 100% agree with the expectation
that there should be a configuration property to drive the desired behavior.
> Resource plugin's handling of symbolic links changed in 3.0.x, broke existing
> behavior
> --
>
> Key: MRESOURCES-237
> URL: https://issues.apache.org/jira/browse/MRESOURCES-237
> Project: Maven Resources Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.1.0, 3.2.0
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T11:41:47-05:00)
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-200.fc25.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Brian D. Johnson
>Priority: Minor
> Fix For: 3.3.0
>
> Attachments: a.tgz
>
>
> It looks like the handling of symbolic links in the
> {{maven-resources-plugin}} has changed in version 3.0.x. I'm submitting a
> JIRA because it breaks the previous behavior and I have not been able to find
> this documented anywhere as an intended change.
> *Use case:* Multi-module maven project. We have a custom log4j2
> configuration file we use during testing. Instead of maintaining this file
> in multiple {{src/test/resources}} directories, we instead maintain a single
> copy of the file at the project's root level and create symbolic links from
> each module's {{src/test/resources}} directory to the file using relative
> paths.
> *2.7 Behavior:* the symlink was evaluated and the target file was copied to
> {{target/test-classes/}}.
> *3.0.x Behavior:* the symlink is copied to {{target/test-classes/}} verbatim.
> The symlink's relative path results in the symlink pointing to the wrong
> file location. The log4j2 configuration is not found.
> *Requested Change:* Either revert to the original 2.7 behavior, or document
> the change and provide a configuration parameter to allow the legacy behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRESOLVER-614) Collector applies depMgt entries coming from a self onto itself
[
https://issues.apache.org/jira/browse/MRESOLVER-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892541#comment-17892541
]
Didier Loiseau commented on MRESOLVER-614:
--
{quote}In general, transitive depMgt handling should just improve things IMO.
{quote}
Oh I totally agree with that. In fact, I would even argue that, if it causes
any issue, the project is probably misconfigured. But some may still consider
it a regression. (OTOH, they can continue to use Maven 3)
{quote}Resolver is not aware that depMgt is "in parent" nor is important.
{quote}
Yes indeed, in this case it is in parent but it could even be in the same pom.
{quote}The important bit is that depMgt from node at n-depth should be applied
only on n+1 and below depth (to children, so to say, so it's own dependency
dependencies, just like in your POM, the depMgt is not overriding your deps).
{quote}
That makes sense indeed. (y)
> Collector applies depMgt entries coming from a self onto itself
> ---
>
> Key: MRESOLVER-614
> URL: https://issues.apache.org/jira/browse/MRESOLVER-614
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 2.0.2
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.3
>
>
> In Maven3 this was not a problem, as Maven3 could add depMgt only on "root
> level".
> In Maven4 with use of new/old transitive Dependency Managers this became a
> problem. The dependency manager first receives depMgt entries for currently
> processed node, and then applies it onto same entry, overriding direct
> dependency versions.
> Example with Maven beta-5: it cannot build Resolver master
> (88a96ac0606d4d2372452a677d9f93c0b55105a4) as bnd-maven-plugin do depend on
> plexus-utils via path of {{bnd-maven-plugin > build-api > plexus-utils}} as
> it explodes due lack of org.plexus.utils.Scanner on classpath. This class was
> introduced in plexus-utils 1.5.8, and build-api do depend on it. But alas,
> build-api parent contains depMgt entry for plexus-utils 1.5.5 and is applied
> onto build-api overriding it's own dependency version.
> Basically current resolver code is NOT prepared for any "transitive
> dependency management" (despite DependencyManagers are there) as node would
> apply it's own depManagement rules onto itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Undo P-X raise [maven-resolver]
cstamas merged PR #590: URL: https://github.com/apache/maven-resolver/pull/590 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MNG-8355) Bump org.apache.velocity:velocity-engine-core from 2.4 to 2.4.1
Guillaume Nodet created MNG-8355: Summary: Bump org.apache.velocity:velocity-engine-core from 2.4 to 2.4.1 Key: MNG-8355 URL: https://issues.apache.org/jira/browse/MNG-8355 Project: Maven Issue Type: Task Reporter: Guillaume Nodet GitHub Pull Request: https://github.com/apache/maven/pull/1831 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8353) Bump com.fasterxml.woodstox:woodstox-core from 7.0.0 to 7.1.0
Guillaume Nodet created MNG-8353: Summary: Bump com.fasterxml.woodstox:woodstox-core from 7.0.0 to 7.1.0 Key: MNG-8353 URL: https://issues.apache.org/jira/browse/MNG-8353 Project: Maven Issue Type: Task Reporter: Guillaume Nodet GitHub Pull Request: https://github.com/apache/maven/pull/1834 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8344] Support multiple operators in variable expansion [maven]
gnodet merged PR #1832: URL: https://github.com/apache/maven/pull/1832 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MNG-8352) Bump net.bytebuddy:byte-buddy from 1.15.5 to 1.15.7
Guillaume Nodet created MNG-8352: Summary: Bump net.bytebuddy:byte-buddy from 1.15.5 to 1.15.7 Key: MNG-8352 URL: https://issues.apache.org/jira/browse/MNG-8352 Project: Maven Issue Type: Task Reporter: Guillaume Nodet GitHub Pull Request: https://github.com/apache/maven/pull/1845 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8354) Bump org.junit:junit-bom from 5.11.2 to 5.11.3
Guillaume Nodet created MNG-8354: Summary: Bump org.junit:junit-bom from 5.11.2 to 5.11.3 Key: MNG-8354 URL: https://issues.apache.org/jira/browse/MNG-8354 Project: Maven Issue Type: Task Reporter: Guillaume Nodet GitHub Pull Request: https://github.com/apache/maven/pull/1830 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8356) [MNG-8344] Support multiple operators in variable expansion
[ https://issues.apache.org/jira/browse/MNG-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8356. Resolution: Duplicate > [MNG-8344] Support multiple operators in variable expansion > --- > > Key: MNG-8356 > URL: https://issues.apache.org/jira/browse/MNG-8356 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > > GitHub Pull Request: https://github.com/apache/maven/pull/1832 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8342] Add command line and terminal information when verbose [maven]
gnodet merged PR #1840: URL: https://github.com/apache/maven/pull/1840 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MNG-8357) Bump org.codehaus.mojo:exec-maven-plugin from 3.4.1 to 3.5.0
Guillaume Nodet created MNG-8357: Summary: Bump org.codehaus.mojo:exec-maven-plugin from 3.4.1 to 3.5.0 Key: MNG-8357 URL: https://issues.apache.org/jira/browse/MNG-8357 Project: Maven Issue Type: Task Reporter: Guillaume Nodet GitHub Pull Request: https://github.com/apache/maven/pull/1833 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8358) Semi-generated dependency graph
Guillaume Nodet created MNG-8358: Summary: Semi-generated dependency graph Key: MNG-8358 URL: https://issues.apache.org/jira/browse/MNG-8358 Project: Maven Issue Type: Task Reporter: Guillaume Nodet GitHub Pull Request: https://github.com/apache/maven/pull/1829 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8354] Bump org.junit:junit-bom from 5.11.2 to 5.11.3 [maven]
gnodet merged PR #1830: URL: https://github.com/apache/maven/pull/1830 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8348) Typos in message printed when using a deprecated option
[
https://issues.apache.org/jira/browse/MNG-8348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8348.
Resolution: Fixed
> Typos in message printed when using a deprecated option
> ---
>
> Key: MNG-8348
> URL: https://issues.apache.org/jira/browse/MNG-8348
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-beta-5
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.0.0-beta-6
>
>
> {code}
> ➜ pdfbox git:(trunk) mvn --debug --verbose
> Listening for transport dt_socket at address: 8000
> Detected deprecated option use in CLI
> The option -null,--debug is deprecated and will be removed in a future
> versionsince Maven 4.0.0
> {code}
> Note the {{-null}} and {{versionsince}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-8355] Bump org.apache.velocity:velocity-engine-core from 2.4 to 2.4.1 [maven]
gnodet merged PR #1831: URL: https://github.com/apache/maven/pull/1831 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8339) An error during transfer output seems to freeze the output
[
https://issues.apache.org/jira/browse/MNG-8339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8339.
Resolution: Fixed
> An error during transfer output seems to freeze the output
> --
>
> Key: MNG-8339
> URL: https://issues.apache.org/jira/browse/MNG-8339
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-beta-5
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-beta-6
>
>
> {code:java}
> Downloading from central:
> http://old-broken-macbook-pro.local:8082/artifactory/maven-remote/com/fasterxml/jackson/dataformat/jackson-dataformat-smile/2.18.0/jackson-dataformat-smile-2.18.0.jar
> [WARNING] [stderr] Exception in thread "Thread-2"
> java.lang.IllegalArgumentException: progressed file size cannot be greater
> than size: 179511 > 178405
> [WARNING] [stderr]at
> org.apache.maven.cli.transfer.FileSizeFormat.formatProgress(FileSizeFormat.java:189)
> [WARNING] [stderr]at
> org.apache.maven.cli.transfer.ConsoleMavenTransferListener.transferProgressed(ConsoleMavenTransferListener.java:99)
> [WARNING] [stderr]at
> org.apache.maven.cli.transfer.SimplexTransferListener.lambda$demux$0(SimplexTransferListener.java:116)
> [WARNING] [stderr]at
> org.apache.maven.cli.transfer.SimplexTransferListener$Exchange.process(SimplexTransferListener.java:204)
> [WARNING] [stderr]at
> org.apache.maven.cli.transfer.SimplexTransferListener.demux(SimplexTransferListener.java:105)
> [WARNING] [stderr]at
> org.apache.maven.cli.transfer.SimplexTransferListener.feedConsumer(SimplexTransferListener.java:96)
> [WARNING] [stderr]at java.base/java.lang.Thread.run(Thread.java:1570)
> {code}
> And then nothing...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Merge docgen [maven]
gnodet commented on code in PR #1849:
URL: https://github.com/apache/maven/pull/1849#discussion_r1815068048
##
maven-docgen/pom.xml:
##
@@ -99,10 +75,12 @@
verify
-
org.apache.maven.tools.CollectConfiguration
+
org.eclipse.aether.tools.CollectConfiguration
+--mode=maven
+
--templates=own-page.md,configuration.properties,configuration.yaml
${basedir}/..
-
${basedir}/../src/site/markdown/configuration.md
+${basedir}/target
Review Comment:
Is this change intended ?
--
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: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Closed] (MNG-8345) Maven generates both settings 1.3.0 and 2.0.0
[ https://issues.apache.org/jira/browse/MNG-8345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8345. Resolution: Fixed > Maven generates both settings 1.3.0 and 2.0.0 > - > > Key: MNG-8345 > URL: https://issues.apache.org/jira/browse/MNG-8345 > Project: Maven > Issue Type: Bug >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-6 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8348] Fix typos in deprecation warning message [maven]
gnodet merged PR #1844: URL: https://github.com/apache/maven/pull/1844 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-8342) Display full command line at debug level
[
https://issues.apache.org/jira/browse/MNG-8342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-8342:
-
Description:
When debugging, especially integration tests, it would be really useful to have
the full command line used to invoke maven.
At debug level, we could display:
* the command line
* the terminal information
The main use case is to be able to easily reproduce the invocation, preferably
using a simple copy/paste.
was:
When debugging, especially integration tests, it would be really useful to have
the full command line used to invoke maven.
At debug level, we could display:
* JVM arguments using
{{ManagementFactory.getRuntimeMXBean().getInputArguments()}}
* The parser request: {{org.apache.maven.api.cli.ParserRequest}} fields (maybe
not all)
The main use case is to be able to easily reproduce the invocation, preferably
using a simple copy/paste.
> Display full command line at debug level
>
>
> Key: MNG-8342
> URL: https://issues.apache.org/jira/browse/MNG-8342
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.0.0-beta-6
>
>
> When debugging, especially integration tests, it would be really useful to
> have the full command line used to invoke maven.
> At debug level, we could display:
> * the command line
> * the terminal information
> The main use case is to be able to easily reproduce the invocation,
> preferably using a simple copy/paste.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-8342) Display full command line at debug level
[ https://issues.apache.org/jira/browse/MNG-8342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8342. Resolution: Fixed > Display full command line at debug level > > > Key: MNG-8342 > URL: https://issues.apache.org/jira/browse/MNG-8342 > Project: Maven > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 4.0.0-beta-6 > > > When debugging, especially integration tests, it would be really useful to > have the full command line used to invoke maven. > At debug level, we could display: > * the command line > * the terminal information > The main use case is to be able to easily reproduce the invocation, > preferably using a simple copy/paste. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8330] Enforce attached artifacts to have the same GAV than their project [maven]
gnodet merged PR #1838: URL: https://github.com/apache/maven/pull/1838 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8330) Enforce attached artifacts to have the same GAV than their project
[ https://issues.apache.org/jira/browse/MNG-8330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8330. Resolution: Fixed > Enforce attached artifacts to have the same GAV than their project > -- > > Key: MNG-8330 > URL: https://issues.apache.org/jira/browse/MNG-8330 > Project: Maven > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-6 > > > The Maven 4 API currently allows such attachments with the > [ProjectManager|https://github.com/apache/maven/blob/30dc81227bf9c36d36f8549d22ab4c40bce60e77/api/maven-api-core/src/main/java/org/apache/maven/api/services/ProjectManager.java#L89]. > If needed a later step could involve dynamic subprojects which could be used > to attach artifacts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8344) Support multiple operators in variable expansion
[
https://issues.apache.org/jira/browse/MNG-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8344.
Resolution: Fixed
> Support multiple operators in variable expansion
>
>
> Key: MNG-8344
> URL: https://issues.apache.org/jira/browse/MNG-8344
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-beta-5
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.0.0-beta-6
>
>
> The following does not work:
> {code}
> maven.user.config =
> ${env.MAVEN_XDG:+${env.XDG_CONFIG_HOME:-${user.home}/.config}/maven}:-${user.home}/.m2}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (MNG-8265) Dependency should inherit properties like parent
[ https://issues.apache.org/jira/browse/MNG-8265 ]
Guillaume Nodet deleted comment on MNG-8265:
--
was (Author: gnt):
That's still unclear. Why do you need to reuse the {{cypher-dsl.version}}
property since the {{neo4j-cypher-dsl-bom}} BOM is imported and all the
dependencies will already be managed.
> Dependency should inherit properties like parent
>
>
> Key: MNG-8265
> URL: https://issues.apache.org/jira/browse/MNG-8265
> Project: Maven
> Issue Type: Improvement
>Reporter: abccbaandy
>Priority: Major
>
> Now only parent have these feature, but sometimes we need some properties
> from the dependency too.
> For ex:
> We have a spring project
> {code:xml}
>
> org.springframework.boot
> spring-boot-starter-parent
> 3.3.4
>
>
>
>
> org.springframework.boot
> spring-boot-starter-data-neo4j
>
>
>org.neo4j
>neo4j-cypher-dsl-parser
>${cypher-dsl.version}
>
>
> {code}
> If I want reuse the properties in the child of
> `spring-boot-starter-data-neo4j`, it's not possible right now.
> The {{cypher-dsl.version}} is from {{spring-boot-starter-data-neo4j}}
> https://github.com/spring-projects/spring-data-neo4j/blob/7.3.3/pom.xml#L79
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8265) Dependency should inherit properties like parent
[
https://issues.apache.org/jira/browse/MNG-8265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892489#comment-17892489
]
Guillaume Nodet commented on MNG-8265:
--
What about the following:
{code}
org.springframework.boot
spring-boot-starter-data-neo4j
pom>/type>
import
org.springframework.boot
spring-boot-starter-data-neo4j
org.neo4j
neo4j-cypher-dsl-parser
{code}
> Dependency should inherit properties like parent
>
>
> Key: MNG-8265
> URL: https://issues.apache.org/jira/browse/MNG-8265
> Project: Maven
> Issue Type: Improvement
>Reporter: abccbaandy
>Priority: Major
>
> Now only parent have these feature, but sometimes we need some properties
> from the dependency too.
> For ex:
> We have a spring project
> {code:xml}
>
> org.springframework.boot
> spring-boot-starter-parent
> 3.3.4
>
>
>
>
> org.springframework.boot
> spring-boot-starter-data-neo4j
>
>
>org.neo4j
>neo4j-cypher-dsl-parser
>${cypher-dsl.version}
>
>
> {code}
> If I want reuse the properties in the child of
> `spring-boot-starter-data-neo4j`, it's not possible right now.
> The {{cypher-dsl.version}} is from {{spring-boot-starter-data-neo4j}}
> https://github.com/spring-projects/spring-data-neo4j/blob/7.3.3/pom.xml#L79
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8340) Staged 4.0.0-beta5 broken by maven-shade-plugin
[
https://issues.apache.org/jira/browse/MNG-8340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892582#comment-17892582
]
Mateusz Gajewski commented on MNG-8340:
---
Is this an issue with the shade plugin or with the api it consumes?
> Staged 4.0.0-beta5 broken by maven-shade-plugin
> ---
>
> Key: MNG-8340
> URL: https://issues.apache.org/jira/browse/MNG-8340
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-beta-5
>Reporter: Mateusz Gajewski
>Priority: Major
> Fix For: 4.0.0-beta-6
>
>
> Reproduction: [https://github.com/trinodb/trino/pull/23849]
>
> Project structure:
> {code:java}
> > pom.xml
> > client/trino-cli/pom.xml (parent.relativePath = ../../pom.xml)
> {code}
> maven-shade-plugin writes trino-cli dependency reduced pom to:
> {code:java}
> ${project.build.directory}/pom.xml -> client/trino-cli/target/pom.xml{code}
> The file contains:
> {code:java}
>
>../../../pom.xml
> {code}
> which correctly points to root pom.xml
>
> This worked under beta4, fails under beta5 with:
> {code:java}
> [ERROR] - [FATAL] 'parent.relativePath' points at '../../../pom.xml' but
> no POM could be found, please verify your project structure @ line 3, column
> 3 {code}
> It seems that {{parent.relativePath}} is resolved against {{client/trino-cli
> instead of client/trino-cli/target}} where pom.xml is placed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNG-8349] Avoid exceptions with invalid modelVersion [maven]
gnodet opened a new pull request, #1848: URL: https://github.com/apache/maven/pull/1848 JIRA issue: [MNG-8349](https://issues.apache.org/jira/browse/MNG-8349) The output is now the expected one (albeit duplicated): ``` [INFO] Scanning for projects... [ERROR] Some problems were encountered while processing the POMs [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.test:foo:jar:1.0-SNAPSHOT (/Users/gnodet/tmp/MNG-8189/pom.xml) has 2 errors [ERROR] 'modelVersion' must be one of [4.0.0, 4.1.0] but is '4..0.0'. @ org.test:foo:1.0-SNAPSHOT, file:///Users/gnodet/tmp/MNG-8189/pom.xml, line 2, column 3 [ERROR] 'modelVersion' must be one of [4.0.0, 4.1.0] but is '4..0.0'. @ org.test:foo:1.0-SNAPSHOT, file:///Users/gnodet/tmp/MNG-8189/pom.xml, line 2, column 3 [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the '-e' switch [ERROR] Re-run Maven using the '-X' switch to enable verbose output [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException ``` -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Updates [maven-resolver]
cstamas opened a new pull request, #589: URL: https://github.com/apache/maven-resolver/pull/589 (no comment) -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MRESOLVER-616) (build) Bump testcontainersVersion from 1.20.2 to 1.20.3
Tamas Cservenak created MRESOLVER-616: - Summary: (build) Bump testcontainersVersion from 1.20.2 to 1.20.3 Key: MRESOLVER-616 URL: https://issues.apache.org/jira/browse/MRESOLVER-616 Project: Maven Resolver Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 2.0.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
