[jira] [Commented] (MSHARED-1445) Unix timestamps since the epoch are not subject to the boundary checks
[
https://issues.apache.org/jira/browse/MSHARED-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889494#comment-17889494
]
Michael Osipov commented on MSHARED-1445:
-
[~hboutemy], here it is.
> Unix timestamps since the epoch are not subject to the boundary checks
> --
>
> Key: MSHARED-1445
> URL: https://issues.apache.org/jira/browse/MSHARED-1445
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: maven-archiver-3.6.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: maven-archiver-4.0.0, maven-archiver-3.6.3,
> maven-archiver-4.0.0-beta-2
>
>
> The Javadoc says:
> {noformat}
> * @throws IllegalArgumentException if the outputTimestamp is neither ISO 8601
> nor an integer, or it's not within
> * the valid range 1980-01-01T00:00:02Z to 2099-12-31T23:59:59Z
> {noformat}
> but when a Unix timestamp since the epoch is passed it is simply passed
> through. No min/max check. We need to fix this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (MSHARED-1445) Unix timestamps since the epoch are not subject to the boundary checks
[ https://issues.apache.org/jira/browse/MSHARED-1445 ]
Michael Osipov deleted comment on MSHARED-1445:
-
was (Author: michael-o):
[~hboutemy], here it is.
> Unix timestamps since the epoch are not subject to the boundary checks
> --
>
> Key: MSHARED-1445
> URL: https://issues.apache.org/jira/browse/MSHARED-1445
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: maven-archiver-3.6.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: maven-archiver-4.0.0, maven-archiver-3.6.3,
> maven-archiver-4.0.0-beta-2
>
>
> The Javadoc says:
> {noformat}
> * @throws IllegalArgumentException if the outputTimestamp is neither ISO 8601
> nor an integer, or it's not within
> * the valid range 1980-01-01T00:00:02Z to 2099-12-31T23:59:59Z
> {noformat}
> but when a Unix timestamp since the epoch is passed it is simply passed
> through. No min/max check. We need to fix this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSHARED-1446) Add docs about repro build output timestamp boundaries
[
https://issues.apache.org/jira/browse/MSHARED-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889498#comment-17889498
]
Michael Osipov commented on MSHARED-1446:
-
[~hboutemy], here it is.
> Add docs about repro build output timestamp boundaries
> --
>
> Key: MSHARED-1446
> URL: https://issues.apache.org/jira/browse/MSHARED-1446
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-archiver
>Affects Versions: maven-archiver-3.6.2
>Reporter: Michael Osipov
>Priority: Major
>
> In MSHARED-1067 the boundaries have been introduced, but never documented by
> they actually exist. Reason: MS-DOS time limitation for 2+2 bytes starting
> from 1980. See ZIP note:
> {quote}
>4.4.6 date and time fields: (2 bytes each)
>The date and time are encoded in standard MS-DOS format.
>If input came from standard input, the date and time are
>those at which compression was started for this data.
>If encrypting the central directory and general purpose bit
>flag 13 is set indicating masking, the value stored in the
>Local Header will be zero. MS-DOS time format is different
>from more commonly used computer time formats such as
>UTC. For example, MS-DOS uses year values relative to 1980
>and 2 second precision.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MSHARED-1446) Add docs about repro build output timestamp boundaries
Michael Osipov created MSHARED-1446:
---
Summary: Add docs about repro build output timestamp boundaries
Key: MSHARED-1446
URL: https://issues.apache.org/jira/browse/MSHARED-1446
Project: Maven Shared Components
Issue Type: Task
Components: maven-archiver
Affects Versions: maven-archiver-3.6.2
Reporter: Michael Osipov
In MSHARED-1067 the boundaries have been introduced, but never documented by
they actually exist. Reason: MS-DOS time limitation for 2+2 bytes starting from
1980. See ZIP note:
{quote}
4.4.6 date and time fields: (2 bytes each)
The date and time are encoded in standard MS-DOS format.
If input came from standard input, the date and time are
those at which compression was started for this data.
If encrypting the central directory and general purpose bit
flag 13 is set indicating masking, the value stored in the
Local Header will be zero. MS-DOS time format is different
from more commonly used computer time formats such as
UTC. For example, MS-DOS uses year values relative to 1980
and 2 second precision.
{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8314) Get rid of xxxDebug scripts, make it work with --debug switch instead
[ https://issues.apache.org/jira/browse/MNG-8314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8314: - Fix Version/s: (was: 4.0.0-beta-5) > Get rid of xxxDebug scripts, make it work with --debug switch instead > - > > Key: MNG-8314 > URL: https://issues.apache.org/jira/browse/MNG-8314 > Project: Maven > Issue Type: Improvement > Components: Command Line >Reporter: Tamas Cservenak >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8310) Use --debug option instead of a specific mvnDebug script
[ https://issues.apache.org/jira/browse/MNG-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned MNG-8310: Assignee: Tamas Cservenak > Use --debug option instead of a specific mvnDebug script > > > Key: MNG-8310 > URL: https://issues.apache.org/jira/browse/MNG-8310 > Project: Maven > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8314) Get rid of xxxDebug scripts, make it work with --debug switch instead
[ https://issues.apache.org/jira/browse/MNG-8314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889737#comment-17889737 ] Guillaume Nodet commented on MNG-8314: -- Yeah, same. > Get rid of xxxDebug scripts, make it work with --debug switch instead > - > > Key: MNG-8314 > URL: https://issues.apache.org/jira/browse/MNG-8314 > Project: Maven > Issue Type: Improvement > Components: Command Line >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-beta-5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8314) Get rid of xxxDebug scripts, make it work with --debug switch instead
[ https://issues.apache.org/jira/browse/MNG-8314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8314. Resolution: Duplicate > Get rid of xxxDebug scripts, make it work with --debug switch instead > - > > Key: MNG-8314 > URL: https://issues.apache.org/jira/browse/MNG-8314 > Project: Maven > Issue Type: Improvement > Components: Command Line >Reporter: Tamas Cservenak >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8310) Use --debug option instead of a specific mvnDebug script
[ https://issues.apache.org/jira/browse/MNG-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8310: - Fix Version/s: 4.0.0-beta-5 (was: 4.0.0) > Use --debug option instead of a specific mvnDebug script > > > Key: MNG-8310 > URL: https://issues.apache.org/jira/browse/MNG-8310 > Project: Maven > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-beta-5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Cleanup after last commit [maven]
cstamas merged PR #1798: URL: https://github.com/apache/maven/pull/1798 -- 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] Improve logging with latest Maven changes [maven-mvnd]
gnodet merged PR #1164: URL: https://github.com/apache/maven-mvnd/pull/1164 -- 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] (DOXIA-750) MarkdownSink: Definition Lists don't properly escape inline styles
Konrad Windszus created DOXIA-750:
-
Summary: MarkdownSink: Definition Lists don't properly escape
inline styles
Key: DOXIA-750
URL: https://issues.apache.org/jira/browse/DOXIA-750
Project: Maven Doxia
Issue Type: Bug
Components: Module - Markdown
Reporter: Konrad Windszus
Assignee: Konrad Windszus
If a {{Sink.definition()}} contains e.g. {{Sink.text(...)}} with some inline
styles, those are emitted with markdown.
But since everything within a definition list is basically an HTML block
(https://spec.commonmark.org/0.31.2/#html-blocks) there every inline style must
be emitted as HTML as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DOXIA-750) MarkdownSink: Definition Lists don't properly escape inline styles
[
https://issues.apache.org/jira/browse/DOXIA-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated DOXIA-750:
--
Description:
If a {{Sink.definition()}} contains e.g. {{Sink.text(...)}} with some inline
styles, the latter are incorrectly emitted with markdown.
But since everything within a definition list is basically an HTML block
(https://spec.commonmark.org/0.31.2/#html-blocks) there every inline style must
be emitted as HTML as well.
was:
If a {{Sink.definition()}} contains e.g. {{Sink.text(...)}} with some inline
styles, those are emitted with markdown.
But since everything within a definition list is basically an HTML block
(https://spec.commonmark.org/0.31.2/#html-blocks) there every inline style must
be emitted as HTML as well.
> MarkdownSink: Definition Lists don't properly escape inline styles
> --
>
> Key: DOXIA-750
> URL: https://issues.apache.org/jira/browse/DOXIA-750
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Markdown
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> If a {{Sink.definition()}} contains e.g. {{Sink.text(...)}} with some inline
> styles, the latter are incorrectly emitted with markdown.
> But since everything within a definition list is basically an HTML block
> (https://spec.commonmark.org/0.31.2/#html-blocks) there every inline style
> must be emitted as HTML as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [DOXIA-746] Sink API: add method for block comment [maven-doxia]
kwin commented on code in PR #236:
URL: https://github.com/apache/maven-doxia/pull/236#discussion_r1801467513
##
doxia-sink-api/src/main/java/org/apache/maven/doxia/sink/Sink.java:
##
@@ -1724,6 +1724,17 @@ public interface Sink extends AutoCloseable {
*/
void comment(String comment);
+/**
+ * Add a comment. The default implementation will just call {@link
#comment(String)}.
+ *
+ * @param comment The comment to write.
+ * @param isBlockComment If true this is a block comment,
i.e. nothing should follow on the same line
+ * @since 2.1
+ */
+default void comment(String comment, boolean isBlockComment) {
+comment(comment);
+}
Review Comment:
Probably `endsWithLineBreak` is more accurate here.
--
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] Bump org.codehaus.plexus:plexus-sec-dispatcher from 2.0 to 4.0.1 [maven-resolver-ant-tasks]
dependabot[bot] closed pull request #49: Bump org.codehaus.plexus:plexus-sec-dispatcher from 2.0 to 4.0.1 URL: https://github.com/apache/maven-resolver-ant-tasks/pull/49 -- 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] Bump org.codehaus.plexus:plexus-sec-dispatcher from 2.0 to 4.0.1 [maven-resolver-ant-tasks]
slachiewicz commented on PR #49: URL: https://github.com/apache/maven-resolver-ant-tasks/pull/49#issuecomment-2413688318 @dependabot ignore this dependency -- 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] (MDEP-959) Possibly Flaky test testUnpackOverWriteIfNewer
[ https://issues.apache.org/jira/browse/MDEP-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889643#comment-17889643 ] Elliotte Rusty Harold commented on MDEP-959: Yep, definitely flaky. Passed the next time when I reran the failed tests in the Github actions UI. > Possibly Flaky test testUnpackOverWriteIfNewer > -- > > Key: MDEP-959 > URL: https://issues.apache.org/jira/browse/MDEP-959 > Project: Maven Dependency Plugin > Issue Type: Test >Reporter: Elliotte Rusty Harold >Priority: Minor > > Error:TestUnpackMojo.testUnpackOverWriteIfNewer:515 unpackedFile > '/Users/runner/work/maven-dependency-plugin/maven-dependency-plugin/target/unit-tests/unpack/outputDirectory/testGroupId-snapshot-2.0-SNAPSHOT-null-jar.txt' > lastModified() == 1728921104000: should be different. Actual: 1728921104000 > Failed here: > https://github.com/apache/maven-dependency-plugin/actions/runs/11330326987/job/31508264337?pr=433 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.codehaus.plexus:plexus-sec-dispatcher from 2.0 to 4.0.1 [maven-resolver-ant-tasks]
dependabot[bot] commented on PR #49: URL: https://github.com/apache/maven-resolver-ant-tasks/pull/49#issuecomment-2413688489 OK, I won't notify you about org.codehaus.plexus:plexus-sec-dispatcher 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-8309) Improve log infrastructure (first step toward multi-threading log view support)
[ https://issues.apache.org/jira/browse/MNG-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8309. Resolution: Fixed > Improve log infrastructure (first step toward multi-threading log view > support) > --- > > Key: MNG-8309 > URL: https://issues.apache.org/jira/browse/MNG-8309 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1792 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8309] Improve log infrastructure (first step toward multi-threading log view support) [maven]
gnodet merged PR #1792: URL: https://github.com/apache/maven/pull/1792 -- 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] (MNG-8311) empty but existing in settings.xml defaulting to current working directory
[
https://issues.apache.org/jira/browse/MNG-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889789#comment-17889789
]
Daniel Schmid commented on MNG-8311:
It seems like builds from the current master branch are using the home
directory instead of the project directory with empty
elements.
> empty but existing in settings.xml defaulting to current
> working directory
> -
>
> Key: MNG-8311
> URL: https://issues.apache.org/jira/browse/MNG-8311
> Project: Maven
> Issue Type: Bug
> Components: Core, Settings
>Affects Versions: 4.0.0-beta-4
> Environment: Apache Maven 4.0.0-beta-4
> (697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
> Maven home:
> /home/runner/work/maven-repro/maven-repro/apache-maven-4.0.0-beta-4
> Java version: 21.0.4, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "6.5.0-1025-azure", arch: "amd64", family: "unix"
>Reporter: Daniel Schmid
>Priority: Major
> Attachments: job_logs_mvn3.txt, job_logs_mvn4.txt,
> settings.template.xml
>
>
> If a ~/.m2/settings.xml with an empty element exists in
> Maven 4, it downloads dependencies to the current working directory as
> opposed to ~/.m2/repository.
> Steps to reproduce:
> * Create a settings.xml with the exact content from the [settings.xml in the
> quick overview|https://maven.apache.org/settings.html#quick-overview]. The
> important part is the empty .
> * Run mvn verify or similar
> * Observe it downloading dependencies to the current repository as opposed
> to ~/.m2/repository
> Full reproducer using GitHub Actions:
> [https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
> build log with Maven 4 (actual result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
> The output of mvn verify -X includes:
> {code:java}
> [DEBUG] Using local repository at /home/runner/work/maven-repro/maven-repro
> {code}
> Files after mvn verify with Maven 4 (the maven.tar.gz and
> apache-maven-4.0.0-beta-4 directories aren't created from mvn verify):
> {code:none}
> Run ls
> aopalliance
> apache-maven-4.0.0-beta-4
> com
> commons-codec
> commons-io
> javax
> maven.tar.gz
> net
> org
> pom.xml
> settings.template.xml
> src
> target
> {code}
> build log with Maven 3 (expected result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
> The output of mvn verify -X includes:
> {code:java}
> [DEBUG] Using local repository at /home/runner/.m2/repository {code}
> Files after mvn verify with Maven 3:
> {code:none}
> Run ls
> pom.xml
> settings.template.xml
> src
> target
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSHARED-1443) Upgrade plugins and components (in ITs)
[ https://issues.apache.org/jira/browse/MSHARED-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1443. --- Resolution: Fixed Fixed with [e48b8864e7fe7e22f5eff971c2d9e67ff794f775|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=e48b8864e7fe7e22f5eff971c2d9e67ff794f775]. > Upgrade plugins and components (in ITs) > --- > > Key: MSHARED-1443 > URL: https://issues.apache.org/jira/browse/MSHARED-1443 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0 > > > * Upgrade to Maven Site Plugin 3.20.0 > * Upgrade to Maven Project Info Reports Plugin 3.7.0 > * Upgrade to Maven Javadoc Plugin 3.10.1 > * Upgrade to Maven Checkstyle Plugin 3.5.0 > * Upgrade to Maven Plugin Tools 3.15.0 > * Upgrade to Maven Reporting Impl 4.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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: - Fix Version/s: 4.0.0-beta-6 (was: 4.0.0-beta-5) > [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: Major > Fix For: 4.0.0-beta-6 > > Attachments: screenshot-1.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] Fix exports and move help in place [maven-mvnd]
cstamas commented on PR #1166: URL: https://github.com/apache/maven-mvnd/pull/1166#issuecomment-2414713598 related mvn PR merged, master deployed, restarted build -- 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 ] Tamas Cservenak updated MNG-8300: - Attachment: screenshot-3.png > [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: Major > Fix For: 4.0.0-beta-6 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.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] [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 ] Tamas Cservenak updated MNG-8300: - Attachment: screenshot-2.png > [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: Major > Fix For: 4.0.0-beta-6 > > Attachments: screenshot-1.png, screenshot-2.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=17889799#comment-17889799 ] Tamas Cservenak commented on MNG-8300: -- Works for me with current master of mvn as well: !screenshot-3.png! > [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: Major > Fix For: 4.0.0-beta-6 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.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-8167) enable "split repo" in settings.xml
[
https://issues.apache.org/jira/browse/MNG-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889562#comment-17889562
]
Benjamin Marwell commented on MNG-8167:
---
Much better!
Current state (maven 3) is to add this profile to your
{{{}$HOME/.m2/settings.xml{}}}:
{code:java}
split-repo
true
true
true
{code}
And then activate it by default, just to make sure you don't get both split and
unsplit dependencies:
{code:java}
split-repo
{code}
> enable "split repo" in settings.xml
> ---
>
> Key: MNG-8167
> URL: https://issues.apache.org/jira/browse/MNG-8167
> Project: Maven
> Issue Type: Improvement
>Reporter: Benjamin Marwell
>Priority: Major
>
> With the availability of "-Daether.enhancedLocalRepository.split" and others,
> this should be settable in settings.xml.
> Rationale: the repo should not have two layouts (or more) locally.
> Settings.xml should at least be able to define a default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MNG-8309) Improve log infrastructure (first step toward multi-threading log view support)
[ https://issues.apache.org/jira/browse/MNG-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned MNG-8309: Assignee: Guillaume Nodet > Improve log infrastructure (first step toward multi-threading log view > support) > --- > > Key: MNG-8309 > URL: https://issues.apache.org/jira/browse/MNG-8309 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1792 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8309) Improve log infrastructure (first step toward multi-threading log view support)
[ https://issues.apache.org/jira/browse/MNG-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8309: - Fix Version/s: 4.0.0-beta-5 > Improve log infrastructure (first step toward multi-threading log view > support) > --- > > Key: MNG-8309 > URL: https://issues.apache.org/jira/browse/MNG-8309 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1792 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-599) Sigstore generator
[ https://issues.apache.org/jira/browse/MRESOLVER-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-599: -- Issue Type: New Feature (was: Improvement) > Sigstore generator > -- > > Key: MRESOLVER-599 > URL: https://issues.apache.org/jira/browse/MRESOLVER-599 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > > Just like > [GPG|https://github.com/apache/maven-resolver/tree/master/maven-resolver-generator-gnupg] > generator, we need sigstore generator. That would remove the limitations > (but would need either to Maven include this generator by default, or users > use this new generator as extension). -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Maven Daemon CLIng [maven-mvnd]
gnodet merged PR #1158: URL: https://github.com/apache/maven-mvnd/pull/1158 -- 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] (SUREFIRE-2278) Don't say Please
Elliotte Rusty Harold created SUREFIRE-2278: --- Summary: Don't say Please Key: SUREFIRE-2278 URL: https://issues.apache.org/jira/browse/SUREFIRE-2278 Project: Maven Surefire Issue Type: Improvement Reporter: Elliotte Rusty Harold Error: Please refer to /Users/runner/work/maven-dependency-plugin/maven-dependency-plugin/target/surefire-reports for the individual test results. Error: Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. Please refer to --:> See -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SUREFIRE-2279) Do dump files exist or not
Elliotte Rusty Harold created SUREFIRE-2279: --- Summary: Do dump files exist or not Key: SUREFIRE-2279 URL: https://issues.apache.org/jira/browse/SUREFIRE-2279 Project: Maven Surefire Issue Type: Improvement Reporter: Elliotte Rusty Harold Error: Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. If they exist print a more detailed message giving their paths. If they don't, don't print this message at all. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SUREFIRE-2280) Test failure is goal success
Elliotte Rusty Harold created SUREFIRE-2280: --- Summary: Test failure is goal success Key: SUREFIRE-2280 URL: https://issues.apache.org/jira/browse/SUREFIRE-2280 Project: Maven Surefire Issue Type: Improvement Reporter: Elliotte Rusty Harold Error: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.3.0:test (default-test) on project maven-dependency-plugin: There are test failures. I don't think this is truly correct. The goals succeeded. It ran the tests. It;s just that a test failed. Maybe Error: project maven-dependency-plugin has test failures. and ideally add the names of the failing tests here. Don't make me scroll back to find them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEP-959) Possibly Flaky test testUnpackOverWriteIfNewer
Elliotte Rusty Harold created MDEP-959: -- Summary: Possibly Flaky test testUnpackOverWriteIfNewer Key: MDEP-959 URL: https://issues.apache.org/jira/browse/MDEP-959 Project: Maven Dependency Plugin Issue Type: Test Reporter: Elliotte Rusty Harold Error:TestUnpackMojo.testUnpackOverWriteIfNewer:515 unpackedFile '/Users/runner/work/maven-dependency-plugin/maven-dependency-plugin/target/unit-tests/unpack/outputDirectory/testGroupId-snapshot-2.0-SNAPSHOT-null-jar.txt' lastModified() == 1728921104000: should be different. Actual: 1728921104000 Failed here: https://github.com/apache/maven-dependency-plugin/actions/runs/11330326987/job/31508264337?pr=433 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8295] Add IT for Dependency Manager Transitivity [maven-integration-testing]
gnodet merged PR #384: URL: https://github.com/apache/maven-integration-testing/pull/384 -- 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-8295] Dependency Manager Transitivity (now default) handles dependency management inconsistently [maven]
gnodet merged PR #1788: URL: https://github.com/apache/maven/pull/1788 -- 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] (MARTIFACT-51) Replace org.codehaus.plexus.util.FileUtils with commons-io in NotReproduciblePluginsDocumentationTest
[ https://issues.apache.org/jira/browse/MARTIFACT-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MARTIFACT-51. -- > Replace org.codehaus.plexus.util.FileUtils with commons-io in > NotReproduciblePluginsDocumentationTest > - > > Key: MARTIFACT-51 > URL: https://issues.apache.org/jira/browse/MARTIFACT-51 > Project: Maven Artifact Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8295) Dependency Manager Transitivity (now default) handles dependency management inconsistently
[
https://issues.apache.org/jira/browse/MNG-8295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8295.
Fix Version/s: 4.0.0-beta-5
Assignee: Guillaume Nodet
Resolution: Fixed
> Dependency Manager Transitivity (now default) handles dependency management
> inconsistently
> --
>
> Key: MNG-8295
> URL: https://issues.apache.org/jira/browse/MNG-8295
> Project: Maven
> Issue Type: Bug
> Components: API, Core
>Affects Versions: 4.0.0-beta-4
>Reporter: Didier Loiseau
>Assignee: Guillaume Nodet
>Priority: Critical
> Fix For: 4.0.0-beta-5
>
> Attachments: dependency-transitivity-inconsistency.zip
>
>
> Since MNG-7982, {{maven.resolver.dependencyManagerTransitivity}}
> ({{{}true{}}} by default) configures the {{ClassicDependencyManager}} with
> the corresponding {{transitivity}} flag.
> It appears, however, that this behavior is inconsistent, because it ignores
> the dependency management of direct dependencies and only considers it for
> the transitive dependencies.
> I already described this in MNG-5761, but since the latter is originally a
> different issue (that should have been fixed by MNG-7982), I thought it would
> make more sense to track this inconsistency as a separate bug.
> The attached [^dependency-transitivity-inconsistency.zip] (copied from
> MNG-5761) can be used to show the issue.
> I’m running with
> {code:java}
> $ mvn -v
> Apache Maven 4.0.0-beta-4 (697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
> Maven home: /home/didier/.sdkman/candidates/maven/4.0.0-beta-4
> Java version: 21.0.2, vendor: Oracle Corporation, runtime:
> /home/didier/.sdkman/candidates/java/21.0.2-open
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "6.8.0-45-generic", arch: "amd64", family: "unix"
> {code}
> First you can see that {{dependent-pom}} manages the version of
> {{commons-collections}} to *3.2.2* ({{{}commons-beanutils:1.9.2{}}} depends
> on 3.2.1):
> {code:java}
> $ mvn dependency:tree -f dependent-pom.xml
> …
> [INFO] MNG-5761:dependent:pom:1.0-SNAPSHOT
> [INFO] \- commons-beanutils:commons-beanutils:jar:1.9.2:compile
> [INFO]+- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO]\- commons-collections:commons-collections:jar:3.2.2:compile
> {code}
> Now install {{parent-pom}} and {{{}dependent-pom{}}}, and check the
> dependencies of {{{}depending-pom{}}}:
> {code:java}
> $ mvn install -f parent-pom.xml
> $ mvn install -f dependent-pom.xml
> $ mvn dependency:tree -f depending-pom.xml
> …
> [INFO] MNG-5761:depending:pom:1.0-SNAPSHOT
> [INFO] \- MNG-5761:dependent:pom:1.0-SNAPSHOT:compile
> [INFO]\- commons-beanutils:commons-beanutils:jar:1.9.2:compile
> [INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO] \- commons-collections:commons-collections:jar:3.2.1:compile
> {code}
> you can see that the {{}} of {{dependent}} is ignored
> (like with Maven 3), and we get {{commons-collections}} *3.2.1* instead.
> However, if we install {{dependent-pom}} and check the dependencies of
> {{{}dependent-pom2{}}}, we get:
> {code:java}
> $ mvn install -f depending-pom.xml
> $ mvn dependency:tree -f depending-pom2.xml
> …
> [INFO] MNG-5761:depending2:pom:1.0-SNAPSHOT
> [INFO] \- MNG-5761:depending:pom:1.0-SNAPSHOT:compile
> [INFO]\- MNG-5761:dependent:pom:1.0-SNAPSHOT:compile
> [INFO] \- commons-beanutils:commons-beanutils:jar:1.9.2:compile
> [INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO] \- commons-collections:commons-collections:jar:3.2.2:compile
> {code}
> So now we get {{commons-collections}} *3.2.2* again!
> {{}} is taken into account at depth 2+ (and 0) but not
> at depth 1.
> This is due to [these 3
> lines|https://github.com/apache/maven-resolver/blob/32844e4eb8d444838953f1d49be2ecb71db15b78/maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/manager/ClassicDependencyManager.java#L91-L93]
> in {{{}ClassicDependencyManager{}}}:
> {code:java}
> @Override
> public DependencyManager deriveChildManager(DependencyCollectionContext
> context) {
> // MNG-4720: Maven2 backward compatibility
> // Removing this IF makes one IT fail here (read comment above):
> //
> https://github.com/apache/maven-integration-testing/blob/b4e8fd52b99a058336f9c7c5ec44fdbc1427759c/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng4720DependencyManagementExclusionMergeTest.java#L67
> if (depth == 1) {
> return newInstance(managedVersions, managedScopes,
> managedOptionals, managedLocalPaths, managedExclusions);
> }
> return super.deriveChildManager(context);
> }
> {code}
> I have also created [a PR with integr
[jira] [Resolved] (MARTIFACT-51) Replace org.codehaus.plexus.util.FileUtils with commons-io in NotReproduciblePluginsDocumentationTest
[ https://issues.apache.org/jira/browse/MARTIFACT-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MARTIFACT-51. Resolution: Fixed > Replace org.codehaus.plexus.util.FileUtils with commons-io in > NotReproduciblePluginsDocumentationTest > - > > Key: MARTIFACT-51 > URL: https://issues.apache.org/jira/browse/MARTIFACT-51 > Project: Maven Artifact Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8312) Generate BOMs instead of hand-writing them
[ https://issues.apache.org/jira/browse/MNG-8312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8312: - Fix Version/s: 4.0.0-beta-5 > Generate BOMs instead of hand-writing them > -- > > Key: MNG-8312 > URL: https://issues.apache.org/jira/browse/MNG-8312 > Project: Maven > Issue Type: Improvement >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8310) Use --debug option instead of a specific mvnDebug script
Guillaume Nodet created MNG-8310: Summary: Use --debug option instead of a specific mvnDebug script Key: MNG-8310 URL: https://issues.apache.org/jira/browse/MNG-8310 Project: Maven Issue Type: Improvement Reporter: Guillaume Nodet Fix For: 4.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8248) WARNING: A restricted method in java.lang.System has been called
[
https://issues.apache.org/jira/browse/MNG-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889570#comment-17889570
]
Guillaume Nodet commented on MNG-8248:
--
This has been fixed in {{master}} branch with MNG-8260
> WARNING: A restricted method in java.lang.System has been called
>
>
> Key: MNG-8248
> URL: https://issues.apache.org/jira/browse/MNG-8248
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.1, 3.8.2, 3.8.3, 3.8.4, 3.8.5, 3.8.6, 3.8.7, 3.8.8,
> 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 3.9.8, 3.9.9,
> 4.0.0-beta-3, 4.0.0-beta-4
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.0-beta-5
>
>
> Building a project with JDK 24.ea.13 produces the following WARNING:
> {code}
> $> mvn clean verify
> WARNING: A restricted method in java.lang.System has been called
> WARNING: java.lang.System::load has been called by
> org.jline.nativ.JLineNativeLoader in an unnamed module
> (file:/Users/khm/tools/maven/lib/jline-3.26.3.jar)
> WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for
> callers in this module
> WARNING: Restricted methods will be blocked in a future release unless native
> access is enabled
> {code}
> also a simple:
> {code}
> mvn --version
> {code}
> wil trigger:
> {code}
> $> mvn --version
> WARNING: A restricted method in java.lang.System has been called
> WARNING: java.lang.System::load has been called by
> org.fusesource.jansi.internal.JansiLoader in an unnamed module
> (file:/Users/khm/tools/maven/lib/jansi-2.4.1.jar)
> WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for
> callers in this module
> WARNING: Restricted methods will be blocked in a future release unless native
> access is enabled
> Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256)
> Maven home: /Users/khm/tools/maven
> Java version: 24-ea, vendor: Oracle Corporation, runtime:
> /Users/khm/.sdkman/candidates/java/24.ea.13-open
> Default locale: en_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "aarch64", family: "mac"
> {code}
> Also opened an issue on JLine3 Project:
> https://github.com/jline/jline3/issues/1067
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-8248) WARNING: A restricted method in java.lang.System has been called
[
https://issues.apache.org/jira/browse/MNG-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8248.
Fix Version/s: (was: 4.0.0-beta-5)
Resolution: Duplicate
> WARNING: A restricted method in java.lang.System has been called
>
>
> Key: MNG-8248
> URL: https://issues.apache.org/jira/browse/MNG-8248
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.1, 3.8.2, 3.8.3, 3.8.4, 3.8.5, 3.8.6, 3.8.7, 3.8.8,
> 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 3.9.8, 3.9.9,
> 4.0.0-beta-3, 4.0.0-beta-4
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> Building a project with JDK 24.ea.13 produces the following WARNING:
> {code}
> $> mvn clean verify
> WARNING: A restricted method in java.lang.System has been called
> WARNING: java.lang.System::load has been called by
> org.jline.nativ.JLineNativeLoader in an unnamed module
> (file:/Users/khm/tools/maven/lib/jline-3.26.3.jar)
> WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for
> callers in this module
> WARNING: Restricted methods will be blocked in a future release unless native
> access is enabled
> {code}
> also a simple:
> {code}
> mvn --version
> {code}
> wil trigger:
> {code}
> $> mvn --version
> WARNING: A restricted method in java.lang.System has been called
> WARNING: java.lang.System::load has been called by
> org.fusesource.jansi.internal.JansiLoader in an unnamed module
> (file:/Users/khm/tools/maven/lib/jansi-2.4.1.jar)
> WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for
> callers in this module
> WARNING: Restricted methods will be blocked in a future release unless native
> access is enabled
> Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256)
> Maven home: /Users/khm/tools/maven
> Java version: 24-ea, vendor: Oracle Corporation, runtime:
> /Users/khm/.sdkman/candidates/java/24.ea.13-open
> Default locale: en_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "aarch64", family: "mac"
> {code}
> Also opened an issue on JLine3 Project:
> https://github.com/jline/jline3/issues/1067
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-8058) Allow variables defined in .mvn/maven.config used as constants
[
https://issues.apache.org/jira/browse/MNG-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8058.
Resolution: Fixed
Please reopen if needed
> Allow variables defined in .mvn/maven.config used as constants
> --
>
> Key: MNG-8058
> URL: https://issues.apache.org/jira/browse/MNG-8058
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 3.9.6, 4.0.0-alpha-12
>Reporter: Stefan Bischof
>Priority: Major
>
> I would like to have all variables defined in .mvn/maven.config to be allowed
> as constants.
> My setup uses different versions on each module but i want to define them
> central.
> in my `.mvn/maven.config` file I define the variables
>
> {code:java}
> -Drevision.org.aaa.bbb=0.0.1-SNAPSHOT
> -Drevision.org.aaa.bbb.ccc=0.0.2-SNAPSHOT
> -Drevision.org.aaa.bbb.ddd=0.0.3-SNAPSHOT {code}
>
> In my pom i want to use this variables to set version of perant ans artifact
> itsselfe
> {code:java}
>
> org.aaa
> org.aaa.bbb
> ${revision.org.aaa.bbb}
>
> org.aaa.bbb.ccc
> ${revision.org.aaa.bbb.ccc} {code}
> I am getting the warning
>
> {code:java}
> 'version' contains an expression but should be a constant. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8303) Bump ch.qos.logback:logback-classic from 1.5.8 to 1.5.10
[ https://issues.apache.org/jira/browse/MNG-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8303: - Description: GitHub Pull Request: https://github.com/apache/maven/pull/1789 GitHub Pull Request: https://github.com/apache/maven/pull/1794 was:GitHub Pull Request: https://github.com/apache/maven/pull/1789 > Bump ch.qos.logback:logback-classic from 1.5.8 to 1.5.10 > > > Key: MNG-8303 > URL: https://issues.apache.org/jira/browse/MNG-8303 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > > GitHub Pull Request: https://github.com/apache/maven/pull/1789 > GitHub Pull Request: https://github.com/apache/maven/pull/1794 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8303) Bump ch.qos.logback:logback-classic from 1.5.8 to 1.5.10
[ https://issues.apache.org/jira/browse/MNG-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8303: - Summary: Bump ch.qos.logback:logback-classic from 1.5.8 to 1.5.10 (was: Bump ch.qos.logback:logback-classic from 1.5.8 to 1.5.9) > Bump ch.qos.logback:logback-classic from 1.5.8 to 1.5.10 > > > Key: MNG-8303 > URL: https://issues.apache.org/jira/browse/MNG-8303 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > > GitHub Pull Request: https://github.com/apache/maven/pull/1789 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8310) Use --debug option instead of a specific mvnDebug script
[
https://issues.apache.org/jira/browse/MNG-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889574#comment-17889574
]
Michael Osipov commented on MNG-8310:
-
We discussed this last year to make this happen in the future and deprecate
{{mvnDebug}} when I have deprecated {{--debug}} inf favor of {{--verbose}}. I
am reall in favor of this. But first we need to make sure that none of our
Invoker stuff uses {{--debug}} for verbose. [~sjaranowski].
> Use --debug option instead of a specific mvnDebug script
>
>
> Key: MNG-8310
> URL: https://issues.apache.org/jira/browse/MNG-8310
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8303) Bump ch.qos.logback:logback-classic from 1.5.8 to 1.5.10
[ https://issues.apache.org/jira/browse/MNG-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8303: - Fix Version/s: 4.0.0-beta-5 > Bump ch.qos.logback:logback-classic from 1.5.8 to 1.5.10 > > > Key: MNG-8303 > URL: https://issues.apache.org/jira/browse/MNG-8303 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1789 > GitHub Pull Request: https://github.com/apache/maven/pull/1794 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MNG-8310) Use --debug option instead of a specific mvnDebug script
[
https://issues.apache.org/jira/browse/MNG-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889574#comment-17889574
]
Michael Osipov edited comment on MNG-8310 at 10/15/24 1:42 PM:
---
We discussed this last year to make this happen in the future and deprecate
{{mvnDebug}} when I have deprecated {{\-\-debug}} inf favor of {{\-\-verbose}}.
I am reall in favor of this. But first we need to make sure that none of our
Invoker stuff uses {{--debug}} for verbose. [~sjaranowski].
was (Author: michael-o):
We discussed this last year to make this happen in the future and deprecate
{{mvnDebug}} when I have deprecated {{--debug}} inf favor of {{--verbose}}. I
am reall in favor of this. But first we need to make sure that none of our
Invoker stuff uses {{--debug}} for verbose. [~sjaranowski].
> Use --debug option instead of a specific mvnDebug script
>
>
> Key: MNG-8310
> URL: https://issues.apache.org/jira/browse/MNG-8310
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (SUREFIRE-2278) Don't say Please
[ https://issues.apache.org/jira/browse/SUREFIRE-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889670#comment-17889670 ] Michael Osipov edited comment on SUREFIRE-2278 at 10/15/24 1:43 PM: Good point. Can you raise a PR? was (Author: michael-o): Good point. > Don't say Please > > > Key: SUREFIRE-2278 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2278 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Error: Please refer to > /Users/runner/work/maven-dependency-plugin/maven-dependency-plugin/target/surefire-reports > for the individual test results. > Error: Please refer to dump files (if any exist) [date].dump, > [date]-jvmRun[N].dump and [date].dumpstream. > Please refer to --:> See -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SUREFIRE-2279) Do dump files exist or not
[ https://issues.apache.org/jira/browse/SUREFIRE-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889671#comment-17889671 ] Michael Osipov commented on SUREFIRE-2279: -- Big question: Can we determine reliably that those files exist? > Do dump files exist or not > -- > > Key: SUREFIRE-2279 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2279 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > Error: Please refer to dump files (if any exist) [date].dump, > [date]-jvmRun[N].dump and [date].dumpstream. > If they exist print a more detailed message giving their paths. If they > don't, don't print this message at all. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SUREFIRE-2278) Don't say Please
[ https://issues.apache.org/jira/browse/SUREFIRE-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889670#comment-17889670 ] Michael Osipov commented on SUREFIRE-2278: -- Good point. > Don't say Please > > > Key: SUREFIRE-2278 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2278 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Error: Please refer to > /Users/runner/work/maven-dependency-plugin/maven-dependency-plugin/target/surefire-reports > for the individual test results. > Error: Please refer to dump files (if any exist) [date].dump, > [date]-jvmRun[N].dump and [date].dumpstream. > Please refer to --:> See -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8312) Generate BOMs instead of hand-writing them
[ https://issues.apache.org/jira/browse/MNG-8312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned MNG-8312: Assignee: Guillaume Nodet > Generate BOMs instead of hand-writing them > -- > > Key: MNG-8312 > URL: https://issues.apache.org/jira/browse/MNG-8312 > Project: Maven > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump native-maven-plugin from 0.10.2 to 0.10.3 [maven-mvnd]
cstamas commented on PR #1143: URL: https://github.com/apache/maven-mvnd/pull/1143#issuecomment-2413994827 Thanks! -- 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-8313) Resolver 2.0.2
Tamas Cservenak created MNG-8313: Summary: Resolver 2.0.2 Key: MNG-8313 URL: https://issues.apache.org/jira/browse/MNG-8313 Project: Maven Issue Type: Dependency upgrade Components: Dependencies Reporter: Tamas Cservenak Fix For: 4.0.0-beta-5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8314) Get rid of xxxDebug scripts, make it work with --debug switch instead
Tamas Cservenak created MNG-8314: Summary: Get rid of xxxDebug scripts, make it work with --debug switch instead Key: MNG-8314 URL: https://issues.apache.org/jira/browse/MNG-8314 Project: Maven Issue Type: Improvement Components: Command Line Reporter: Tamas Cservenak Fix For: 4.0.0-beta-5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8313) Resolver 2.0.2
[ https://issues.apache.org/jira/browse/MNG-8313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8313: Assignee: Tamas Cservenak > Resolver 2.0.2 > -- > > Key: MNG-8313 > URL: https://issues.apache.org/jira/browse/MNG-8313 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-beta-5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Drop `commons-io` from explicit test dependencies [maven-dependency-plugin]
MLabusquiere opened a new pull request, #442: URL: https://github.com/apache/maven-dependency-plugin/pull/442 Hello guys, First thanks for your work 👍 Currently, I get the following error when using the plugin (3.8.0): ``` [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.8.0:unpack-dependencies (unpack) on project opportunity-service: Execution unpack of goal org.apache.maven.plugins:maven-dependency-plugin:3.8.0:unpack-dependencies failed: A required class was missing while executing org.apache.maven.plugins:maven-dependency-plugin:3.8.0:unpack-dependencies: org/apache/commons/io/build/AbstractStreamBuilder ``` I believe this is because `commons-io` is a transitive deps of `org.codehaus.plexus:plexus-archiver`. Here is a diff of mvn dependency:tree result between master and this PR: ``` [INFO] | +- org.apache.maven.doxia:doxia-module-xdoc:jar:2.0.0-M12:runtime [INFO] | \- org.apache.maven:maven-archiver:jar:3.6.2:compile -[INFO] +- commons-io:commons-io:jar:2.16.1:test [INFO] +- org.codehaus.plexus:plexus-archiver:jar:4.10.0:compile +[INFO] | +- commons-io:commons-io:jar:2.16.1:compile [INFO] | +- org.apache.commons:commons-compress:jar:1.26.2:compile [INFO] | | \- commons-codec:commons-codec:jar:1.17.0:compile [INFO] | +- io.airlift:aircompressor:jar:0.27:compile ``` I know for sure that the bugs didn't exist in 3.2.0. I now need to resume to my job activites. I will post an update when tested (~tomorrow), and LMK if I need to open a Jira. -- 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-8311) empty but existing in settings.xml defaulting to current working directory
[
https://issues.apache.org/jira/browse/MNG-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Schmid updated MNG-8311:
---
Description:
If a ~/.m2/settings.xml with an empty element exists in
Maven 4, it downloads dependencies to the current working directory as opposed
to ~/.m2/repository.
Steps to reproduce:
* Create a settings.xml with the exact content from the [settings.xml in the
quick overview|https://maven.apache.org/settings.html#quick-overview]. The
important part is the empty .
* Run mvn verify or similar
* Observe it downloading dependencies to the current repository as opposed to
~/.m2/repository
Full reproducer using GitHub Actions:
[https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
build log with Maven 4 (actual result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
Files after mvn verify with Maven 4:
{code:none}
Run ls
aopalliance
apache-maven-4.0.0-beta-4
com
commons-codec
commons-io
javax
maven.tar.gz
net
org
pom.xml
settings.template.xml
src
target
{code}
build log with Maven 3 (expected result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
Files after mvn verify with Maven 3:
{code:none}
Run ls
pom.xml
settings.template.xml
src
target
{code}
was:
If a ~/.m2/settings.xml with an empty element exists in
Maven 4, it downloads dependencies to the current working directory.
Steps to reproduce:
* Create a settings.xml with the exact content from the [settings.xml in the
quick overview|https://maven.apache.org/settings.html#quick-overview]. The
important part is the empty .
* Run mvn verify or similar
* Observe it downloading dependencies to the current repository as opposed to
.m2/repository
Full reproducer using GitHub Actions:
[https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
build log with Maven 4 (actual result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
Files after mvn verify with Maven 4:
{code:none}
Run ls
aopalliance
apache-maven-4.0.0-beta-4
com
commons-codec
commons-io
javax
maven.tar.gz
net
org
pom.xml
settings.template.xml
src
target
{code}
build log with Maven 3 (expected result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
Files after mvn verify with Maven 3:
{code:none}
Run ls
pom.xml
settings.template.xml
src
target
{code}
> empty but existing in settings.xml defaulting to current
> working directory
> -
>
> Key: MNG-8311
> URL: https://issues.apache.org/jira/browse/MNG-8311
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-beta-4
> Environment: Apache Maven 4.0.0-beta-4
> (697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
> Maven home:
> /home/runner/work/maven-repro/maven-repro/apache-maven-4.0.0-beta-4
> Java version: 21.0.4, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "6.5.0-1025-azure", arch: "amd64", family: "unix"
>Reporter: Daniel Schmid
>Priority: Major
> Attachments: job_logs_mvn3.txt, job_logs_mvn4.txt,
> settings.template.xml
>
>
> If a ~/.m2/settings.xml with an empty element exists in
> Maven 4, it downloads dependencies to the current working directory as
> opposed to ~/.m2/repository.
> Steps to reproduce:
> * Create a settings.xml with the exact content from the [settings.xml in the
> quick overview|https://maven.apache.org/settings.html#quick-overview]. The
> important part is the empty .
> * Run mvn verify or similar
> * Observe it downloading dependencies to the current repository as opposed
> to ~/.m2/repository
> Full reproducer using GitHub Actions:
> [https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
> build log with Maven 4 (actual result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
> Files after mvn verify with Maven 4:
> {code:none}
> Run ls
> aopalliance
> apache-maven-4.0.0-beta-4
> com
> commons-codec
> commons-io
> javax
> maven.tar.gz
> net
> org
> pom.xml
> settings.template.xml
> src
> target
> {code}
> build log with Maven 3 (expected result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
> Files after mvn verify with Maven 3:
> {code:none}
> Run ls
> pom.xml
> settings.template.xml
> src
> target
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8311) empty but existing in settings.xml defaulting to current working directory
[
https://issues.apache.org/jira/browse/MNG-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Schmid updated MNG-8311:
---
Description:
If a ~/.m2/settings.xml with an empty element exists in
Maven 4, it downloads dependencies to the current working directory as opposed
to ~/.m2/repository.
Steps to reproduce:
* Create a settings.xml with the exact content from the [settings.xml in the
quick overview|https://maven.apache.org/settings.html#quick-overview]. The
important part is the empty .
* Run mvn verify or similar
* Observe it downloading dependencies to the current repository as opposed to
~/.m2/repository
Full reproducer using GitHub Actions:
[https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
build log with Maven 4 (actual result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
Files after mvn verify with Maven 4 (the maven.tar.gz and
apache-maven-4.0.0-beta-4 directories aren't created from mvn verify):
{code:none}
Run ls
aopalliance
apache-maven-4.0.0-beta-4
com
commons-codec
commons-io
javax
maven.tar.gz
net
org
pom.xml
settings.template.xml
src
target
{code}
build log with Maven 3 (expected result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
Files after mvn verify with Maven 3:
{code:none}
Run ls
pom.xml
settings.template.xml
src
target
{code}
was:
If a ~/.m2/settings.xml with an empty element exists in
Maven 4, it downloads dependencies to the current working directory as opposed
to ~/.m2/repository.
Steps to reproduce:
* Create a settings.xml with the exact content from the [settings.xml in the
quick overview|https://maven.apache.org/settings.html#quick-overview]. The
important part is the empty .
* Run mvn verify or similar
* Observe it downloading dependencies to the current repository as opposed to
~/.m2/repository
Full reproducer using GitHub Actions:
[https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
build log with Maven 4 (actual result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
Files after mvn verify with Maven 4:
{code:none}
Run ls
aopalliance
apache-maven-4.0.0-beta-4
com
commons-codec
commons-io
javax
maven.tar.gz
net
org
pom.xml
settings.template.xml
src
target
{code}
build log with Maven 3 (expected result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
Files after mvn verify with Maven 3:
{code:none}
Run ls
pom.xml
settings.template.xml
src
target
{code}
> empty but existing in settings.xml defaulting to current
> working directory
> -
>
> Key: MNG-8311
> URL: https://issues.apache.org/jira/browse/MNG-8311
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-beta-4
> Environment: Apache Maven 4.0.0-beta-4
> (697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
> Maven home:
> /home/runner/work/maven-repro/maven-repro/apache-maven-4.0.0-beta-4
> Java version: 21.0.4, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "6.5.0-1025-azure", arch: "amd64", family: "unix"
>Reporter: Daniel Schmid
>Priority: Major
> Attachments: job_logs_mvn3.txt, job_logs_mvn4.txt,
> settings.template.xml
>
>
> If a ~/.m2/settings.xml with an empty element exists in
> Maven 4, it downloads dependencies to the current working directory as
> opposed to ~/.m2/repository.
> Steps to reproduce:
> * Create a settings.xml with the exact content from the [settings.xml in the
> quick overview|https://maven.apache.org/settings.html#quick-overview]. The
> important part is the empty .
> * Run mvn verify or similar
> * Observe it downloading dependencies to the current repository as opposed
> to ~/.m2/repository
> Full reproducer using GitHub Actions:
> [https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
> build log with Maven 4 (actual result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
> Files after mvn verify with Maven 4 (the maven.tar.gz and
> apache-maven-4.0.0-beta-4 directories aren't created from mvn verify):
> {code:none}
> Run ls
> aopalliance
> apache-maven-4.0.0-beta-4
> com
> commons-codec
> commons-io
> javax
> maven.tar.gz
> net
> org
> pom.xml
> settings.template.xml
> src
> target
> {code}
> build log with Maven 3 (expected result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
> Files after mvn verify with Maven 3:
> {code:none}
> Run ls
> pom.xml
> settings.template.xml
> src
> target
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8311) empty but existing in settings.xml defaulting to current working directory
[
https://issues.apache.org/jira/browse/MNG-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Schmid updated MNG-8311:
---
Description:
If a ~/.m2/settings.xml with an empty element exists in
Maven 4, it downloads dependencies to the current working directory as opposed
to ~/.m2/repository.
Steps to reproduce:
* Create a settings.xml with the exact content from the [settings.xml in the
quick overview|https://maven.apache.org/settings.html#quick-overview]. The
important part is the empty .
* Run mvn verify or similar
* Observe it downloading dependencies to the current repository as opposed to
~/.m2/repository
Full reproducer using GitHub Actions:
[https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
build log with Maven 4 (actual result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
The output of mvn verify -X includes:
{code:java}
[DEBUG] Using local repository at /home/runner/work/maven-repro/maven-repro
{code}
Files after mvn verify with Maven 4 (the maven.tar.gz and
apache-maven-4.0.0-beta-4 directories aren't created from mvn verify):
{code:none}
Run ls
aopalliance
apache-maven-4.0.0-beta-4
com
commons-codec
commons-io
javax
maven.tar.gz
net
org
pom.xml
settings.template.xml
src
target
{code}
build log with Maven 3 (expected result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
The output of mvn verify -X includes:
{code:java}
[DEBUG] Using local repository at /home/runner/.m2/repository {code}
Files after mvn verify with Maven 3:
{code:none}
Run ls
pom.xml
settings.template.xml
src
target
{code}
was:
If a ~/.m2/settings.xml with an empty element exists in
Maven 4, it downloads dependencies to the current working directory as opposed
to ~/.m2/repository.
Steps to reproduce:
* Create a settings.xml with the exact content from the [settings.xml in the
quick overview|https://maven.apache.org/settings.html#quick-overview]. The
important part is the empty .
* Run mvn verify or similar
* Observe it downloading dependencies to the current repository as opposed to
~/.m2/repository
Full reproducer using GitHub Actions:
[https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
build log with Maven 4 (actual result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
Files after mvn verify with Maven 4 (the maven.tar.gz and
apache-maven-4.0.0-beta-4 directories aren't created from mvn verify):
{code:none}
Run ls
aopalliance
apache-maven-4.0.0-beta-4
com
commons-codec
commons-io
javax
maven.tar.gz
net
org
pom.xml
settings.template.xml
src
target
{code}
build log with Maven 3 (expected result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
Files after mvn verify with Maven 3:
{code:none}
Run ls
pom.xml
settings.template.xml
src
target
{code}
> empty but existing in settings.xml defaulting to current
> working directory
> -
>
> Key: MNG-8311
> URL: https://issues.apache.org/jira/browse/MNG-8311
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-beta-4
> Environment: Apache Maven 4.0.0-beta-4
> (697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
> Maven home:
> /home/runner/work/maven-repro/maven-repro/apache-maven-4.0.0-beta-4
> Java version: 21.0.4, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "6.5.0-1025-azure", arch: "amd64", family: "unix"
>Reporter: Daniel Schmid
>Priority: Major
> Attachments: job_logs_mvn3.txt, job_logs_mvn4.txt,
> settings.template.xml
>
>
> If a ~/.m2/settings.xml with an empty element exists in
> Maven 4, it downloads dependencies to the current working directory as
> opposed to ~/.m2/repository.
> Steps to reproduce:
> * Create a settings.xml with the exact content from the [settings.xml in the
> quick overview|https://maven.apache.org/settings.html#quick-overview]. The
> important part is the empty .
> * Run mvn verify or similar
> * Observe it downloading dependencies to the current repository as opposed
> to ~/.m2/repository
> Full reproducer using GitHub Actions:
> [https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
> build log with Maven 4 (actual result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
> The output of mvn verify -X includes:
> {code:java}
> [DEBUG] Using local repository at /home/runner/work/maven-repro/maven-repro
> {code}
> Files after mvn verify with Maven 4 (the maven.tar.gz and
> apache-maven-4.0.0-beta-4 directories aren't created from mvn verify):
> {code:none}
> Run ls
> aopalliance
> apache-maven
[jira] [Updated] (MNG-8311) empty but existing in settings.xml defaulting to current working directory
[
https://issues.apache.org/jira/browse/MNG-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Schmid updated MNG-8311:
---
Component/s: Settings
> empty but existing in settings.xml defaulting to current
> working directory
> -
>
> Key: MNG-8311
> URL: https://issues.apache.org/jira/browse/MNG-8311
> Project: Maven
> Issue Type: Bug
> Components: Core, Settings
>Affects Versions: 4.0.0-beta-4
> Environment: Apache Maven 4.0.0-beta-4
> (697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
> Maven home:
> /home/runner/work/maven-repro/maven-repro/apache-maven-4.0.0-beta-4
> Java version: 21.0.4, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "6.5.0-1025-azure", arch: "amd64", family: "unix"
>Reporter: Daniel Schmid
>Priority: Major
> Attachments: job_logs_mvn3.txt, job_logs_mvn4.txt,
> settings.template.xml
>
>
> If a ~/.m2/settings.xml with an empty element exists in
> Maven 4, it downloads dependencies to the current working directory as
> opposed to ~/.m2/repository.
> Steps to reproduce:
> * Create a settings.xml with the exact content from the [settings.xml in the
> quick overview|https://maven.apache.org/settings.html#quick-overview]. The
> important part is the empty .
> * Run mvn verify or similar
> * Observe it downloading dependencies to the current repository as opposed
> to ~/.m2/repository
> Full reproducer using GitHub Actions:
> [https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
> build log with Maven 4 (actual result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
> The output of mvn verify -X includes:
> {code:java}
> [DEBUG] Using local repository at /home/runner/work/maven-repro/maven-repro
> {code}
> Files after mvn verify with Maven 4 (the maven.tar.gz and
> apache-maven-4.0.0-beta-4 directories aren't created from mvn verify):
> {code:none}
> Run ls
> aopalliance
> apache-maven-4.0.0-beta-4
> com
> commons-codec
> commons-io
> javax
> maven.tar.gz
> net
> org
> pom.xml
> settings.template.xml
> src
> target
> {code}
> build log with Maven 3 (expected result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
> The output of mvn verify -X includes:
> {code:java}
> [DEBUG] Using local repository at /home/runner/.m2/repository {code}
> Files after mvn verify with Maven 3:
> {code:none}
> Run ls
> pom.xml
> settings.template.xml
> src
> target
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-8311) empty but existing in settings.xml defaulting to current working directory
Daniel Schmid created MNG-8311:
--
Summary: empty but existing in settings.xml
defaulting to current working directory
Key: MNG-8311
URL: https://issues.apache.org/jira/browse/MNG-8311
Project: Maven
Issue Type: Bug
Components: Core
Affects Versions: 4.0.0-beta-4
Environment: Apache Maven 4.0.0-beta-4
(697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
Maven home: /home/runner/work/maven-repro/maven-repro/apache-maven-4.0.0-beta-4
Java version: 21.0.4, vendor: Eclipse Adoptium, runtime:
/usr/lib/jvm/temurin-21-jdk-amd64
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "6.5.0-1025-azure", arch: "amd64", family: "unix"
Reporter: Daniel Schmid
Attachments: job_logs_mvn3.txt, job_logs_mvn4.txt,
settings.template.xml
If a ~/.m2/settings.xml with an empty element exists in
Maven 4, it downloads dependencies to the current working directory.
Steps to reproduce:
* Create a settings.xml with the exact content from the [settings.xml in the
quick overview|https://maven.apache.org/settings.html#quick-overview]. The
important part is the empty .
* Run mvn verify or similar
* Observe it downloading dependencies to the current repository as opposed to
.m2/repository
Full reproducer using GitHub Actions: https://github.com/danthe1st/maven-repro
build log with Maven 4 (actual result):
https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467
{code:none}
Run ls
aopalliance
apache-maven-4.0.0-beta-4
com
commons-codec
commons-io
javax
maven.tar.gz
net
org
pom.xml
settings.template.xml
src
target
{code}
build log with Maven 3 (expected result):
https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854
{code:none}
Run ls
pom.xml
settings.template.xml
src
target
{code}
--
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=17889583#comment-17889583
]
Guillaume Nodet commented on MNG-8300:
--
[~hboutemy] Could you double check ?
I cannot reproduce the problem on {{beta-3}}, {{beta-4}} or current {{master}}.
Here's a screenshot of beta-3:
!screenshot-1.png!
> [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: Major
> Fix For: 4.0.0-beta-5
>
> Attachments: screenshot-1.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=17889583#comment-17889583
]
Guillaume Nodet edited comment on MNG-8300 at 10/15/24 9:49 AM:
[~hboutemy] Could you double check ?
I cannot reproduce the problem on {{{}beta-3{}}}, {{beta-4}} or current
{{{}master{}}}.
Here's a screenshot of beta-3:
!screenshot-1.png|width=1136,height=164!
was (Author: gnt):
[~hboutemy] Could you double check ?
I cannot reproduce the problem on {{beta-3}}, {{beta-4}} or current {{master}}.
Here's a screenshot of beta-3:
!screenshot-1.png!
> [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: Major
> Fix For: 4.0.0-beta-5
>
> Attachments: screenshot-1.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] [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: - Attachment: screenshot-1.png > [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: Major > Fix For: 4.0.0-beta-5 > > Attachments: screenshot-1.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] [Closed] (MNG-8303) Bump ch.qos.logback:logback-classic from 1.5.8 to 1.5.10
[ https://issues.apache.org/jira/browse/MNG-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8303. Assignee: Tamas Cservenak Resolution: Fixed > Bump ch.qos.logback:logback-classic from 1.5.8 to 1.5.10 > > > Key: MNG-8303 > URL: https://issues.apache.org/jira/browse/MNG-8303 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-beta-5 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1789 > GitHub Pull Request: https://github.com/apache/maven/pull/1794 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8311) empty but existing in settings.xml defaulting to current working directory
[
https://issues.apache.org/jira/browse/MNG-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Schmid updated MNG-8311:
---
Description:
If a ~/.m2/settings.xml with an empty element exists in
Maven 4, it downloads dependencies to the current working directory.
Steps to reproduce:
* Create a settings.xml with the exact content from the [settings.xml in the
quick overview|https://maven.apache.org/settings.html#quick-overview]. The
important part is the empty .
* Run mvn verify or similar
* Observe it downloading dependencies to the current repository as opposed to
.m2/repository
Full reproducer using GitHub Actions: [https://github.com/danthe1st/maven-repro]
build log with Maven 4 (actual result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
Files after mvn verify with Maven 4:
{code:none}
Run ls
aopalliance
apache-maven-4.0.0-beta-4
com
commons-codec
commons-io
javax
maven.tar.gz
net
org
pom.xml
settings.template.xml
src
target
{code}
build log with Maven 3 (expected result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
Files after mvn verify with Maven 3:
{code:none}
Run ls
pom.xml
settings.template.xml
src
target
{code}
was:
If a ~/.m2/settings.xml with an empty element exists in
Maven 4, it downloads dependencies to the current working directory.
Steps to reproduce:
* Create a settings.xml with the exact content from the [settings.xml in the
quick overview|https://maven.apache.org/settings.html#quick-overview]. The
important part is the empty .
* Run mvn verify or similar
* Observe it downloading dependencies to the current repository as opposed to
.m2/repository
Full reproducer using GitHub Actions: https://github.com/danthe1st/maven-repro
build log with Maven 4 (actual result):
https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467
{code:none}
Run ls
aopalliance
apache-maven-4.0.0-beta-4
com
commons-codec
commons-io
javax
maven.tar.gz
net
org
pom.xml
settings.template.xml
src
target
{code}
build log with Maven 3 (expected result):
https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854
{code:none}
Run ls
pom.xml
settings.template.xml
src
target
{code}
> empty but existing in settings.xml defaulting to current
> working directory
> -
>
> Key: MNG-8311
> URL: https://issues.apache.org/jira/browse/MNG-8311
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-beta-4
> Environment: Apache Maven 4.0.0-beta-4
> (697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
> Maven home:
> /home/runner/work/maven-repro/maven-repro/apache-maven-4.0.0-beta-4
> Java version: 21.0.4, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "6.5.0-1025-azure", arch: "amd64", family: "unix"
>Reporter: Daniel Schmid
>Priority: Major
> Attachments: job_logs_mvn3.txt, job_logs_mvn4.txt,
> settings.template.xml
>
>
> If a ~/.m2/settings.xml with an empty element exists in
> Maven 4, it downloads dependencies to the current working directory.
> Steps to reproduce:
> * Create a settings.xml with the exact content from the [settings.xml in the
> quick overview|https://maven.apache.org/settings.html#quick-overview]. The
> important part is the empty .
> * Run mvn verify or similar
> * Observe it downloading dependencies to the current repository as opposed
> to .m2/repository
> Full reproducer using GitHub Actions:
> [https://github.com/danthe1st/maven-repro]
> build log with Maven 4 (actual result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
> Files after mvn verify with Maven 4:
> {code:none}
> Run ls
> aopalliance
> apache-maven-4.0.0-beta-4
> com
> commons-codec
> commons-io
> javax
> maven.tar.gz
> net
> org
> pom.xml
> settings.template.xml
> src
> target
> {code}
> build log with Maven 3 (expected result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
> Files after mvn verify with Maven 3:
> {code:none}
> Run ls
> pom.xml
> settings.template.xml
> src
> target
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-8312) Generate BOMs instead of hand-writing them
Guillaume Nodet created MNG-8312: Summary: Generate BOMs instead of hand-writing them Key: MNG-8312 URL: https://issues.apache.org/jira/browse/MNG-8312 Project: Maven Issue Type: Improvement Reporter: Guillaume Nodet -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8308) Maven should indicate which argument from the CLI is wrong during parsing
[ https://issues.apache.org/jira/browse/MNG-8308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8308. Fix Version/s: (was: 4.0.0-beta-5) Resolution: Cannot Reproduce > Maven should indicate which argument from the CLI is wrong during parsing > - > > Key: MNG-8308 > URL: https://issues.apache.org/jira/browse/MNG-8308 > Project: Maven > Issue Type: Bug >Reporter: Guillaume Nodet >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8311) empty but existing in settings.xml defaulting to current working directory
[
https://issues.apache.org/jira/browse/MNG-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Schmid updated MNG-8311:
---
Description:
If a ~/.m2/settings.xml with an empty element exists in
Maven 4, it downloads dependencies to the current working directory.
Steps to reproduce:
* Create a settings.xml with the exact content from the [settings.xml in the
quick overview|https://maven.apache.org/settings.html#quick-overview]. The
important part is the empty .
* Run mvn verify or similar
* Observe it downloading dependencies to the current repository as opposed to
.m2/repository
Full reproducer using GitHub Actions:
[https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
build log with Maven 4 (actual result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
Files after mvn verify with Maven 4:
{code:none}
Run ls
aopalliance
apache-maven-4.0.0-beta-4
com
commons-codec
commons-io
javax
maven.tar.gz
net
org
pom.xml
settings.template.xml
src
target
{code}
build log with Maven 3 (expected result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
Files after mvn verify with Maven 3:
{code:none}
Run ls
pom.xml
settings.template.xml
src
target
{code}
was:
If a ~/.m2/settings.xml with an empty element exists in
Maven 4, it downloads dependencies to the current working directory.
Steps to reproduce:
* Create a settings.xml with the exact content from the [settings.xml in the
quick overview|https://maven.apache.org/settings.html#quick-overview]. The
important part is the empty .
* Run mvn verify or similar
* Observe it downloading dependencies to the current repository as opposed to
.m2/repository
Full reproducer using GitHub Actions: [https://github.com/danthe1st/maven-repro]
build log with Maven 4 (actual result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
Files after mvn verify with Maven 4:
{code:none}
Run ls
aopalliance
apache-maven-4.0.0-beta-4
com
commons-codec
commons-io
javax
maven.tar.gz
net
org
pom.xml
settings.template.xml
src
target
{code}
build log with Maven 3 (expected result):
[https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
Files after mvn verify with Maven 3:
{code:none}
Run ls
pom.xml
settings.template.xml
src
target
{code}
> empty but existing in settings.xml defaulting to current
> working directory
> -
>
> Key: MNG-8311
> URL: https://issues.apache.org/jira/browse/MNG-8311
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-beta-4
> Environment: Apache Maven 4.0.0-beta-4
> (697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
> Maven home:
> /home/runner/work/maven-repro/maven-repro/apache-maven-4.0.0-beta-4
> Java version: 21.0.4, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "6.5.0-1025-azure", arch: "amd64", family: "unix"
>Reporter: Daniel Schmid
>Priority: Major
> Attachments: job_logs_mvn3.txt, job_logs_mvn4.txt,
> settings.template.xml
>
>
> If a ~/.m2/settings.xml with an empty element exists in
> Maven 4, it downloads dependencies to the current working directory.
> Steps to reproduce:
> * Create a settings.xml with the exact content from the [settings.xml in the
> quick overview|https://maven.apache.org/settings.html#quick-overview]. The
> important part is the empty .
> * Run mvn verify or similar
> * Observe it downloading dependencies to the current repository as opposed
> to .m2/repository
> Full reproducer using GitHub Actions:
> [https://github.com/danthe1st/maven-repro/tree/wrong-local-repo]
> build log with Maven 4 (actual result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681467]
> Files after mvn verify with Maven 4:
> {code:none}
> Run ls
> aopalliance
> apache-maven-4.0.0-beta-4
> com
> commons-codec
> commons-io
> javax
> maven.tar.gz
> net
> org
> pom.xml
> settings.template.xml
> src
> target
> {code}
> build log with Maven 3 (expected result):
> [https://github.com/danthe1st/maven-repro/actions/runs/11343337296/job/31545681854]
> Files after mvn verify with Maven 3:
> {code:none}
> Run ls
> pom.xml
> settings.template.xml
> src
> target
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MARTIFACT-74) describe build groupId
Herve Boutemy created MARTIFACT-74: -- Summary: describe build groupId Key: MARTIFACT-74 URL: https://issues.apache.org/jira/browse/MARTIFACT-74 Project: Maven Artifact Plugin Issue Type: New Feature Components: artifact:describe-build-output (experimental) Affects Versions: 3.5.2 Reporter: Herve Boutemy Fix For: 3.5.3 groupId has been dropped from output of describe-build-output because it takes much output space, with value that is in general quite static: often, groupId is the same for all modules of a build but sometimes, this is not the case: it would be useful to prepend the file-level output with a simple analysis for groupId: - what groupId(s) is used, and how many modules for each? - is there any artifactId that is provided as part of multiple groupId? this should be a simple addition, with compact but useful info -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8304] Bump net.bytebuddy:byte-buddy from 1.15.3 to 1.15.4 [maven]
gnodet merged PR #1791: URL: https://github.com/apache/maven/pull/1791 -- 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-8304) Bump net.bytebuddy:byte-buddy from 1.15.3 to 1.15.4
[ https://issues.apache.org/jira/browse/MNG-8304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8304. Fix Version/s: 4.0.0-beta-5 Assignee: Guillaume Nodet Resolution: Fixed > Bump net.bytebuddy:byte-buddy from 1.15.3 to 1.15.4 > --- > > Key: MNG-8304 > URL: https://issues.apache.org/jira/browse/MNG-8304 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1791 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8309) Improve log infrastructure (first step toward multi-threading log view support)
Guillaume Nodet created MNG-8309: Summary: Improve log infrastructure (first step toward multi-threading log view support) Key: MNG-8309 URL: https://issues.apache.org/jira/browse/MNG-8309 Project: Maven Issue Type: Task Reporter: Guillaume Nodet GitHub Pull Request: https://github.com/apache/maven/pull/1792 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MARTIFACT-74) describe build groupId
[ https://issues.apache.org/jira/browse/MARTIFACT-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889523#comment-17889523 ] Michael Osipov commented on MARTIFACT-74: - We have a similiar approach in Maven Core for the build thread ID. [~kwin], added code to drop group ID if it never changes, but add it if it does. Do you need reference? > describe build groupId > -- > > Key: MARTIFACT-74 > URL: https://issues.apache.org/jira/browse/MARTIFACT-74 > Project: Maven Artifact Plugin > Issue Type: New Feature > Components: artifact:describe-build-output (experimental) >Affects Versions: 3.5.2 >Reporter: Herve Boutemy >Priority: Major > Fix For: 3.5.3 > > > groupId has been dropped from output of describe-build-output because it > takes much output space, with value that is in general quite static: often, > groupId is the same for all modules of a build > but sometimes, this is not the case: it would be useful to prepend the > file-level output with a simple analysis for groupId: > - what groupId(s) is used, and how many modules for each? > - is there any artifactId that is provided as part of multiple groupId? > this should be a simple addition, with compact but useful info -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Update to Maven 4.0.0-beta-4 [maven-mvnd]
gnodet closed pull request #1122: Update to Maven 4.0.0-beta-4 URL: https://github.com/apache/maven-mvnd/pull/1122 -- 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] Fix exports and move help in place [maven-mvnd]
cstamas opened a new pull request, #1166: URL: https://github.com/apache/maven-mvnd/pull/1166 (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] (DOXIA-751) MarkdownSink: Put link and inline code in markup in the right order
Konrad Windszus created DOXIA-751:
-
Summary: MarkdownSink: Put link and inline code in markup in the
right order
Key: DOXIA-751
URL: https://issues.apache.org/jira/browse/DOXIA-751
Project: Maven Doxia
Issue Type: Bug
Reporter: Konrad Windszus
For an inline code being linked the syntax in MD is
{code}
[`code label`](http://example.com)
{code}
instead of
{code}
`[code label](http://example.com)`
{code}
The latter leads to incorrect escaping as everything within a code inline
section is emitted as is (i.e. not interpreted).
However the following APT has a different order (code prefix first, then link
prefix):
{code}
<<<{{{http://example.com}code label}}>>>
{code}
leading to
{code}
Sink.inline(code);
Sink.link("http://example.com";);
Sink.text("code label");
Sink.link_();
Sink.inline_()
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump mockitoVersion from 5.14.1 to 5.14.2 [maven-filtering]
dependabot[bot] opened a new pull request, #130: URL: https://github.com/apache/maven-filtering/pull/130 Bumps `mockitoVersion` from 5.14.1 to 5.14.2. Updates `org.mockito:mockito-junit-jupiter` from 5.14.1 to 5.14.2 Release notes Sourced from https://github.com/mockito/mockito/releases";>org.mockito:mockito-junit-jupiter's releases. v5.14.2 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 5.14.2 2024-10-15 - https://github.com/mockito/mockito/compare/v5.14.1...v5.14.2";>12 commit(s) by Brice Dutheil, Rafael Winterhalter, dependabot[bot] Fix https://redirect.github.com/mockito/mockito/issues/3466";>#3466 nexus publishing configuration [(https://redirect.github.com/mockito/mockito/issues/3470";>#3470)](https://redirect.github.com/mockito/mockito/pull/3470";>mockito/mockito#3470) Bump org.jetbrains.kotlin:kotlin-stdlib from 2.0.20 to 2.0.21 [(https://redirect.github.com/mockito/mockito/issues/3468";>#3468)](https://redirect.github.com/mockito/mockito/pull/3468";>mockito/mockito#3468) Bump bytebuddy from 1.15.3 to 1.15.4 [(https://redirect.github.com/mockito/mockito/issues/3467";>#3467)](https://redirect.github.com/mockito/mockito/pull/3467";>mockito/mockito#3467) Missing 5.14.2 release [(https://redirect.github.com/mockito/mockito/issues/3466";>#3466)](https://redirect.github.com/mockito/mockito/issues/3466";>mockito/mockito#3466) chore: Tests whether JVM warnings / messages on dynamic attach [(https://redirect.github.com/mockito/mockito/issues/3462";>#3462)](https://redirect.github.com/mockito/mockito/pull/3462";>mockito/mockito#3462) Bump junit-jupiter from 5.11.1 to 5.11.2 [(https://redirect.github.com/mockito/mockito/issues/3461";>#3461)](https://redirect.github.com/mockito/mockito/pull/3461";>mockito/mockito#3461) Renames extension modules with mockito- prefix [(https://redirect.github.com/mockito/mockito/issues/3460";>#3460)](https://redirect.github.com/mockito/mockito/pull/3460";>mockito/mockito#3460) Avoid attach warning if Byte Buddy is configured for command-line attach. [(https://redirect.github.com/mockito/mockito/issues/3459";>#3459)](https://redirect.github.com/mockito/mockito/pull/3459";>mockito/mockito#3459) Bump org.shipkit:shipkit-auto-version from 2.0.10 to 2.0.11 [(https://redirect.github.com/mockito/mockito/issues/3458";>#3458)](https://redirect.github.com/mockito/mockito/pull/3458";>mockito/mockito#3458) Bump junit-jupiter from 5.11.0 to 5.11.1 [(https://redirect.github.com/mockito/mockito/issues/3455";>#3455)](https://redirect.github.com/mockito/mockito/pull/3455";>mockito/mockito#3455) Move root project to dedicated core folder [(https://redirect.github.com/mockito/mockito/issues/3444";>#3444)](https://redirect.github.com/mockito/mockito/issues/3444";>mockito/mockito#3444) Bump biz.aQute.bnd:biz.aQute.bnd.gradle from 6.4.0 to 7.0.0 [(https://redirect.github.com/mockito/mockito/issues/3136";>#3136)](https://redirect.github.com/mockito/mockito/pull/3136";>mockito/mockito#3136) Commits https://github.com/mockito/mockito/commit/78348597236d54a84843f454936b8440b006f773";>7834859 Update nexusPublishing to use project.group(https://redirect.github.com/mockito/mockito/issues/3470";>#3470) https://github.com/mockito/mockito/commit/297d147cce8eeab1c43a0d3b7b2645464c7d2750";>297d147 Bump org.jetbrains.kotlin:kotlin-stdlib from 2.0.20 to 2.0.21 (https://redirect.github.com/mockito/mockito/issues/3468";>#3468) https://github.com/mockito/mockito/commit/6a72b103a7987df35abd1f90653794d69393c83e";>6a72b10 Bump bytebuddy from 1.15.3 to 1.15.4 (https://redirect.github.com/mockito/mockito/issues/3467";>#3467) https://github.com/mockito/mockito/commit/68ca2f81494caaeab639d64765bd7b5ff880e43a";>68ca2f8 Bump biz.aQute.bnd:biz.aQute.bnd.gradle from 6.4.0 to 7.0.0 (https://redirect.github.com/mockito/mockito/issues/3136";>#3136) https://github.com/mockito/mockito/commit/147c599ca57749abb17e47507652428cbad49235";>147c599 Bump junit-jupiter from 5.11.1 to 5.11.2 (https://redirect.github.com/mockito/mockito/issues/3461";>#3461) https://github.com/mockito/mockito/commit/99426415c0ceb30e55216c3934854528c83f410e";>9942641 Avoid attach warning if Byte Buddy is configured for command-line attach. (https://redirect.github.com/mockito/mockito/issues/3";>#3... https://github.com/mockito/mockito/commit/560d8558fb612cf9c600767bcc4869b7e75db7bf";>560d855 Removes deprecated and now unused gradle/root/gradle-fix.gradle https://github.com/mockito/mockito/commit/1c0b04b0fde79d2c79dd6643f15fabf65b95bee5";>1c0b04b Rename extension modules with mockito- prefix (https://redirect.github.com/mockito/mockito/issues/3460";>#3460) https://github.com/mockito/mockito/commit/ab32438db0e4f49ead93fd350c3294a7d749db2c";>ab32438 Move core sources to mockito-core https://github.com/mockito/mockito/commit/61dcd838b5400cbdb7f96044f8f9770b5698a98c";>61dc
[jira] [Assigned] (MNG-8302) CLIng and/or rootDirectory being mandatory causes warning at start when no root discovered
[
https://issues.apache.org/jira/browse/MNG-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned MNG-8302:
Assignee: Guillaume Nodet
> CLIng and/or rootDirectory being mandatory causes warning at start when no
> root discovered
> --
>
> Key: MNG-8302
> URL: https://issues.apache.org/jira/browse/MNG-8302
> Project: Maven
> Issue Type: Bug
> Components: Core
>Reporter: Tamas Cservenak
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-beta-5
>
>
> Since CLIng, and/or making rootDirectory mandatory, all the CLI tools (mvn,
> mvnenc) we have so far produce WARNING about "root directory not found" (the
> standard message) when invoked from directory that cannot have root directory
> (like doing some CLI-only mojo from home directory, or invoking mvnenc).
> This is wrong, as this message should be emitted by mvn only (tools like
> mvnenc are not likely to ever use this directory), and even then, ONLY when
> there is POM/project in context.
> When I do {{mvn toolbox:gav-tree -Dgav=...}} from my home directory (mojo is
> direct invocation. does not need project) or just {{mvnenc init}} this
> warning is wrong.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Cleanup after last commit [maven]
gnodet commented on code in PR #1798:
URL: https://github.com/apache/maven/pull/1798#discussion_r1801385119
##
maven-cli/src/main/java/org/apache/maven/cling/invoker/mvnenc/DefaultEncryptInvoker.java:
##
@@ -119,11 +116,11 @@ protected int doExecute(LocalContext context) throws
Exception {
context.addInHeader("");
try {
Thread executeThread = Thread.currentThread();
-terminal.handle(Terminal.Signal.INT, signal ->
executeThread.interrupt());
+context.terminal.handle(Terminal.Signal.INT, signal ->
executeThread.interrupt());
ConsolePrompt.UiConfig config;
-if (terminal.getType().equals(Terminal.TYPE_DUMB)
-|| terminal.getType().equals(Terminal.TYPE_DUMB_COLOR)) {
-System.out.println(terminal.getName() + ": " +
terminal.getType());
+if (context.terminal.getType().equals(Terminal.TYPE_DUMB)
+||
context.terminal.getType().equals(Terminal.TYPE_DUMB_COLOR)) {
+System.out.println(context.terminal.getName() + ": " +
context.terminal.getType());
Review Comment:
All `System.out` should be replaced with `context.terminal.writer()`
--
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] (MNG-8314) Get rid of xxxDebug scripts, make it work with --debug switch instead
[ https://issues.apache.org/jira/browse/MNG-8314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889714#comment-17889714 ] Michael Osipov commented on MNG-8314: - What? MNG-8310? > Get rid of xxxDebug scripts, make it work with --debug switch instead > - > > Key: MNG-8314 > URL: https://issues.apache.org/jira/browse/MNG-8314 > Project: Maven > Issue Type: Improvement > Components: Command Line >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-beta-5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Cleanup after last commit [maven]
gnodet commented on code in PR #1798:
URL: https://github.com/apache/maven/pull/1798#discussion_r1801389897
##
maven-cli/src/main/java/org/apache/maven/cling/invoker/LookupInvoker.java:
##
@@ -413,6 +413,7 @@ protected void helpOrVersionAndMayExit(C context) throws
Exception {
} else {
context.terminal.writer().println(CLIReportingUtils.showVersion());
}
+context.terminal.writer().flush();
Review Comment:
I would add a flush after displaying the help, just so that we don't rely on
`displayHelp` to call `flush`...
--
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] Display proper syntax on help [maven]
cstamas opened a new pull request, #1799: URL: https://github.com/apache/maven/pull/1799 (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
Re: [PR] Minor fixes: proper help syntax and ability to extend core exports [maven]
cstamas merged PR #1799: URL: https://github.com/apache/maven/pull/1799 -- 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] (DOXIA-750) MarkdownSink: Definition Lists don't properly escape inline styles
[
https://issues.apache.org/jira/browse/DOXIA-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated DOXIA-750:
--
Fix Version/s: 2.0.1
> MarkdownSink: Definition Lists don't properly escape inline styles
> --
>
> Key: DOXIA-750
> URL: https://issues.apache.org/jira/browse/DOXIA-750
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Markdown
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 2.0.1
>
>
> If a {{Sink.definition()}} contains e.g. {{Sink.text(...)}} with some inline
> styles, the latter are incorrectly emitted with markdown.
> But since everything within a definition list is basically an HTML block
> (https://spec.commonmark.org/0.31.2/#html-blocks) there every inline style
> must be emitted as HTML as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (DOXIA-751) MarkdownSink: Put link and inline code in markup in the right order
[
https://issues.apache.org/jira/browse/DOXIA-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned DOXIA-751:
-
Assignee: Konrad Windszus
> MarkdownSink: Put link and inline code in markup in the right order
> ---
>
> Key: DOXIA-751
> URL: https://issues.apache.org/jira/browse/DOXIA-751
> Project: Maven Doxia
> Issue Type: Bug
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> For an inline code being linked the syntax in MD is
> {code}
> [`code label`](http://example.com)
> {code}
> instead of
> {code}
> `[code label](http://example.com)`
> {code}
> The latter leads to incorrect escaping as everything within a code inline
> section is emitted as is (i.e. not interpreted).
> However the following APT has a different order (code prefix first, then link
> prefix):
> {code}
> <<<{{{http://example.com}code label}}>>>
> {code}
> leading to
> {code}
> Sink.inline(code);
> Sink.link("http://example.com";);
> Sink.text("code label");
> Sink.link_();
> Sink.inline_()
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [SUREFIRE-2277] Fix bug in RunResult serialisation/deserialisation to (from) failsafe-summary.xml [maven-surefire]
hubertgrzeskowiak commented on code in PR #790:
URL: https://github.com/apache/maven-surefire/pull/790#discussion_r1798627583
##
maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/util/FailsafeSummaryXmlUtils.java:
##
@@ -84,12 +85,14 @@ public static RunResult toRunResult(File
failsafeSummaryXml) throws Exception {
String skipped = xpath.evaluate("/failsafe-summary/skipped", root);
String failureMessage =
xpath.evaluate("/failsafe-summary/failureMessage", root);
String timeout = xpath.evaluate("/failsafe-summary/@timeout",
root);
+String flakes = xpath.evaluate("/failsafe-summary/flakes", root);
Review Comment:
nit: would be better to move this two lines up, right under `skipped`.
`completed`, `errors`, `failures` and `skipped` all belong to the same type of
field as `flakes`.
--
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] Bump org.apache.maven.reporting:maven-reporting-impl from 4.0.0-M15 to 4.0.0 [maven-invoker-plugin]
dependabot[bot] opened a new pull request, #260: URL: https://github.com/apache/maven-invoker-plugin/pull/260 Bumps [org.apache.maven.reporting:maven-reporting-impl](https://github.com/apache/maven-reporting-impl) from 4.0.0-M15 to 4.0.0. Commits https://github.com/apache/maven-reporting-impl/commit/c0d27267bea59eaac967660ce22e3b61dbdd06ad";>c0d2726 [maven-release-plugin] prepare release maven-reporting-impl-4.0.0 https://github.com/apache/maven-reporting-impl/commit/cbe0d8418b626f06f59c6319be8417b9e5e5b235";>cbe0d84 [MSHARED-1438] Provide protected methods for XRef location construction https://github.com/apache/maven-reporting-impl/commit/a4d9b2ff9c031aa270b5366410c39bad2b0eb0ad";>a4d9b2f [MSHARED-1437] Upgrade plugins and components (in ITs) https://github.com/apache/maven-reporting-impl/commit/fc982d1dbe001806080e878599bcabb797174539";>fc982d1 Bump doxiaSitetoolsVersion from 2.0.0-M19 to 2.0.0 https://github.com/apache/maven-reporting-impl/commit/24d3b4688ea82d757704c0acc55312725fbaad29";>24d3b46 Bump org.apache.maven.reporting:maven-reporting-api https://github.com/apache/maven-reporting-impl/commit/a724ac8d8acfd4cedacaaa05b54710a7ec65c6eb";>a724ac8 Bump doxiaVersion from 2.0.0-M12 to 2.0.0 https://github.com/apache/maven-reporting-impl/commit/817d6b881c34771b90c3a884a06b4f6983069d4c";>817d6b8 Bump org.apache.maven.shared:maven-shared-components from 42 to 43 https://github.com/apache/maven-reporting-impl/commit/884e658e04307314385553db509504ab81624ef7";>884e658 Bump org.junit:junit-bom from 5.11.0 to 5.11.2 https://github.com/apache/maven-reporting-impl/commit/3d6495857a64261c35a0c97bd52705c5a9bfae2b";>3d64958 Drop redundant license comment https://github.com/apache/maven-reporting-impl/commit/a9e741ed5460248c51409ae86799410adba20d04";>a9e741e Bump org.junit:junit-bom from 5.10.3 to 5.11.0 Additional commits viewable in https://github.com/apache/maven-reporting-impl/compare/maven-reporting-impl-4.0.0-M15...maven-reporting-impl-4.0.0";>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
[PR] Bump org.mockito:mockito-core from 5.14.1 to 5.14.2 [maven-resolver]
dependabot[bot] opened a new pull request, #583: URL: https://github.com/apache/maven-resolver/pull/583 Bumps [org.mockito:mockito-core](https://github.com/mockito/mockito) from 5.14.1 to 5.14.2. Release notes Sourced from https://github.com/mockito/mockito/releases";>org.mockito:mockito-core's releases. v5.14.2 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 5.14.2 2024-10-15 - https://github.com/mockito/mockito/compare/v5.14.1...v5.14.2";>12 commit(s) by Brice Dutheil, Rafael Winterhalter, dependabot[bot] Fix https://redirect.github.com/mockito/mockito/issues/3466";>#3466 nexus publishing configuration [(https://redirect.github.com/mockito/mockito/issues/3470";>#3470)](https://redirect.github.com/mockito/mockito/pull/3470";>mockito/mockito#3470) Bump org.jetbrains.kotlin:kotlin-stdlib from 2.0.20 to 2.0.21 [(https://redirect.github.com/mockito/mockito/issues/3468";>#3468)](https://redirect.github.com/mockito/mockito/pull/3468";>mockito/mockito#3468) Bump bytebuddy from 1.15.3 to 1.15.4 [(https://redirect.github.com/mockito/mockito/issues/3467";>#3467)](https://redirect.github.com/mockito/mockito/pull/3467";>mockito/mockito#3467) Missing 5.14.2 release [(https://redirect.github.com/mockito/mockito/issues/3466";>#3466)](https://redirect.github.com/mockito/mockito/issues/3466";>mockito/mockito#3466) chore: Tests whether JVM warnings / messages on dynamic attach [(https://redirect.github.com/mockito/mockito/issues/3462";>#3462)](https://redirect.github.com/mockito/mockito/pull/3462";>mockito/mockito#3462) Bump junit-jupiter from 5.11.1 to 5.11.2 [(https://redirect.github.com/mockito/mockito/issues/3461";>#3461)](https://redirect.github.com/mockito/mockito/pull/3461";>mockito/mockito#3461) Renames extension modules with mockito- prefix [(https://redirect.github.com/mockito/mockito/issues/3460";>#3460)](https://redirect.github.com/mockito/mockito/pull/3460";>mockito/mockito#3460) Avoid attach warning if Byte Buddy is configured for command-line attach. [(https://redirect.github.com/mockito/mockito/issues/3459";>#3459)](https://redirect.github.com/mockito/mockito/pull/3459";>mockito/mockito#3459) Bump org.shipkit:shipkit-auto-version from 2.0.10 to 2.0.11 [(https://redirect.github.com/mockito/mockito/issues/3458";>#3458)](https://redirect.github.com/mockito/mockito/pull/3458";>mockito/mockito#3458) Bump junit-jupiter from 5.11.0 to 5.11.1 [(https://redirect.github.com/mockito/mockito/issues/3455";>#3455)](https://redirect.github.com/mockito/mockito/pull/3455";>mockito/mockito#3455) Move root project to dedicated core folder [(https://redirect.github.com/mockito/mockito/issues/3444";>#3444)](https://redirect.github.com/mockito/mockito/issues/3444";>mockito/mockito#3444) Bump biz.aQute.bnd:biz.aQute.bnd.gradle from 6.4.0 to 7.0.0 [(https://redirect.github.com/mockito/mockito/issues/3136";>#3136)](https://redirect.github.com/mockito/mockito/pull/3136";>mockito/mockito#3136) Commits https://github.com/mockito/mockito/commit/78348597236d54a84843f454936b8440b006f773";>7834859 Update nexusPublishing to use project.group(https://redirect.github.com/mockito/mockito/issues/3470";>#3470) https://github.com/mockito/mockito/commit/297d147cce8eeab1c43a0d3b7b2645464c7d2750";>297d147 Bump org.jetbrains.kotlin:kotlin-stdlib from 2.0.20 to 2.0.21 (https://redirect.github.com/mockito/mockito/issues/3468";>#3468) https://github.com/mockito/mockito/commit/6a72b103a7987df35abd1f90653794d69393c83e";>6a72b10 Bump bytebuddy from 1.15.3 to 1.15.4 (https://redirect.github.com/mockito/mockito/issues/3467";>#3467) https://github.com/mockito/mockito/commit/68ca2f81494caaeab639d64765bd7b5ff880e43a";>68ca2f8 Bump biz.aQute.bnd:biz.aQute.bnd.gradle from 6.4.0 to 7.0.0 (https://redirect.github.com/mockito/mockito/issues/3136";>#3136) https://github.com/mockito/mockito/commit/147c599ca57749abb17e47507652428cbad49235";>147c599 Bump junit-jupiter from 5.11.1 to 5.11.2 (https://redirect.github.com/mockito/mockito/issues/3461";>#3461) https://github.com/mockito/mockito/commit/99426415c0ceb30e55216c3934854528c83f410e";>9942641 Avoid attach warning if Byte Buddy is configured for command-line attach. (https://redirect.github.com/mockito/mockito/issues/3";>#3... https://github.com/mockito/mockito/commit/560d8558fb612cf9c600767bcc4869b7e75db7bf";>560d855 Removes deprecated and now unused gradle/root/gradle-fix.gradle https://github.com/mockito/mockito/commit/1c0b04b0fde79d2c79dd6643f15fabf65b95bee5";>1c0b04b Rename extension modules with mockito- prefix (https://redirect.github.com/mockito/mockito/issues/3460";>#3460) https://github.com/mockito/mockito/commit/ab32438db0e4f49ead93fd350c3294a7d749db2c";>ab32438 Move core sources to mockito-core https://github.com/mockito/mockito/commit/61dcd838b5400cbdb7f96044f8f9770b5698a98c";>61dcd83 Switch gradleEnterprise to
[jira] [Closed] (MNG-5761) Dependency management is not transitive.
[ https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-5761. Fix Version/s: 4.0.0-beta-5 (was: 4.0.x-candidate) Resolution: Fixed > Dependency management is not transitive. > > > Key: MNG-5761 > URL: https://issues.apache.org/jira/browse/MNG-5761 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.2.5 >Reporter: Jeff Schnitzer >Priority: Critical > Fix For: 4.0.0-beta-5 > > Attachments: MNG-5761.zip, depending-pom2.xml > > > A detailed description of the issue is here: > http://stackoverflow.com/questions/28312975/maven-dependencymanagement-version-ignored-in-transitive-dependencies > The short of it is that maven appears to be using the wrong > version in a transitive dependency. There are two > relevant sections in the build, one pulled in by guice > and one pulled in by gwizard-parent. These are the dependency paths from the > top: > gwizard-example -> gwizard-config -> gwizard-parent > gwizard-example -> gwizard-config -> guice -> guice-parent > gwizard-parent's dependencyManagement specifies guava 18 > guice-parent's dependencyManagement specifies guava 16 > Guava 16 is winning. This seems highly undesirable, and in fact it breaks our > build. I would expect that in a version # fight, "closest to the top" should > win. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump org.apache.maven.reporting:maven-reporting-impl from 4.0.0-M15 to 4.0.0 [maven-javadoc-plugin]
dependabot[bot] opened a new pull request, #328: URL: https://github.com/apache/maven-javadoc-plugin/pull/328 Bumps [org.apache.maven.reporting:maven-reporting-impl](https://github.com/apache/maven-reporting-impl) from 4.0.0-M15 to 4.0.0. Commits https://github.com/apache/maven-reporting-impl/commit/c0d27267bea59eaac967660ce22e3b61dbdd06ad";>c0d2726 [maven-release-plugin] prepare release maven-reporting-impl-4.0.0 https://github.com/apache/maven-reporting-impl/commit/cbe0d8418b626f06f59c6319be8417b9e5e5b235";>cbe0d84 [MSHARED-1438] Provide protected methods for XRef location construction https://github.com/apache/maven-reporting-impl/commit/a4d9b2ff9c031aa270b5366410c39bad2b0eb0ad";>a4d9b2f [MSHARED-1437] Upgrade plugins and components (in ITs) https://github.com/apache/maven-reporting-impl/commit/fc982d1dbe001806080e878599bcabb797174539";>fc982d1 Bump doxiaSitetoolsVersion from 2.0.0-M19 to 2.0.0 https://github.com/apache/maven-reporting-impl/commit/24d3b4688ea82d757704c0acc55312725fbaad29";>24d3b46 Bump org.apache.maven.reporting:maven-reporting-api https://github.com/apache/maven-reporting-impl/commit/a724ac8d8acfd4cedacaaa05b54710a7ec65c6eb";>a724ac8 Bump doxiaVersion from 2.0.0-M12 to 2.0.0 https://github.com/apache/maven-reporting-impl/commit/817d6b881c34771b90c3a884a06b4f6983069d4c";>817d6b8 Bump org.apache.maven.shared:maven-shared-components from 42 to 43 https://github.com/apache/maven-reporting-impl/commit/884e658e04307314385553db509504ab81624ef7";>884e658 Bump org.junit:junit-bom from 5.11.0 to 5.11.2 https://github.com/apache/maven-reporting-impl/commit/3d6495857a64261c35a0c97bd52705c5a9bfae2b";>3d64958 Drop redundant license comment https://github.com/apache/maven-reporting-impl/commit/a9e741ed5460248c51409ae86799410adba20d04";>a9e741e Bump org.junit:junit-bom from 5.10.3 to 5.11.0 Additional commits viewable in https://github.com/apache/maven-reporting-impl/compare/maven-reporting-impl-4.0.0-M15...maven-reporting-impl-4.0.0";>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
[PR] Bump org.apache.maven.reporting:maven-reporting-impl from 4.0.0-M15 to 4.0.0 [maven-checkstyle-plugin]
dependabot[bot] opened a new pull request, #153: URL: https://github.com/apache/maven-checkstyle-plugin/pull/153 Bumps [org.apache.maven.reporting:maven-reporting-impl](https://github.com/apache/maven-reporting-impl) from 4.0.0-M15 to 4.0.0. Commits https://github.com/apache/maven-reporting-impl/commit/c0d27267bea59eaac967660ce22e3b61dbdd06ad";>c0d2726 [maven-release-plugin] prepare release maven-reporting-impl-4.0.0 https://github.com/apache/maven-reporting-impl/commit/cbe0d8418b626f06f59c6319be8417b9e5e5b235";>cbe0d84 [MSHARED-1438] Provide protected methods for XRef location construction https://github.com/apache/maven-reporting-impl/commit/a4d9b2ff9c031aa270b5366410c39bad2b0eb0ad";>a4d9b2f [MSHARED-1437] Upgrade plugins and components (in ITs) https://github.com/apache/maven-reporting-impl/commit/fc982d1dbe001806080e878599bcabb797174539";>fc982d1 Bump doxiaSitetoolsVersion from 2.0.0-M19 to 2.0.0 https://github.com/apache/maven-reporting-impl/commit/24d3b4688ea82d757704c0acc55312725fbaad29";>24d3b46 Bump org.apache.maven.reporting:maven-reporting-api https://github.com/apache/maven-reporting-impl/commit/a724ac8d8acfd4cedacaaa05b54710a7ec65c6eb";>a724ac8 Bump doxiaVersion from 2.0.0-M12 to 2.0.0 https://github.com/apache/maven-reporting-impl/commit/817d6b881c34771b90c3a884a06b4f6983069d4c";>817d6b8 Bump org.apache.maven.shared:maven-shared-components from 42 to 43 https://github.com/apache/maven-reporting-impl/commit/884e658e04307314385553db509504ab81624ef7";>884e658 Bump org.junit:junit-bom from 5.11.0 to 5.11.2 https://github.com/apache/maven-reporting-impl/commit/3d6495857a64261c35a0c97bd52705c5a9bfae2b";>3d64958 Drop redundant license comment https://github.com/apache/maven-reporting-impl/commit/a9e741ed5460248c51409ae86799410adba20d04";>a9e741e Bump org.junit:junit-bom from 5.10.3 to 5.11.0 Additional commits viewable in https://github.com/apache/maven-reporting-impl/compare/maven-reporting-impl-4.0.0-M15...maven-reporting-impl-4.0.0";>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] [Commented] (MSITE-1018) LastPublicationTimestamp shows a fixed timestamp instead of the last build date
[
https://issues.apache.org/jira/browse/MSITE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889963#comment-17889963
]
Michael Osipov commented on MSITE-1018:
---
[~pottlinger], based on [~hboutemy]'s comment there is one really easy solution
for you:
{code}
$ git diff
diff --git a/pom.xml b/pom.xml
index 06465b8..ee475ec 100644
--- a/pom.xml
+++ b/pom.xml
@@ -239,6 +239,7 @@
${project.build.sourceEncoding}
${project.build.sourceEncoding}
false
+ X
{code}
and you have the previous behavior back.
> LastPublicationTimestamp shows a fixed timestamp instead of the last build
> date
> ---
>
> Key: MSITE-1018
> URL: https://issues.apache.org/jira/browse/MSITE-1018
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.20.0
>Reporter: Philipp Ottlinger
>Assignee: Michael Osipov
>Priority: Major
>
> After having updated Apache Creadur Tentacles to v3.20.0 the
> LastPublicationDate shown is always fixed to 1970-01-01 in versions
> before the last build date was used to render this variable.
> Is there a configuration option to get this behaviour back?
> * https://github.com/apache/creadur-tentacles/blob/master/pom.xml
> * https://creadur.apache.org/tentacles/
> Apache Creadur Whisker also uses a fixed project.build.outputTimestamp value
> in its pom but its site renders the lastPubDate correctly:
> * https://creadur.apache.org/whisker/
> * https://github.com/apache/creadur-whisker/blob/master/pom.xml
> Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MSITE-1018) LastPublicationTimestamp shows a fixed timestamp instead of the last build date
[
https://issues.apache.org/jira/browse/MSITE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889963#comment-17889963
]
Michael Osipov edited comment on MSITE-1018 at 10/16/24 6:51 AM:
-
[~pottlinger], based on [~hboutemy]'s comment there is one really easy solution
for you:
{code}
$ git diff
diff --git a/pom.xml b/pom.xml
index 06465b8..ee475ec 100644
--- a/pom.xml
+++ b/pom.xml
@@ -239,6 +239,7 @@
${project.build.sourceEncoding}
${project.build.sourceEncoding}
false
+ X
{code}
and you have the previous behavior back.
Should have provided this in the first place, apologies for that.
was (Author: michael-o):
[~pottlinger], based on [~hboutemy]'s comment there is one really easy solution
for you:
{code}
$ git diff
diff --git a/pom.xml b/pom.xml
index 06465b8..ee475ec 100644
--- a/pom.xml
+++ b/pom.xml
@@ -239,6 +239,7 @@
${project.build.sourceEncoding}
${project.build.sourceEncoding}
false
+ X
{code}
and you have the previous behavior back.
> LastPublicationTimestamp shows a fixed timestamp instead of the last build
> date
> ---
>
> Key: MSITE-1018
> URL: https://issues.apache.org/jira/browse/MSITE-1018
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.20.0
>Reporter: Philipp Ottlinger
>Assignee: Michael Osipov
>Priority: Major
>
> After having updated Apache Creadur Tentacles to v3.20.0 the
> LastPublicationDate shown is always fixed to 1970-01-01 in versions
> before the last build date was used to render this variable.
> Is there a configuration option to get this behaviour back?
> * https://github.com/apache/creadur-tentacles/blob/master/pom.xml
> * https://creadur.apache.org/tentacles/
> Apache Creadur Whisker also uses a fixed project.build.outputTimestamp value
> in its pom but its site renders the lastPubDate correctly:
> * https://creadur.apache.org/whisker/
> * https://github.com/apache/creadur-whisker/blob/master/pom.xml
> Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSITE-1018) LastPublicationTimestamp shows a fixed timestamp instead of the last build date
[ https://issues.apache.org/jira/browse/MSITE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889939#comment-17889939 ] Michael Osipov commented on MSITE-1018: --- The plugin Parameter is read write so it can eb changed any time. > LastPublicationTimestamp shows a fixed timestamp instead of the last build > date > --- > > Key: MSITE-1018 > URL: https://issues.apache.org/jira/browse/MSITE-1018 > Project: Maven Site Plugin > Issue Type: Bug >Affects Versions: 3.20.0 >Reporter: Philipp Ottlinger >Assignee: Michael Osipov >Priority: Major > > After having updated Apache Creadur Tentacles to v3.20.0 the > LastPublicationDate shown is always fixed to 1970-01-01 in versions > before the last build date was used to render this variable. > Is there a configuration option to get this behaviour back? > * https://github.com/apache/creadur-tentacles/blob/master/pom.xml > * https://creadur.apache.org/tentacles/ > Apache Creadur Whisker also uses a fixed project.build.outputTimestamp value > in its pom but its site renders the lastPubDate correctly: > * https://creadur.apache.org/whisker/ > * https://github.com/apache/creadur-whisker/blob/master/pom.xml > Thanks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-5761) Dependency management is not transitive.
[ https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889942#comment-17889942 ] Christian Schulte commented on MNG-5761: [~Didier Loiseau] Indifference, not bitterness. parent - module1 - module2 Build in parent, get a different dependency tree. Build in module1, get a different dependency tree. Build in module2, get a different dependency tree. What build system is that, not fixing a key feature for more than a decade and not even now. Requested by various users independently for Maven 2, Maven 3, Maven 4 and what not. Repeatedly reported. Repeatedly closed won't fix. Repeatedly reopened. Ridiculous. Has driven away lots of users. Those said "millions of users" never existed. Received a lot of justified rants for things like this. > Dependency management is not transitive. > > > Key: MNG-5761 > URL: https://issues.apache.org/jira/browse/MNG-5761 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.2.5 >Reporter: Jeff Schnitzer >Priority: Critical > Fix For: 4.0.x-candidate > > Attachments: MNG-5761.zip, depending-pom2.xml > > > A detailed description of the issue is here: > http://stackoverflow.com/questions/28312975/maven-dependencymanagement-version-ignored-in-transitive-dependencies > The short of it is that maven appears to be using the wrong > version in a transitive dependency. There are two > relevant sections in the build, one pulled in by guice > and one pulled in by gwizard-parent. These are the dependency paths from the > top: > gwizard-example -> gwizard-config -> gwizard-parent > gwizard-example -> gwizard-config -> guice -> guice-parent > gwizard-parent's dependencyManagement specifies guava 18 > guice-parent's dependencyManagement specifies guava 16 > Guava 16 is winning. This seems highly undesirable, and in fact it breaks our > build. I would expect that in a version # fight, "closest to the top" should > win. -- This message was sent by Atlassian Jira (v8.20.10#820010)
