[jira] [Created] (MARTIFACT-66) Upgrade maven resolver version 1.9.18 to 1.9.20
Zhongming Hua created MARTIFACT-66: -- Summary: Upgrade maven resolver version 1.9.18 to 1.9.20 Key: MARTIFACT-66 URL: https://issues.apache.org/jira/browse/MARTIFACT-66 Project: Maven Artifact Plugin Issue Type: Task Reporter: Zhongming Hua -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-7976) Investigate MNG-6127 IT instability
[ https://issues.apache.org/jira/browse/MNG-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua closed MNG-7976. -- > Investigate MNG-6127 IT instability > --- > > Key: MNG-7976 > URL: https://issues.apache.org/jira/browse/MNG-7976 > Project: Maven > Issue Type: Task > Components: Core >Reporter: Tamas Cservenak >Assignee: Zhongming Hua >Priority: Major > Fix For: 4.0.0-alpha-13 > > > The MNG-6127 IT quite often fails, and passes when CI job rebuilt, seems > unstable. > Look into it why (lurking concurrency bug somewhere? or just the IT is > flakey?) and fix it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MNG-7976) Investigate MNG-6127 IT instability
[ https://issues.apache.org/jira/browse/MNG-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua resolved MNG-7976. Fix Version/s: 4.0.0-alpha-13 (was: 4.0.x-candidate) (was: 4.0.0) Resolution: Fixed > Investigate MNG-6127 IT instability > --- > > Key: MNG-7976 > URL: https://issues.apache.org/jira/browse/MNG-7976 > Project: Maven > Issue Type: Task > Components: Core >Reporter: Tamas Cservenak >Assignee: Zhongming Hua >Priority: Major > Fix For: 4.0.0-alpha-13 > > > The MNG-6127 IT quite often fails, and passes when CI job rebuilt, seems > unstable. > Look into it why (lurking concurrency bug somewhere? or just the IT is > flakey?) and fix it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-7976) Investigate MNG-6127 IT instability
[ https://issues.apache.org/jira/browse/MNG-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua reassigned MNG-7976: -- Assignee: Zhongming Hua > Investigate MNG-6127 IT instability > --- > > Key: MNG-7976 > URL: https://issues.apache.org/jira/browse/MNG-7976 > Project: Maven > Issue Type: Task > Components: Core >Reporter: Tamas Cservenak >Assignee: Zhongming Hua >Priority: Major > Fix For: 4.0.x-candidate, 4.0.0 > > > The MNG-6127 IT quite often fails, and passes when CI job rebuilt, seems > unstable. > Look into it why (lurking concurrency bug somewhere? or just the IT is > flakey?) and fix it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MNG-8060) Use String#isEmpty instead of length
[ https://issues.apache.org/jira/browse/MNG-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua resolved MNG-8060. Fix Version/s: 4.0.0-alpha-13 Resolution: Fixed > Use String#isEmpty instead of length > > > Key: MNG-8060 > URL: https://issues.apache.org/jira/browse/MNG-8060 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Assignee: Zhongming Hua >Priority: Minor > Fix For: 4.0.0-alpha-13 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8060) Use String#isEmpty instead of length
[ https://issues.apache.org/jira/browse/MNG-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua reassigned MNG-8060: -- Assignee: Zhongming Hua > Use String#isEmpty instead of length > > > Key: MNG-8060 > URL: https://issues.apache.org/jira/browse/MNG-8060 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Assignee: Zhongming Hua >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8060) Use String#isEmpty instead of length
[ https://issues.apache.org/jira/browse/MNG-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua closed MNG-8060. -- > Use String#isEmpty instead of length > > > Key: MNG-8060 > URL: https://issues.apache.org/jira/browse/MNG-8060 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Assignee: Zhongming Hua >Priority: Minor > Fix For: 4.0.0-alpha-13 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8060) Use String#isEmpty instead of length
[ https://issues.apache.org/jira/browse/MNG-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua updated MNG-8060: --- Priority: Minor (was: Major) > Use String#isEmpty instead of length > > > Key: MNG-8060 > URL: https://issues.apache.org/jira/browse/MNG-8060 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8060) Use String#isEmpty instead of length
Zhongming Hua created MNG-8060: -- Summary: Use String#isEmpty instead of length Key: MNG-8060 URL: https://issues.apache.org/jira/browse/MNG-8060 Project: Maven Issue Type: Task Reporter: Zhongming Hua -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MSHADE-469) Cannot generate a jar since switching from 3.4.1 to 3.5.x
[
https://issues.apache.org/jira/browse/MSHADE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongming Hua resolved MSHADE-469.
--
Assignee: Zhongming Hua
Resolution: Duplicate
> Cannot generate a jar since switching from 3.4.1 to 3.5.x
> -
>
> Key: MSHADE-469
> URL: https://issues.apache.org/jira/browse/MSHADE-469
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0, 3.5.1
>Reporter: Emmanuel Lécharny
>Assignee: Zhongming Hua
>Priority: Major
>
> Hi!
> I have a working build for the Apache Diretcory LDAP API project that worked
> pretty well until I tried to switch to maven shade plugin version 3.5.0/3.5.1.
> The error I get is
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.5.0:shade (default) on project
> api-all: Execution default of goal
> org.apache.maven.plugins:maven-shade-plugin:3.5.0:shade failed: For artifact
> {org.apache.directory.api:api-asn1-api:null:jar}: The version cannot be
> empty. -> [Help 1]
> {noformat}
> The project's pom:
> [https://repo.maven.apache.org/maven2/org/apache/directory/api/api-all/2.1.6/api-all-2.1.6.pom|https://repo.maven.apache.org/maven2/org/apache/directory/api/api-all/2.1.6/api-all-2.1.6.pom]
> The parent's pom:
> [https://repo.maven.apache.org/maven2/org/apache/directory/api/api-parent/2.1.6/api-parent-2.1.6.pom|https://repo.maven.apache.org/maven2/org/apache/directory/api/api-parent/2.1.6/api-parent-2.1.6.pom]
> The parent's parent's pom, where the shade plugin version is declared:
> [https://repo.maven.apache.org/maven2/org/apache/directory/project/project/48/project-48.pom|https://repo.maven.apache.org/maven2/org/apache/directory/project/project/48/project-48.pom]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSHADE-469) Cannot generate a jar since switching from 3.4.1 to 3.5.x
[
https://issues.apache.org/jira/browse/MSHADE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818665#comment-17818665
]
Zhongming Hua commented on MSHADE-469:
--
[~elecharny]
This bug has been fixed in 3.5.2, please wait until 3.5.2 is released to use it.
> Cannot generate a jar since switching from 3.4.1 to 3.5.x
> -
>
> Key: MSHADE-469
> URL: https://issues.apache.org/jira/browse/MSHADE-469
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0, 3.5.1
>Reporter: Emmanuel Lécharny
>Priority: Major
>
> Hi!
> I have a working build for the Apache Diretcory LDAP API project that worked
> pretty well until I tried to switch to maven shade plugin version 3.5.0/3.5.1.
> The error I get is
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.5.0:shade (default) on project
> api-all: Execution default of goal
> org.apache.maven.plugins:maven-shade-plugin:3.5.0:shade failed: For artifact
> {org.apache.directory.api:api-asn1-api:null:jar}: The version cannot be
> empty. -> [Help 1]
> {noformat}
> The project's pom:
> [https://repo.maven.apache.org/maven2/org/apache/directory/api/api-all/2.1.6/api-all-2.1.6.pom|https://repo.maven.apache.org/maven2/org/apache/directory/api/api-all/2.1.6/api-all-2.1.6.pom]
> The parent's pom:
> [https://repo.maven.apache.org/maven2/org/apache/directory/api/api-parent/2.1.6/api-parent-2.1.6.pom|https://repo.maven.apache.org/maven2/org/apache/directory/api/api-parent/2.1.6/api-parent-2.1.6.pom]
> The parent's parent's pom, where the shade plugin version is declared:
> [https://repo.maven.apache.org/maven2/org/apache/directory/project/project/48/project-48.pom|https://repo.maven.apache.org/maven2/org/apache/directory/project/project/48/project-48.pom]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-8046) Upgrade github action version from v3 to v4
[ https://issues.apache.org/jira/browse/MNG-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua closed MNG-8046. -- > Upgrade github action version from v3 to v4 > --- > > Key: MNG-8046 > URL: https://issues.apache.org/jira/browse/MNG-8046 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Assignee: Zhongming Hua >Priority: Major > Fix For: 4.0.0-alpha-13 > > > Node.js 16 actions are deprecated. Please update the following actions to use > Node.js 20: actions/checkout@v3, actions/setup-java@v3. For more information > see: > https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MNG-8046) Upgrade github action version from v3 to v4
[ https://issues.apache.org/jira/browse/MNG-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua resolved MNG-8046. Fix Version/s: 4.0.0-alpha-13 Assignee: Zhongming Hua Resolution: Resolved > Upgrade github action version from v3 to v4 > --- > > Key: MNG-8046 > URL: https://issues.apache.org/jira/browse/MNG-8046 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Assignee: Zhongming Hua >Priority: Major > Fix For: 4.0.0-alpha-13 > > > Node.js 16 actions are deprecated. Please update the following actions to use > Node.js 20: actions/checkout@v3, actions/setup-java@v3. For more information > see: > https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8046) Upgrade github action version from v3 to v4
Zhongming Hua created MNG-8046: -- Summary: Upgrade github action version from v3 to v4 Key: MNG-8046 URL: https://issues.apache.org/jira/browse/MNG-8046 Project: Maven Issue Type: Task Reporter: Zhongming Hua Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-java@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MNG-8013) Integration testing process logs can be output github artifact
[ https://issues.apache.org/jira/browse/MNG-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua resolved MNG-8013. Resolution: Resolved > Integration testing process logs can be output github artifact > -- > > Key: MNG-8013 > URL: https://issues.apache.org/jira/browse/MNG-8013 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Assignee: Zhongming Hua >Priority: Major > Fix For: 4.0.0-alpha-13 > > Attachments: image-2024-01-12-22-55-07-271.png > > > Related Jira: https://issues.apache.org/jira/browse/MNG-7976 > If we can show the maven build process in maven's ci log, such as > maven-integration-testing/core-it-suit/target/test-classes/mng-6127-plugin-execution-configuration-interference/project/log.txt. > we can more easily troubleshoot some occasional problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8013) Integration testing process logs can be output github artifact
[ https://issues.apache.org/jira/browse/MNG-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua closed MNG-8013. -- > Integration testing process logs can be output github artifact > -- > > Key: MNG-8013 > URL: https://issues.apache.org/jira/browse/MNG-8013 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Assignee: Zhongming Hua >Priority: Major > Fix For: 4.0.0-alpha-13 > > Attachments: image-2024-01-12-22-55-07-271.png > > > Related Jira: https://issues.apache.org/jira/browse/MNG-7976 > If we can show the maven build process in maven's ci log, such as > maven-integration-testing/core-it-suit/target/test-classes/mng-6127-plugin-execution-configuration-interference/project/log.txt. > we can more easily troubleshoot some occasional problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8013) Integration testing process logs can be output github artifact
[ https://issues.apache.org/jira/browse/MNG-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua updated MNG-8013: --- Fix Version/s: 4.0.0-alpha-13 > Integration testing process logs can be output github artifact > -- > > Key: MNG-8013 > URL: https://issues.apache.org/jira/browse/MNG-8013 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Assignee: Zhongming Hua >Priority: Major > Fix For: 4.0.0-alpha-13 > > Attachments: image-2024-01-12-22-55-07-271.png > > > Related Jira: https://issues.apache.org/jira/browse/MNG-7976 > If we can show the maven build process in maven's ci log, such as > maven-integration-testing/core-it-suit/target/test-classes/mng-6127-plugin-execution-configuration-interference/project/log.txt. > we can more easily troubleshoot some occasional problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8013) Integration testing process logs can be output github artifact
[ https://issues.apache.org/jira/browse/MNG-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua reassigned MNG-8013: -- Assignee: Zhongming Hua > Integration testing process logs can be output github artifact > -- > > Key: MNG-8013 > URL: https://issues.apache.org/jira/browse/MNG-8013 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Assignee: Zhongming Hua >Priority: Major > Attachments: image-2024-01-12-22-55-07-271.png > > > Related Jira: https://issues.apache.org/jira/browse/MNG-7976 > If we can show the maven build process in maven's ci log, such as > maven-integration-testing/core-it-suit/target/test-classes/mng-6127-plugin-execution-configuration-interference/project/log.txt. > we can more easily troubleshoot some occasional problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8013) Integration testing process logs can be output github artifact
[ https://issues.apache.org/jira/browse/MNG-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17806080#comment-17806080 ] Zhongming Hua commented on MNG-8013: Thank you, [~sjaranowski] I have submitted the PR, but I find that we also have this problem: [https://github.com/actions/upload-artifact/issues/240] !image-2024-01-12-22-55-07-271.png! > Integration testing process logs can be output github artifact > -- > > Key: MNG-8013 > URL: https://issues.apache.org/jira/browse/MNG-8013 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Priority: Major > Attachments: image-2024-01-12-22-55-07-271.png > > > Related Jira: https://issues.apache.org/jira/browse/MNG-7976 > If we can show the maven build process in maven's ci log, such as > maven-integration-testing/core-it-suit/target/test-classes/mng-6127-plugin-execution-configuration-interference/project/log.txt. > we can more easily troubleshoot some occasional problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8013) Integration testing process logs can be output github artifact
[ https://issues.apache.org/jira/browse/MNG-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua updated MNG-8013: --- Attachment: image-2024-01-12-22-55-07-271.png > Integration testing process logs can be output github artifact > -- > > Key: MNG-8013 > URL: https://issues.apache.org/jira/browse/MNG-8013 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Priority: Major > Attachments: image-2024-01-12-22-55-07-271.png > > > Related Jira: https://issues.apache.org/jira/browse/MNG-7976 > If we can show the maven build process in maven's ci log, such as > maven-integration-testing/core-it-suit/target/test-classes/mng-6127-plugin-execution-configuration-interference/project/log.txt. > we can more easily troubleshoot some occasional problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8013) Integration testing process logs can be output github artifact
[ https://issues.apache.org/jira/browse/MNG-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua updated MNG-8013: --- Summary: Integration testing process logs can be output github artifact (was: Integration testing process logs can be output Github action log) > Integration testing process logs can be output github artifact > -- > > Key: MNG-8013 > URL: https://issues.apache.org/jira/browse/MNG-8013 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Priority: Major > > Related Jira: https://issues.apache.org/jira/browse/MNG-7976 > If we can show the maven build process in maven's ci log, such as > maven-integration-testing/core-it-suit/target/test-classes/mng-6127-plugin-execution-configuration-interference/project/log.txt. > we can more easily troubleshoot some occasional problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8013) Integration testing process logs can be output Github action log
[ https://issues.apache.org/jira/browse/MNG-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805930#comment-17805930 ] Zhongming Hua commented on MNG-8013: [~cstamas] Yes, Let me finish it. > Integration testing process logs can be output Github action log > > > Key: MNG-8013 > URL: https://issues.apache.org/jira/browse/MNG-8013 > Project: Maven > Issue Type: Task >Reporter: Zhongming Hua >Priority: Major > > Related Jira: https://issues.apache.org/jira/browse/MNG-7976 > If we can show the maven build process in maven's ci log, such as > maven-integration-testing/core-it-suit/target/test-classes/mng-6127-plugin-execution-configuration-interference/project/log.txt. > we can more easily troubleshoot some occasional problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8013) Integration testing process logs can be output Github action log
Zhongming Hua created MNG-8013: -- Summary: Integration testing process logs can be output Github action log Key: MNG-8013 URL: https://issues.apache.org/jira/browse/MNG-8013 Project: Maven Issue Type: Task Reporter: Zhongming Hua Related Jira: https://issues.apache.org/jira/browse/MNG-7976 If we can show the maven build process in maven's ci log, such as maven-integration-testing/core-it-suit/target/test-classes/mng-6127-plugin-execution-configuration-interference/project/log.txt. we can more easily troubleshoot some occasional problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHADE-464) Maven 3.6.3 as minimum requirements
[ https://issues.apache.org/jira/browse/MSHADE-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805865#comment-17805865 ] Zhongming Hua commented on MSHADE-464: -- [~sjaranowski] Done. > Maven 3.6.3 as minimum requirements > --- > > Key: MSHADE-464 > URL: https://issues.apache.org/jira/browse/MSHADE-464 > Project: Maven Shade Plugin > Issue Type: Task >Reporter: Zhongming Hua >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1352) Maven 3.6.3 as minimum requirements
Zhongming Hua created MSHARED-1352: -- Summary: Maven 3.6.3 as minimum requirements Key: MSHARED-1352 URL: https://issues.apache.org/jira/browse/MSHARED-1352 Project: Maven Shared Components Issue Type: Task Reporter: Zhongming Hua -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8000) DefaultArtifact lacks constructors for version and optional
Zhongming Hua created MNG-8000: -- Summary: DefaultArtifact lacks constructors for version and optional Key: MNG-8000 URL: https://issues.apache.org/jira/browse/MNG-8000 Project: Maven Issue Type: Task Components: Core Affects Versions: 4.0.0-alpha-10 Reporter: Zhongming Hua -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7976) Investigate MNG-6127 IT instability
[ https://issues.apache.org/jira/browse/MNG-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804962#comment-17804962 ] Zhongming Hua commented on MNG-7976: [~cstamas] I can find the log from [https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/509/artifact/core-it-suite-logs-linux-jdk11.zip]. Let‘s wait for it to reappear.:D > Investigate MNG-6127 IT instability > --- > > Key: MNG-7976 > URL: https://issues.apache.org/jira/browse/MNG-7976 > Project: Maven > Issue Type: Task > Components: Core >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-11 > > > The MNG-6127 IT quite often fails, and passes when CI job rebuilt, seems > unstable. > Look into it why (lurking concurrency bug somewhere? or just the IT is > flakey?) and fix it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7976) Investigate MNG-6127 IT instability
[ https://issues.apache.org/jira/browse/MNG-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17801516#comment-17801516 ] Zhongming Hua commented on MNG-7976: [~cstamas] I can't reproduce the unstable 6127 IT in the local environment. With the debug log enabled, I will try to troubleshoot the problem through the debug log. https://github.com/apache/maven-integration-testing/pull/330 > Investigate MNG-6127 IT instability > --- > > Key: MNG-7976 > URL: https://issues.apache.org/jira/browse/MNG-7976 > Project: Maven > Issue Type: Task > Components: Core >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-11 > > > The MNG-6127 IT quite often fails, and passes when CI job rebuilt, seems > unstable. > Look into it why (lurking concurrency bug somewhere? or just the IT is > flakey?) and fix it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7976) Investigate MNG-6127 IT instability
[ https://issues.apache.org/jira/browse/MNG-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17801109#comment-17801109 ] Zhongming Hua commented on MNG-7976: [~cstamas] Are you referring to integration testing or IT? Which can provide failed information and links? > Investigate MNG-6127 IT instability > --- > > Key: MNG-7976 > URL: https://issues.apache.org/jira/browse/MNG-7976 > Project: Maven > Issue Type: Task > Components: Core >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-11 > > > The MNG-6127 IT quite often fails, and passes when CI job rebuilt, seems > unstable. > Look into it why (lurking concurrency bug somewhere? or just the IT is > flakey?) and fix it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7944) Execution default of goal org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2 out of bounds for length 2
[
https://issues.apache.org/jira/browse/MNG-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796515#comment-17796515
]
Zhongming Hua commented on MNG-7944:
[~khmarbaise]
I don't have permission to close it. Can you do it?
> Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2
> out of bounds for length 2
>
>
> Key: MNG-7944
> URL: https://issues.apache.org/jira/browse/MNG-7944
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-8
>Reporter: Filipe Roque
>Priority: Major
>
> It only affects apache-maven-4.0.0-alpha-8
> pom.xml
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> org.example
> mvn4-assembly-index
> 1.0-SNAPSHOT
>
> 17
> 17
> UTF-8
>
>
>
> org.ehcache
> ehcache
> 3.10.8
>
>
>
>
>
> org.apache.maven.plugins
> maven-assembly-plugin
> 3.6.0
>
>
>
> src/main/assembly/descriptor.xml
>
> false
>
>
>
> package
>
> single
>
>
>
>
>
>
> {code}
> descriptor.xml
> {code:java}
> http://maven.apache.org/ASSEMBLY/2.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.1.0
> http://maven.apache.org/xsd/assembly-2.1.0.xsd;>
> assembly
>
> dir
>
> false
> .
>
>
> /
> false
> runtime
>
>
>
> {code}
> {code:java}
> ❯ /opt/maven/apache-maven-4.0.0-alpha-8/bin/mvn -q package
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single (default) on
> project mvn4-assembly-index: Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2
> out of bounds for length 2 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the '-e'
> switch
> [ERROR] Re-run Maven using the '-X' switch to enable verbose output
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7944) Execution default of goal org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2 out of bounds for length 2
[
https://issues.apache.org/jira/browse/MNG-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795983#comment-17795983
]
Zhongming Hua commented on MNG-7944:
[~froque]
I reproduced your question with your samples in the 4.0.0-alpha-8 version, but
it's okay in 4.0.0-alpha-9-SNAPSHOT. Please wait for the 4.0.0-alpha-9 release.
> Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2
> out of bounds for length 2
>
>
> Key: MNG-7944
> URL: https://issues.apache.org/jira/browse/MNG-7944
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-8
>Reporter: Filipe Roque
>Priority: Major
>
> It only affects apache-maven-4.0.0-alpha-8
> pom.xml
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> org.example
> mvn4-assembly-index
> 1.0-SNAPSHOT
>
> 17
> 17
> UTF-8
>
>
>
> org.ehcache
> ehcache
> 3.10.8
>
>
>
>
>
> org.apache.maven.plugins
> maven-assembly-plugin
> 3.6.0
>
>
>
> src/main/assembly/descriptor.xml
>
> false
>
>
>
> package
>
> single
>
>
>
>
>
>
> {code}
> descriptor.xml
> {code:java}
> http://maven.apache.org/ASSEMBLY/2.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.1.0
> http://maven.apache.org/xsd/assembly-2.1.0.xsd;>
> assembly
>
> dir
>
> false
> .
>
>
> /
> false
> runtime
>
>
>
> {code}
> {code:java}
> ❯ /opt/maven/apache-maven-4.0.0-alpha-8/bin/mvn -q package
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single (default) on
> project mvn4-assembly-index: Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2
> out of bounds for length 2 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the '-e'
> switch
> [ERROR] Re-run Maven using the '-X' switch to enable verbose output
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7950) Support new version scheme selector in Maven
[ https://issues.apache.org/jira/browse/MNG-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794485#comment-17794485 ] Zhongming Hua commented on MNG-7950: Luckily, I haven't started yet.;) Otherwise, the work will be repeated. [~cstamas] > Support new version scheme selector in Maven > > > Key: MNG-7950 > URL: https://issues.apache.org/jira/browse/MNG-7950 > Project: Maven > Issue Type: Task > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-alpha-9, 4.0.0 > > > The generic version scheme is made into component, but it is not enough: > there should be an indirection and extension point to support multiple > schemes. > Resolver introduces MRESOLVER-446 for that. > There is one component in Maven maven-resolver-provider module that needs to > be adapted, and use selector instead of ctor passed in scheme. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7950) Support new version scheme selector in Maven
[ https://issues.apache.org/jira/browse/MNG-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794313#comment-17794313 ] Zhongming Hua commented on MNG-7950: It depends on the maven-resolver-api:2.0.0-alpha-4 release. I can try this task when maven-resolver-api:2.0.0-alpha-4 is released. [~cstamas] > Support new version scheme selector in Maven > > > Key: MNG-7950 > URL: https://issues.apache.org/jira/browse/MNG-7950 > Project: Maven > Issue Type: Task > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-alpha-9, 4.0.0 > > > The generic version scheme is made into component, but it is not enough: > there should be an indirection and extension point to support multiple > schemes. > Resolver introduces MRESOLVER-446 for that. > There is one component in Maven maven-resolver-provider module that needs to > be adapted, and use selector instead of ctor passed in scheme. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7944) Execution default of goal org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2 out of bounds for length 2
[
https://issues.apache.org/jira/browse/MNG-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17793236#comment-17793236
]
Zhongming Hua commented on MNG-7944:
[~froque]
I can't reproduce your question with your configuration. version 4.0.0-alpha-8
is ok, you can try it again.
> Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2
> out of bounds for length 2
>
>
> Key: MNG-7944
> URL: https://issues.apache.org/jira/browse/MNG-7944
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-8
>Reporter: Filipe Roque
>Priority: Major
>
> It only affects apache-maven-4.0.0-alpha-8
> pom.xml
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> org.example
> mvn4-assembly-index
> 1.0-SNAPSHOT
>
> 17
> 17
> UTF-8
>
>
>
> org.ehcache
> ehcache
> 3.10.8
>
>
>
>
>
> org.apache.maven.plugins
> maven-assembly-plugin
> 3.6.0
>
>
>
> src/main/assembly/descriptor.xml
>
> false
>
>
>
> package
>
> single
>
>
>
>
>
>
> {code}
> descriptor.xml
> {code:java}
> http://maven.apache.org/ASSEMBLY/2.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.1.0
> http://maven.apache.org/xsd/assembly-2.1.0.xsd;>
> assembly
>
> dir
>
> false
> .
>
>
> /
> false
> runtime
>
>
>
> {code}
> {code:java}
> ❯ /opt/maven/apache-maven-4.0.0-alpha-8/bin/mvn -q package
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single (default) on
> project mvn4-assembly-index: Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2
> out of bounds for length 2 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the '-e'
> switch
> [ERROR] Re-run Maven using the '-X' switch to enable verbose output
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[
https://issues.apache.org/jira/browse/MNG-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787841#comment-17787841
]
Zhongming Hua commented on MNG-7920:
[~khmarbaise]
I have revised the PR again and fixed several problems you raised, please
review it again.
> Usage of packaging BOM fails in maven-install-plugin
>
>
> Key: MNG-7920
> URL: https://issues.apache.org/jira/browse/MNG-7920
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> Using to use the {{bom}} packaging in a module it will fail with:
> {code}
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project bom: The packaging plugin for this project did not assign a main
> file to the project but it has attachments. Change packaging to 'pom'. ->
> [Help 1]
> {code}
> The bom module looks like this:
> {code:xml}
>xmlns="http://maven.apache.org/POM/4.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
> http://maven.apache.org/maven-v4_1_0.xsd;>
> 4.1.0
>
> maven4
> bom-example
>
> bom
> bom
>
>
>
> ...maven4
> mod-1
>
>
> maven4
> mod-2
>
>
>
>
> {code}
> I would assume that I need to upgrade the maven-install-plugin which is
> capable of handling that...but I assumed that this conversion is done by core?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[
https://issues.apache.org/jira/browse/MNG-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787491#comment-17787491
]
Zhongming Hua edited comment on MNG-7920 at 11/18/23 1:50 PM:
--
Thank you for testing and replying to my PR. I have some questions about two
issues you mentioned:
# I found that neither the *pom* nor the *bom* would automatically parse and
include the version. Does that mean *pom* has the same problem?
# At present, the pom will contain all bom's resolved which are from the
module parent. But we expect that the bom does not contain all bom's resolved
which are from the module parent, right?
[~khmarbaise]
was (Author: crazyhzm):
Thank you for testing and replying to my PR. I have some questions about two
issues you mentioned:
# I found that neither the *pom* nor the *bom* would automatically parse and
include the version.
# At present, the pom will contain all bom's resolved which are from the
module parent. But we expect that the bom does not contain all bom's resolved
which are from the module parent, right?
[~khmarbaise]
> Usage of packaging BOM fails in maven-install-plugin
>
>
> Key: MNG-7920
> URL: https://issues.apache.org/jira/browse/MNG-7920
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> Using to use the {{bom}} packaging in a module it will fail with:
> {code}
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project bom: The packaging plugin for this project did not assign a main
> file to the project but it has attachments. Change packaging to 'pom'. ->
> [Help 1]
> {code}
> The bom module looks like this:
> {code:xml}
>xmlns="http://maven.apache.org/POM/4.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
> http://maven.apache.org/maven-v4_1_0.xsd;>
> 4.1.0
>
> maven4
> bom-example
>
> bom
> bom
>
>
>
> ...maven4
> mod-1
>
>
> maven4
> mod-2
>
>
>
>
> {code}
> I would assume that I need to upgrade the maven-install-plugin which is
> capable of handling that...but I assumed that this conversion is done by core?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[
https://issues.apache.org/jira/browse/MNG-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787491#comment-17787491
]
Zhongming Hua commented on MNG-7920:
Thank you for testing and replying to my PR. I have some questions about two
issues you mentioned:
# I found that neither the *pom* nor the *bom* would automatically parse and
include the version.
# At present, the pom will contain all bom's resolved which are from the
module parent. But we expect that the bom does not contain all bom's resolved
which are from the module parent, right?
[~khmarbaise]
> Usage of packaging BOM fails in maven-install-plugin
>
>
> Key: MNG-7920
> URL: https://issues.apache.org/jira/browse/MNG-7920
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> Using to use the {{bom}} packaging in a module it will fail with:
> {code}
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project bom: The packaging plugin for this project did not assign a main
> file to the project but it has attachments. Change packaging to 'pom'. ->
> [Help 1]
> {code}
> The bom module looks like this:
> {code:xml}
>xmlns="http://maven.apache.org/POM/4.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
> http://maven.apache.org/maven-v4_1_0.xsd;>
> 4.1.0
>
> maven4
> bom-example
>
> bom
> bom
>
>
>
> ...maven4
> mod-1
>
>
> maven4
> mod-2
>
>
>
>
> {code}
> I would assume that I need to upgrade the maven-install-plugin which is
> capable of handling that...but I assumed that this conversion is done by core?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[
https://issues.apache.org/jira/browse/MNG-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785829#comment-17785829
]
Zhongming Hua commented on MNG-7920:
I will fix the problem.
[~sjaranowski] [~khmarbaise]
> Usage of packaging BOM fails in maven-install-plugin
>
>
> Key: MNG-7920
> URL: https://issues.apache.org/jira/browse/MNG-7920
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> Using to use the `bom` packaging in a module it will fail with:
> {code}
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project bom: The packaging plugin for this project did not assign a main
> file to the project but it has attachments. Change packaging to 'pom'. ->
> [Help 1]
> {code}
> The bom module looks like this:
> {code:xml}
>xmlns="http://maven.apache.org/POM/4.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
> http://maven.apache.org/maven-v4_1_0.xsd;>
> 4.1.0
>
> maven4
> bom-example
>
> bom
> bom
>
>
>
> ...maven4
> mod-1
>
>
> maven4
> mod-2
>
>
>
>
> {code}
> I would assume that I need to upgrade the maven-install-plugin which is
> capable of handling that...but I assumed that this conversion is done by core?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[
https://issues.apache.org/jira/browse/MNG-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785827#comment-17785827
]
Zhongming Hua commented on MNG-7920:
[~khmarbaise] [~sjaranowski]
> Usage of packaging BOM fails in maven-install-plugin
>
>
> Key: MNG-7920
> URL: https://issues.apache.org/jira/browse/MNG-7920
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> Using to use the `bom` packaging in a module it will fail with:
> {code}
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project bom: The packaging plugin for this project did not assign a main
> file to the project but it has attachments. Change packaging to 'pom'. ->
> [Help 1]
> {code}
> The bom module looks like this:
> {code:xml}
>xmlns="http://maven.apache.org/POM/4.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
> http://maven.apache.org/maven-v4_1_0.xsd;>
> 4.1.0
>
> maven4
> bom-example
>
> bom
> bom
>
>
>
> ...maven4
> mod-1
>
>
> maven4
> mod-2
>
>
>
>
> {code}
> I would assume that I need to upgrade the maven-install-plugin which is
> capable of handling that...but I assumed that this conversion is done by core?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[ https://issues.apache.org/jira/browse/MNG-7920 ]
Zhongming Hua deleted comment on MNG-7920:
was (Author: crazyhzm):
[~khmarbaise] [~sjaranowski]
> Usage of packaging BOM fails in maven-install-plugin
>
>
> Key: MNG-7920
> URL: https://issues.apache.org/jira/browse/MNG-7920
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> Using to use the `bom` packaging in a module it will fail with:
> {code}
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project bom: The packaging plugin for this project did not assign a main
> file to the project but it has attachments. Change packaging to 'pom'. ->
> [Help 1]
> {code}
> The bom module looks like this:
> {code:xml}
>xmlns="http://maven.apache.org/POM/4.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
> http://maven.apache.org/maven-v4_1_0.xsd;>
> 4.1.0
>
> maven4
> bom-example
>
> bom
> bom
>
>
>
> ...maven4
> mod-1
>
>
> maven4
> mod-2
>
>
>
>
> {code}
> I would assume that I need to upgrade the maven-install-plugin which is
> capable of handling that...but I assumed that this conversion is done by core?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7775) toString method in VersionRange is undocumented and surprising
[ https://issues.apache.org/jira/browse/MNG-7775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784049#comment-17784049 ] Zhongming Hua commented on MNG-7775: Can I optimize the Javadoc of VersionRange#asString to fix this?[~elharo] > toString method in VersionRange is undocumented and surprising > -- > > Key: MNG-7775 > URL: https://issues.apache.org/jira/browse/MNG-7775 > Project: Maven > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Minor > > It sometimes returns a single version rather than the full range, though the > only way to see this is by reading the code. I've seen this create confusing > end user messages in enforcer rules. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MNG-7883) Also print groupId and version in the Reactor Build Order
[
https://issues.apache.org/jira/browse/MNG-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766223#comment-17766223
]
Zhongming Hua edited comment on MNG-7883 at 9/18/23 6:29 AM:
-
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] my-group:my-parent:1.0.0-SNAPSHOT [pom]
[INFO] my-group:my-lib:1.0.0-SNAPSHOT [jar]
[INFO] my-group:my-app:1.0.4 [jar]
was (Author: crazyhzm):
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] my-group:my-parent:1.0.0-SNAPSHOT [pom]
[INFO] my-group:my-lib:1.0.0-SNAPSHOT [jar]
[INFO] my-group:my-app:1.0.4 [jar]
> Also print groupId and version in the Reactor Build Order
> -
>
> Key: MNG-7883
> URL: https://issues.apache.org/jira/browse/MNG-7883
> Project: Maven
> Issue Type: Improvement
> Components: Reactor and Workspace
>Reporter: Reto Hoehener
>Priority: Trivial
>
> This would be useful information when debugging a build process:
> {code:java}
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] my-groupmy-parent1.0.0-SNAPSHOT
> [pom]
> [INFO] my-groupmy-lib 1.0.0-SNAPSHOT
> [jar]
> [INFO] my-groupmy-app 1.0.4
> [jar] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7883) Also print groupId and version in the Reactor Build Order
[
https://issues.apache.org/jira/browse/MNG-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766224#comment-17766224
]
Zhongming Hua edited comment on MNG-7883 at 9/18/23 6:26 AM:
-
I think the *groupId:name:version* structure is better.
was (Author: crazyhzm):
I think the *{groupId}:{name}:{version}* structure is better.
> Also print groupId and version in the Reactor Build Order
> -
>
> Key: MNG-7883
> URL: https://issues.apache.org/jira/browse/MNG-7883
> Project: Maven
> Issue Type: Improvement
> Components: Reactor and Workspace
>Reporter: Reto Hoehener
>Priority: Trivial
>
> This would be useful information when debugging a build process:
> {code:java}
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] my-groupmy-parent1.0.0-SNAPSHOT
> [pom]
> [INFO] my-groupmy-lib 1.0.0-SNAPSHOT
> [jar]
> [INFO] my-groupmy-app 1.0.4
> [jar] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7883) Also print groupId and version in the Reactor Build Order
[
https://issues.apache.org/jira/browse/MNG-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766224#comment-17766224
]
Zhongming Hua edited comment on MNG-7883 at 9/18/23 6:25 AM:
-
I think the *{groupId}:{name}:{version}* structure is better.
was (Author: crazyhzm):
I think the *{groupId}:\{name}:\{version}* structure is better.
> Also print groupId and version in the Reactor Build Order
> -
>
> Key: MNG-7883
> URL: https://issues.apache.org/jira/browse/MNG-7883
> Project: Maven
> Issue Type: Improvement
> Components: Reactor and Workspace
>Reporter: Reto Hoehener
>Priority: Trivial
>
> This would be useful information when debugging a build process:
> {code:java}
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] my-groupmy-parent1.0.0-SNAPSHOT
> [pom]
> [INFO] my-groupmy-lib 1.0.0-SNAPSHOT
> [jar]
> [INFO] my-groupmy-app 1.0.4
> [jar] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7883) Also print groupId and version in the Reactor Build Order
[
https://issues.apache.org/jira/browse/MNG-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766224#comment-17766224
]
Zhongming Hua commented on MNG-7883:
I think the *{groupId}:\{name}:\{version}* structure is better.
> Also print groupId and version in the Reactor Build Order
> -
>
> Key: MNG-7883
> URL: https://issues.apache.org/jira/browse/MNG-7883
> Project: Maven
> Issue Type: Improvement
> Components: Reactor and Workspace
>Reporter: Reto Hoehener
>Priority: Trivial
>
> This would be useful information when debugging a build process:
> {code:java}
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] my-groupmy-parent1.0.0-SNAPSHOT
> [pom]
> [INFO] my-groupmy-lib 1.0.0-SNAPSHOT
> [jar]
> [INFO] my-groupmy-app 1.0.4
> [jar] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7883) Also print groupId and version in the Reactor Build Order
[
https://issues.apache.org/jira/browse/MNG-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766224#comment-17766224
]
Zhongming Hua edited comment on MNG-7883 at 9/18/23 6:25 AM:
-
I think the *{groupId}:\{name}:\{version}* structure is better.
was (Author: crazyhzm):
I think the *{groupId}:\{name}:\{version}* structure is better.
> Also print groupId and version in the Reactor Build Order
> -
>
> Key: MNG-7883
> URL: https://issues.apache.org/jira/browse/MNG-7883
> Project: Maven
> Issue Type: Improvement
> Components: Reactor and Workspace
>Reporter: Reto Hoehener
>Priority: Trivial
>
> This would be useful information when debugging a build process:
> {code:java}
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] my-groupmy-parent1.0.0-SNAPSHOT
> [pom]
> [INFO] my-groupmy-lib 1.0.0-SNAPSHOT
> [jar]
> [INFO] my-groupmy-app 1.0.4
> [jar] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7883) Also print groupId and version in the Reactor Build Order
[
https://issues.apache.org/jira/browse/MNG-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766223#comment-17766223
]
Zhongming Hua edited comment on MNG-7883 at 9/18/23 6:24 AM:
-
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] my-group:my-parent:1.0.0-SNAPSHOT [pom]
[INFO] my-group:my-lib:1.0.0-SNAPSHOT [jar]
[INFO] my-group:my-app:1.0.4 [jar]
was (Author: crazyhzm):
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] my-group:my-parent:1.0.0-SNAPSHOT [pom]
[INFO] my-group:my-lib:1.0.0-SNAPSHOT [jar]
[INFO] my-group:my-app:1.0.4 [jar]
I think the *{groupId}:\{name}:\{version}* structure is better.
> Also print groupId and version in the Reactor Build Order
> -
>
> Key: MNG-7883
> URL: https://issues.apache.org/jira/browse/MNG-7883
> Project: Maven
> Issue Type: Improvement
> Components: Reactor and Workspace
>Reporter: Reto Hoehener
>Priority: Trivial
>
> This would be useful information when debugging a build process:
> {code:java}
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] my-groupmy-parent1.0.0-SNAPSHOT
> [pom]
> [INFO] my-groupmy-lib 1.0.0-SNAPSHOT
> [jar]
> [INFO] my-groupmy-app 1.0.4
> [jar] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7883) Also print groupId and version in the Reactor Build Order
[
https://issues.apache.org/jira/browse/MNG-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766223#comment-17766223
]
Zhongming Hua commented on MNG-7883:
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] my-group:my-parent:1.0.0-SNAPSHOT [pom]
[INFO] my-group:my-lib:1.0.0-SNAPSHOT [jar]
[INFO] my-group:my-app:1.0.4 [jar]
I think the *{groupId}:\{name}:\{version}* structure is better.
> Also print groupId and version in the Reactor Build Order
> -
>
> Key: MNG-7883
> URL: https://issues.apache.org/jira/browse/MNG-7883
> Project: Maven
> Issue Type: Improvement
> Components: Reactor and Workspace
>Reporter: Reto Hoehener
>Priority: Trivial
>
> This would be useful information when debugging a build process:
> {code:java}
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] my-groupmy-parent1.0.0-SNAPSHOT
> [pom]
> [INFO] my-groupmy-lib 1.0.0-SNAPSHOT
> [jar]
> [INFO] my-groupmy-app 1.0.4
> [jar] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7820) Remove dependency on plexus-utils
[ https://issues.apache.org/jira/browse/MNG-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17738346#comment-17738346 ] Zhongming Hua commented on MNG-7820: I will wait for this PR to be merged and then complete the issue based on it. > Remove dependency on plexus-utils > - > > Key: MNG-7820 > URL: https://issues.apache.org/jira/browse/MNG-7820 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-alpha-8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7820) Remove dependency on plexus-utils
[ https://issues.apache.org/jira/browse/MNG-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737423#comment-17737423 ] Zhongming Hua commented on MNG-7820: maven-compat and maven-embedder cannot fully remove the dependency on plexus-utils because the *Xpp3Reader* generated by modello relies on the ReaderFactory, I think we may need to replace *ReaderFactory.newXmlReader (in)* with *new XmlStreamReader (in)* in modello-maven-plugin > Remove dependency on plexus-utils > - > > Key: MNG-7820 > URL: https://issues.apache.org/jira/browse/MNG-7820 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-alpha-8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7820) Remove dependency on plexus-utils
[ https://issues.apache.org/jira/browse/MNG-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737120#comment-17737120 ] Zhongming Hua commented on MNG-7820: [~gnodet] I checked it and found that the introspection package also needed to be copied to maven-core. > Remove dependency on plexus-utils > - > > Key: MNG-7820 > URL: https://issues.apache.org/jira/browse/MNG-7820 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-alpha-8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7820) Remove dependency on plexus-utils
[ https://issues.apache.org/jira/browse/MNG-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736975#comment-17736975 ] Zhongming Hua commented on MNG-7820: [~gnodet] StringUtils can no longer use common components such as Apache commons? > Remove dependency on plexus-utils > - > > Key: MNG-7820 > URL: https://issues.apache.org/jira/browse/MNG-7820 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-alpha-8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7820) Remove dependency on plexus-utils
[ https://issues.apache.org/jira/browse/MNG-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua updated MNG-7820: --- Attachment: (was: image-2023-06-25-17-40-05-430.png) > Remove dependency on plexus-utils > - > > Key: MNG-7820 > URL: https://issues.apache.org/jira/browse/MNG-7820 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-alpha-8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7820) Remove dependency on plexus-utils
[ https://issues.apache.org/jira/browse/MNG-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736848#comment-17736848 ] Zhongming Hua commented on MNG-7820: [~gnodet] I can try to do this. > Remove dependency on plexus-utils > - > > Key: MNG-7820 > URL: https://issues.apache.org/jira/browse/MNG-7820 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-alpha-8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7820) Remove dependency on plexus-utils
[ https://issues.apache.org/jira/browse/MNG-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongming Hua updated MNG-7820: --- Attachment: image-2023-06-25-17-40-05-430.png > Remove dependency on plexus-utils > - > > Key: MNG-7820 > URL: https://issues.apache.org/jira/browse/MNG-7820 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-alpha-8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7585) Get rid if duplicate utility classes
[
https://issues.apache.org/jira/browse/MNG-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17720185#comment-17720185
]
Zhongming Hua commented on MNG-7585:
The ability of these classes is the common ability, and whether consider
providing a maven-common module.
[~gnodet]
> Get rid if duplicate utility classes
>
>
> Key: MNG-7585
> URL: https://issues.apache.org/jira/browse/MNG-7585
> Project: Maven
> Issue Type: Task
>Affects Versions: 4.0.0-alpha-2
>Reporter: Guillaume Nodet
>Priority: Major
>
> We currently have 3 copies of {{WrapperList}} and {{WrapperProperties}} and 4
> copies of {{{}ImmutableCollections{}}}.
> It would be nice to find a way to keep a single copy of those without adding
> a dependency on some utility module, especially for the
> {{ImmutableCollections}} which are non public classes inside the v4 api.
>
> One possibility may be to use maven-shade-plugin to include a copy of the
> needed classes as non public classes inside the needed package... ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7777) Upgrade Guice to 6
[ https://issues.apache.org/jira/browse/MNG-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719893#comment-17719893 ] Zhongming Hua edited comment on MNG- at 5/5/23 2:45 PM: [~slachiewicz] I found Guice 6.0.0 doesn’t publish, Only version 6.0.0-rc2 is available. Do we need to wait for the official release of version 6.0.0? was (Author: crazyhzm): @ I found Guice 6.0.0 doesn’t publish, Only version 6.0.0-rc2 is available. Do we need to wait for the official release of version 6.0.0? > Upgrade Guice to 6 > -- > > Key: MNG- > URL: https://issues.apache.org/jira/browse/MNG- > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Major > > Add support to jakarta.inject -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7777) Upgrade Guice to 6
[ https://issues.apache.org/jira/browse/MNG-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719893#comment-17719893 ] Zhongming Hua commented on MNG-: @ I found Guice 6.0.0 doesn’t publish, Only version 6.0.0-rc2 is available. Do we need to wait for the official release of version 6.0.0? > Upgrade Guice to 6 > -- > > Key: MNG- > URL: https://issues.apache.org/jira/browse/MNG- > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Major > > Add support to jakarta.inject -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MNG-7714) sp < final
[
https://issues.apache.org/jira/browse/MNG-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718772#comment-17718772
]
Zhongming Hua edited comment on MNG-7714 at 5/3/23 2:17 AM:
[~elharo]
Please review this PR: [https://github.com/apache/maven/pull/1099]
was (Author: crazyhzm):
[~elharo]
Please review the PR: https://github.com/apache/maven/pull/1099
> sp < final
> --
>
> Key: MNG-7714
> URL: https://issues.apache.org/jira/browse/MNG-7714
> Project: Maven
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Major
> Fix For: 4.0.0-alpha-6
>
>
> Ported from a comment on https://issues.apache.org/jira/browse/MNG-7701
> The claim is that sp < final, which if true is incorrect according to spec.
> It is easy to demonstrate that this is not fixed and also not in line with
> the spec, with just this one important example (yes this does break for us):
> $ jbang org.apache.maven:maven-artifact:3.8.6 1.0.final-redhat-0001
> 1.0.sp1-redhat-0001
> Display parameters as parsed by Maven (in canonical form and as a list of
> tokens) and comparison result:
> 1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
>1.0.final-redhat-0001 < 1.0.sp1-redhat-0001
> 2. 1.0.sp1-redhat-0001 -> 1.0.sp-1-redhat-1; tokens: [1, 0, sp, [1, [redhat,
> [1
> versus
> $ jbang org.apache.maven:maven-artifact:3.8.7 1.0.final-redhat-0001
> 1.0.sp1-redhat-0001
> Display parameters as parsed by Maven (in canonical form and as a list of
> tokens) and comparison result:
> 1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
>1.0.final-redhat-0001 > 1.0.sp1-redhat-0001
> 2. 1.0.sp1-redhat-0001 -> 1-sp-1-redhat-1; tokens: [1, [sp, [1, [redhat,
> [1]
> As you can see, our `sp` release is now ordered after our `final` release
> despite this clear text in the "spec":
> Non-numeric tokens ("qualifiers") have the alphabetical order, except for
> the following tokens which come first in this order: "alpha" < "beta" <
> "milestone" < "rc" = "cr" < "snapshot" < "" = "final" = "ga" < "sp"
> It's clear that this tokenization isn't really correct by any reasonable
> measurement, and breaking large amounts of (our) existing artifacts in the
> wild is definitely not OK.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7714) sp < final
[
https://issues.apache.org/jira/browse/MNG-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718772#comment-17718772
]
Zhongming Hua commented on MNG-7714:
[~elharo]
Please review the PR: https://github.com/apache/maven/pull/1099
> sp < final
> --
>
> Key: MNG-7714
> URL: https://issues.apache.org/jira/browse/MNG-7714
> Project: Maven
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Major
> Fix For: 4.0.0-alpha-6
>
>
> Ported from a comment on https://issues.apache.org/jira/browse/MNG-7701
> The claim is that sp < final, which if true is incorrect according to spec.
> It is easy to demonstrate that this is not fixed and also not in line with
> the spec, with just this one important example (yes this does break for us):
> $ jbang org.apache.maven:maven-artifact:3.8.6 1.0.final-redhat-0001
> 1.0.sp1-redhat-0001
> Display parameters as parsed by Maven (in canonical form and as a list of
> tokens) and comparison result:
> 1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
>1.0.final-redhat-0001 < 1.0.sp1-redhat-0001
> 2. 1.0.sp1-redhat-0001 -> 1.0.sp-1-redhat-1; tokens: [1, 0, sp, [1, [redhat,
> [1
> versus
> $ jbang org.apache.maven:maven-artifact:3.8.7 1.0.final-redhat-0001
> 1.0.sp1-redhat-0001
> Display parameters as parsed by Maven (in canonical form and as a list of
> tokens) and comparison result:
> 1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
>1.0.final-redhat-0001 > 1.0.sp1-redhat-0001
> 2. 1.0.sp1-redhat-0001 -> 1-sp-1-redhat-1; tokens: [1, [sp, [1, [redhat,
> [1]
> As you can see, our `sp` release is now ordered after our `final` release
> despite this clear text in the "spec":
> Non-numeric tokens ("qualifiers") have the alphabetical order, except for
> the following tokens which come first in this order: "alpha" < "beta" <
> "milestone" < "rc" = "cr" < "snapshot" < "" = "final" = "ga" < "sp"
> It's clear that this tokenization isn't really correct by any reasonable
> measurement, and breaking large amounts of (our) existing artifacts in the
> wild is definitely not OK.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7714) sp < final
[
https://issues.apache.org/jira/browse/MNG-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongming Hua updated MNG-7714:
---
Attachment: (was: image-2023-05-03-10-16-04-679.png)
> sp < final
> --
>
> Key: MNG-7714
> URL: https://issues.apache.org/jira/browse/MNG-7714
> Project: Maven
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Major
> Fix For: 4.0.0-alpha-6
>
>
> Ported from a comment on https://issues.apache.org/jira/browse/MNG-7701
> The claim is that sp < final, which if true is incorrect according to spec.
> It is easy to demonstrate that this is not fixed and also not in line with
> the spec, with just this one important example (yes this does break for us):
> $ jbang org.apache.maven:maven-artifact:3.8.6 1.0.final-redhat-0001
> 1.0.sp1-redhat-0001
> Display parameters as parsed by Maven (in canonical form and as a list of
> tokens) and comparison result:
> 1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
>1.0.final-redhat-0001 < 1.0.sp1-redhat-0001
> 2. 1.0.sp1-redhat-0001 -> 1.0.sp-1-redhat-1; tokens: [1, 0, sp, [1, [redhat,
> [1
> versus
> $ jbang org.apache.maven:maven-artifact:3.8.7 1.0.final-redhat-0001
> 1.0.sp1-redhat-0001
> Display parameters as parsed by Maven (in canonical form and as a list of
> tokens) and comparison result:
> 1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
>1.0.final-redhat-0001 > 1.0.sp1-redhat-0001
> 2. 1.0.sp1-redhat-0001 -> 1-sp-1-redhat-1; tokens: [1, [sp, [1, [redhat,
> [1]
> As you can see, our `sp` release is now ordered after our `final` release
> despite this clear text in the "spec":
> Non-numeric tokens ("qualifiers") have the alphabetical order, except for
> the following tokens which come first in this order: "alpha" < "beta" <
> "milestone" < "rc" = "cr" < "snapshot" < "" = "final" = "ga" < "sp"
> It's clear that this tokenization isn't really correct by any reasonable
> measurement, and breaking large amounts of (our) existing artifacts in the
> wild is definitely not OK.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7714) sp < final
[
https://issues.apache.org/jira/browse/MNG-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongming Hua updated MNG-7714:
---
Attachment: image-2023-05-03-10-16-04-679.png
> sp < final
> --
>
> Key: MNG-7714
> URL: https://issues.apache.org/jira/browse/MNG-7714
> Project: Maven
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Major
> Fix For: 4.0.0-alpha-6
>
>
> Ported from a comment on https://issues.apache.org/jira/browse/MNG-7701
> The claim is that sp < final, which if true is incorrect according to spec.
> It is easy to demonstrate that this is not fixed and also not in line with
> the spec, with just this one important example (yes this does break for us):
> $ jbang org.apache.maven:maven-artifact:3.8.6 1.0.final-redhat-0001
> 1.0.sp1-redhat-0001
> Display parameters as parsed by Maven (in canonical form and as a list of
> tokens) and comparison result:
> 1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
>1.0.final-redhat-0001 < 1.0.sp1-redhat-0001
> 2. 1.0.sp1-redhat-0001 -> 1.0.sp-1-redhat-1; tokens: [1, 0, sp, [1, [redhat,
> [1
> versus
> $ jbang org.apache.maven:maven-artifact:3.8.7 1.0.final-redhat-0001
> 1.0.sp1-redhat-0001
> Display parameters as parsed by Maven (in canonical form and as a list of
> tokens) and comparison result:
> 1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
>1.0.final-redhat-0001 > 1.0.sp1-redhat-0001
> 2. 1.0.sp1-redhat-0001 -> 1-sp-1-redhat-1; tokens: [1, [sp, [1, [redhat,
> [1]
> As you can see, our `sp` release is now ordered after our `final` release
> despite this clear text in the "spec":
> Non-numeric tokens ("qualifiers") have the alphabetical order, except for
> the following tokens which come first in this order: "alpha" < "beta" <
> "milestone" < "rc" = "cr" < "snapshot" < "" = "final" = "ga" < "sp"
> It's clear that this tokenization isn't really correct by any reasonable
> measurement, and breaking large amounts of (our) existing artifacts in the
> wild is definitely not OK.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7714) sp < final
[
https://issues.apache.org/jira/browse/MNG-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717556#comment-17717556
]
Zhongming Hua commented on MNG-7714:
[~elharo]
I find that this problem is related to the following logic. Because treat *.x*
as {*}-x{*}, 1.0.sp is resolved as [1,[sp]], not [1,sp].
{code:java}
// 1.0.0.X1 < 1.0.0-X2
// treat .X as -X for any string qualifier X
if (!list.isEmpty()) {
list.add(list = new ListItem());
stack.push(list);
} {code}
> sp < final
> --
>
> Key: MNG-7714
> URL: https://issues.apache.org/jira/browse/MNG-7714
> Project: Maven
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Major
> Fix For: 4.0.0-alpha-6
>
>
> Ported from a comment on https://issues.apache.org/jira/browse/MNG-7701
> The claim is that sp < final, which if true is incorrect according to spec.
> It is easy to demonstrate that this is not fixed and also not in line with
> the spec, with just this one important example (yes this does break for us):
> $ jbang org.apache.maven:maven-artifact:3.8.6 1.0.final-redhat-0001
> 1.0.sp1-redhat-0001
> Display parameters as parsed by Maven (in canonical form and as a list of
> tokens) and comparison result:
> 1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
>1.0.final-redhat-0001 < 1.0.sp1-redhat-0001
> 2. 1.0.sp1-redhat-0001 -> 1.0.sp-1-redhat-1; tokens: [1, 0, sp, [1, [redhat,
> [1
> versus
> $ jbang org.apache.maven:maven-artifact:3.8.7 1.0.final-redhat-0001
> 1.0.sp1-redhat-0001
> Display parameters as parsed by Maven (in canonical form and as a list of
> tokens) and comparison result:
> 1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
>1.0.final-redhat-0001 > 1.0.sp1-redhat-0001
> 2. 1.0.sp1-redhat-0001 -> 1-sp-1-redhat-1; tokens: [1, [sp, [1, [redhat,
> [1]
> As you can see, our `sp` release is now ordered after our `final` release
> despite this clear text in the "spec":
> Non-numeric tokens ("qualifiers") have the alphabetical order, except for
> the following tokens which come first in this order: "alpha" < "beta" <
> "milestone" < "rc" = "cr" < "snapshot" < "" = "final" = "ga" < "sp"
> It's clear that this tokenization isn't really correct by any reasonable
> measurement, and breaking large amounts of (our) existing artifacts in the
> wild is definitely not OK.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7639) Prepare a unit test for DefaultRepositorySystemSessionFactory#newRepositorySession
[
https://issues.apache.org/jira/browse/MNG-7639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716955#comment-17716955
]
Zhongming Hua commented on MNG-7639:
[~sjaranowski]
I will finish this task in the future, please assign it to me.
> Prepare a unit test for
> DefaultRepositorySystemSessionFactory#newRepositorySession
> --
>
> Key: MNG-7639
> URL: https://issues.apache.org/jira/browse/MNG-7639
> Project: Maven
> Issue Type: Task
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> {{DefaultRepositorySystemSessionFactory#newRepositorySession}} has many
> decision branches, most of them are not covered by IT tests.
> We can write a unit test to try cover it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7755) If a plugin is an extension, the managed version is ignored
[
https://issues.apache.org/jira/browse/MNG-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716588#comment-17716588
]
Zhongming Hua commented on MNG-7755:
[~laeubi]
You also have the option to close the issue and reopen it later when the issue
is reproduced.
> If a plugin is an extension, the managed version is ignored
> ---
>
> Key: MNG-7755
> URL: https://issues.apache.org/jira/browse/MNG-7755
> Project: Maven
> Issue Type: Bug
>Reporter: Christoph Läubrich
>Priority: Major
> Labels: invalid
> Attachments: testme.zip
>
>
> I have the following in a child pom:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> true
>
>
>
> {code}
> and in the parent:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
>
>
> {code}
> This gives an warning (and alter an error):
> [WARNING] 'build.plugins.plugin.version' for
> org.eclipse.tycho:tycho-bnd-plugin is missing.
> If I write directly in the child
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> it works ... it seems to be triggered by the true
> tag here that it then do not look at ate managed version...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7755) If a plugin is an extension, the managed version is ignored
[
https://issues.apache.org/jira/browse/MNG-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716552#comment-17716552
]
Zhongming Hua edited comment on MNG-7755 at 4/26/23 6:40 AM:
-
[~laeubi]
Under version 3.8.8, I tried to reproduce the problem according to your new
description, but there is still no WARNING message.
was (Author: crazyhzm):
[~laeubi]
Under version 3.8.8, I reproduced the problem according to your new
description, but there is still no WARNING message.
> If a plugin is an extension, the managed version is ignored
> ---
>
> Key: MNG-7755
> URL: https://issues.apache.org/jira/browse/MNG-7755
> Project: Maven
> Issue Type: Bug
>Reporter: Christoph Läubrich
>Priority: Major
>
> I have the following in a child pom:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> true
>
>
>
> {code}
> and in the parent:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
>
>
> {code}
> This gives an warning (and alter an error):
> [WARNING] 'build.plugins.plugin.version' for
> org.eclipse.tycho:tycho-bnd-plugin is missing.
> If I write directly in the child
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> it works ... it seems to be triggered by the true
> tag here that it then do not look at ate managed version...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7755) If a plugin is an extension, the managed version is ignored
[
https://issues.apache.org/jira/browse/MNG-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716552#comment-17716552
]
Zhongming Hua commented on MNG-7755:
[~laeubi]
Under version 3.8.8, I reproduced the problem according to your new
description, but there is still no WARNING message.
> If a plugin is an extension, the managed version is ignored
> ---
>
> Key: MNG-7755
> URL: https://issues.apache.org/jira/browse/MNG-7755
> Project: Maven
> Issue Type: Bug
>Reporter: Christoph Läubrich
>Priority: Major
>
> I have the following in a child pom:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> true
>
>
>
> {code}
> and in the parent:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
>
>
> {code}
> This gives an warning (and alter an error):
> [WARNING] 'build.plugins.plugin.version' for
> org.eclipse.tycho:tycho-bnd-plugin is missing.
> If I write directly in the child
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> it works ... it seems to be triggered by the true
> tag here that it then do not look at ate managed version...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7755) If a plugin is an extension, the managed version is ignored
[
https://issues.apache.org/jira/browse/MNG-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongming Hua updated MNG-7755:
---
Attachment: (was: image-2023-04-26-14-26-42-815.png)
> If a plugin is an extension, the managed version is ignored
> ---
>
> Key: MNG-7755
> URL: https://issues.apache.org/jira/browse/MNG-7755
> Project: Maven
> Issue Type: Bug
>Reporter: Christoph Läubrich
>Priority: Major
>
> I have the following in a child pom:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> true
>
>
>
> {code}
> and in the parent:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
>
>
> {code}
> This gives an warning (and alter an error):
> [WARNING] 'build.plugins.plugin.version' for
> org.eclipse.tycho:tycho-bnd-plugin is missing.
> If I write directly in the child
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> it works ... it seems to be triggered by the true
> tag here that it then do not look at ate managed version...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7755) If a plugin is an extension, the managed version is ignored
[
https://issues.apache.org/jira/browse/MNG-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongming Hua updated MNG-7755:
---
Attachment: image-2023-04-26-14-26-42-815.png
> If a plugin is an extension, the managed version is ignored
> ---
>
> Key: MNG-7755
> URL: https://issues.apache.org/jira/browse/MNG-7755
> Project: Maven
> Issue Type: Bug
>Reporter: Christoph Läubrich
>Priority: Major
>
> I have the following in a child pom:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> true
>
>
>
> {code}
> and in the parent:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
>
>
> {code}
> This gives an warning (and alter an error):
> [WARNING] 'build.plugins.plugin.version' for
> org.eclipse.tycho:tycho-bnd-plugin is missing.
> If I write directly in the child
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> it works ... it seems to be triggered by the true
> tag here that it then do not look at ate managed version...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7755) If a plugin is an extension, the managed version is ignored
[
https://issues.apache.org/jira/browse/MNG-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716545#comment-17716545
]
Zhongming Hua commented on MNG-7755:
[~laeubi]
I did not reproduce this problem in version 3.8.8. You can try it with 3.8.8?
If you still have problems, you can provide a demo.
> If a plugin is an extension, the managed version is ignored
> ---
>
> Key: MNG-7755
> URL: https://issues.apache.org/jira/browse/MNG-7755
> Project: Maven
> Issue Type: Bug
>Reporter: Christoph Läubrich
>Priority: Major
>
> I have the following in a child pom:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> and in the parent:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
>
>
> {code}
> This gives an warning (and alter an error):
> [WARNING] 'build.plugins.plugin.version' for
> org.eclipse.tycho:tycho-bnd-plugin is missing.
> If I write directly in the child
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> it works ... it seems to be triggered by the true
> tag here that it then do not look at ate managed version...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7755) If a plugin is an extension, the managed version is ignored
[
https://issues.apache.org/jira/browse/MNG-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716477#comment-17716477
]
Zhongming Hua commented on MNG-7755:
[~laeubi]
Please provide the maven version used.
> If a plugin is an extension, the managed version is ignored
> ---
>
> Key: MNG-7755
> URL: https://issues.apache.org/jira/browse/MNG-7755
> Project: Maven
> Issue Type: Bug
>Reporter: Christoph Läubrich
>Priority: Major
>
> I have the following in a child pom:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> and in the parent:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
>
>
> {code}
> This gives an warning (and alter an error):
> [WARNING] 'build.plugins.plugin.version' for
> org.eclipse.tycho:tycho-bnd-plugin is missing.
> If I write directly in the child
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> it works ... it seems to be triggered by the true
> tag here that it then do not look at ate managed version...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7755) If a plugin is an extension, the managed version is ignored
[
https://issues.apache.org/jira/browse/MNG-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongming Hua updated MNG-7755:
---
Attachment: image-2023-04-26-08-54-22-523.png
> If a plugin is an extension, the managed version is ignored
> ---
>
> Key: MNG-7755
> URL: https://issues.apache.org/jira/browse/MNG-7755
> Project: Maven
> Issue Type: Bug
>Reporter: Christoph Läubrich
>Priority: Major
>
> I have the following in a child pom:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> and in the parent:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
>
>
> {code}
> This gives an warning (and alter an error):
> [WARNING] 'build.plugins.plugin.version' for
> org.eclipse.tycho:tycho-bnd-plugin is missing.
> If I write directly in the child
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> it works ... it seems to be triggered by the true
> tag here that it then do not look at ate managed version...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7755) If a plugin is an extension, the managed version is ignored
[
https://issues.apache.org/jira/browse/MNG-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongming Hua updated MNG-7755:
---
Attachment: (was: image-2023-04-26-08-54-22-523.png)
> If a plugin is an extension, the managed version is ignored
> ---
>
> Key: MNG-7755
> URL: https://issues.apache.org/jira/browse/MNG-7755
> Project: Maven
> Issue Type: Bug
>Reporter: Christoph Läubrich
>Priority: Major
>
> I have the following in a child pom:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> and in the parent:
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
>
>
> {code}
> This gives an warning (and alter an error):
> [WARNING] 'build.plugins.plugin.version' for
> org.eclipse.tycho:tycho-bnd-plugin is missing.
> If I write directly in the child
> {code}
>
>
> org.eclipse.tycho
> tycho-bnd-plugin
> ${tycho.version}
> true
>
>
>
> {code}
> it works ... it seems to be triggered by the true
> tag here that it then do not look at ate managed version...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7444) Multiple optional non-existing projects not logged correctly
[
https://issues.apache.org/jira/browse/MNG-7444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716362#comment-17716362
]
Zhongming Hua commented on MNG-7444:
[~mthmulders]
I found that it is fixed in the following versions, this JIRA can be closed.
{code:java}
Apache Maven 4.0.0-alpha-6-SNAPSHOT
(81231b886563937d47560ebf468e4e24251877b7){code}
> Multiple optional non-existing projects not logged correctly
>
>
> Key: MNG-7444
> URL: https://issues.apache.org/jira/browse/MNG-7444
> Project: Maven
> Issue Type: Bug
> Components: Reactor and Workspace
> Environment: Apache Maven 4.0.0-alpha-1-SNAPSHOT
> (31193cbf0c93205a63c8c7b372b09200f60e69f4)
>Reporter: Maarten Mulders
>Priority: Trivial
> Labels: up-for-grabs
> Attachments: image-2023-04-26-00-48-51-379.png
>
>
> Run {{mvn -pl \?:a,\?:b validate}} (escaping necessary on POSIX compliant
> shells, Windows doesn't need it) on a project that does not have a module
> {{:a}} and {{:b}}.
> Expected:
> {code}
> [INFO] Could not find the selected project(s) in the reactor: :a, :b
> {code}
> Actual:
> {code}
> [INFO] Could not find the selected project in the reactor: :a
> {code}
> The output of {{mvn -help}} with regards to {{-pl}}:
> {quote}Comma-delimited list of specified reactor projects to build instead of
> all projects. A project can be specified by [groupId]:artifactId or by its
> relative path. Prefixing a project with ! excludes it, and ? marks it as
> optional{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7444) Multiple optional non-existing projects not logged correctly
[
https://issues.apache.org/jira/browse/MNG-7444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongming Hua updated MNG-7444:
---
Attachment: image-2023-04-26-00-48-51-379.png
> Multiple optional non-existing projects not logged correctly
>
>
> Key: MNG-7444
> URL: https://issues.apache.org/jira/browse/MNG-7444
> Project: Maven
> Issue Type: Bug
> Components: Reactor and Workspace
> Environment: Apache Maven 4.0.0-alpha-1-SNAPSHOT
> (31193cbf0c93205a63c8c7b372b09200f60e69f4)
>Reporter: Maarten Mulders
>Priority: Trivial
> Labels: up-for-grabs
> Attachments: image-2023-04-26-00-48-51-379.png
>
>
> Run {{mvn -pl \?:a,\?:b validate}} (escaping necessary on POSIX compliant
> shells, Windows doesn't need it) on a project that does not have a module
> {{:a}} and {{:b}}.
> Expected:
> {code}
> [INFO] Could not find the selected project(s) in the reactor: :a, :b
> {code}
> Actual:
> {code}
> [INFO] Could not find the selected project in the reactor: :a
> {code}
> The output of {{mvn -help}} with regards to {{-pl}}:
> {quote}Comma-delimited list of specified reactor projects to build instead of
> all projects. A project can be specified by [groupId]:artifactId or by its
> relative path. Prefixing a project with ! excludes it, and ? marks it as
> optional{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
