[jira] [Commented] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds
[
https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849476#comment-17849476
]
Tamas Cservenak commented on MNG-7868:
--
All affected users: please upgrade to 3.9.7 and report back. The MRESOLVER-522
should fix the problem of "hot artifacts".
> "Could not acquire lock(s)" error in concurrent maven builds
>
>
> Key: MNG-7868
> URL: https://issues.apache.org/jira/browse/MNG-7868
> Project: Maven
> Issue Type: Bug
> Environment: windows, maven 3.9.4
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: image-2024-04-10-15-44-37-013.png, screenshot-1.png
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project foo.bar: Execution default-install of goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install failed: Could not
> acquire lock(s) -> [Help 1]
> {code}
> I am using maven 3.9.4 on windows:
> {code}
> $ mvn -v
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: D:\projects\test\software\mvn
> Java version: 17.0.5, vendor: Eclipse Adoptium, runtime:
> D:\projects\test\software\java
> Default locale: en_US, platform encoding: UTF-8
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> {code}
> I searched for this bug and found issues like MRESOLVER-332 that first look
> identical or similar but do not really seem to be related so I decided to
> create this issue.
> For this bug I made the following observations:
> * it only happens with concurrent builds: {{mvn -T ...}}
> * is seems to be windows related (at least mainly happens on windows)
> * it is in-deterministic and is not so easy to create an isolated and simple
> project and a reproducible scenario that always results in this error.
> However, I get this very often in my current project with many modules (500+).
> * it is not specific to the maven-install-plugin and also happens from other
> spots in maven:
> I also got this stacktrace:
> {code}
> Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire
> write lock for
> 'C:\Users\hohwille\.m2\repository\.locks\artifact~com.caucho~com.springsource.com.caucho~3.2.1.lock'
> in 30 SECONDS
> at
> org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire
> (NamedLockFactoryAdapter.java:202)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:271)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:259)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
> (DefaultRepositorySystem.java:352)
> {code}
> See also this related discussion:
> https://github.com/apache/maven-mvnd/issues/836#issuecomment-1702488377
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MINDEXER-224) Bump com.google.code.gson:gson from 2.10.1 to 2.11.0
[ https://issues.apache.org/jira/browse/MINDEXER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MINDEXER-224: Assignee: Tamas Cservenak > Bump com.google.code.gson:gson from 2.10.1 to 2.11.0 > > > Key: MINDEXER-224 > URL: https://issues.apache.org/jira/browse/MINDEXER-224 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.1.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MINDEXER-224) Bump com.google.code.gson:gson from 2.10.1 to 2.11.0
[ https://issues.apache.org/jira/browse/MINDEXER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MINDEXER-224. Resolution: Fixed > Bump com.google.code.gson:gson from 2.10.1 to 2.11.0 > > > Key: MINDEXER-224 > URL: https://issues.apache.org/jira/browse/MINDEXER-224 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.1.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MINDEXER-224) Bump com.google.code.gson:gson from 2.10.1 to 2.11.0
Tamas Cservenak created MINDEXER-224: Summary: Bump com.google.code.gson:gson from 2.10.1 to 2.11.0 Key: MINDEXER-224 URL: https://issues.apache.org/jira/browse/MINDEXER-224 Project: Maven Indexer Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 7.1.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-564) Align with Maven4 beta-3
Tamas Cservenak created MRESOLVER-564: - Summary: Align with Maven4 beta-3 Key: MRESOLVER-564 URL: https://issues.apache.org/jira/browse/MRESOLVER-564 Project: Maven Resolver Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 2.0.0, 2.0.0-beta-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-564) Align with Maven4 beta-3
[ https://issues.apache.org/jira/browse/MRESOLVER-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-564: - Assignee: Tamas Cservenak > Align with Maven4 beta-3 > > > Key: MRESOLVER-564 > URL: https://issues.apache.org/jira/browse/MRESOLVER-564 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-289) Remove "Aether wiki" link from site
[ https://issues.apache.org/jira/browse/MRESOLVER-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-289. - Resolution: Fixed > Remove "Aether wiki" link from site > --- > > Key: MRESOLVER-289 > URL: https://issues.apache.org/jira/browse/MRESOLVER-289 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > > It points to Eclipe wiki that is defunct. Possibly migrate something from > there, if needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-526) Import Eclipse Aether wiki content to Maven Site
[
https://issues.apache.org/jira/browse/MRESOLVER-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MRESOLVER-526.
-
Resolution: Fixed
> Import Eclipse Aether wiki content to Maven Site
>
>
> Key: MRESOLVER-526
> URL: https://issues.apache.org/jira/browse/MRESOLVER-526
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Reporter: Konrad Windszus
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-beta-1
>
> Attachments: EclipseAetherWikiExportAsMD.zip,
> Eclipsepedia-20240410130147.xml
>
>
> As the Eclipse wiki is gonna be shutdown soon the content currently only
> available on https://wiki.eclipse.org/Aether (and other pages with category
> {{Aether}}) should be migrated to the resolver site.
> The steps for exporting and converting to Markdown are outlined at
> https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-Move-FAQ.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MRESOLVER-563) Bump org.codehaus.plexus:plexus-xml from 4.0.3 to 4.0.4
[ https://issues.apache.org/jira/browse/MRESOLVER-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-563. - Resolution: Fixed > Bump org.codehaus.plexus:plexus-xml from 4.0.3 to 4.0.4 > --- > > Key: MRESOLVER-563 > URL: https://issues.apache.org/jira/browse/MRESOLVER-563 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-563) Bump org.codehaus.plexus:plexus-xml from 4.0.3 to 4.0.4
[ https://issues.apache.org/jira/browse/MRESOLVER-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-563: - Assignee: Tamas Cservenak > Bump org.codehaus.plexus:plexus-xml from 4.0.3 to 4.0.4 > --- > > Key: MRESOLVER-563 > URL: https://issues.apache.org/jira/browse/MRESOLVER-563 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-563) Bump org.codehaus.plexus:plexus-xml from 4.0.3 to 4.0.4
Tamas Cservenak created MRESOLVER-563: - Summary: Bump org.codehaus.plexus:plexus-xml from 4.0.3 to 4.0.4 Key: MRESOLVER-563 URL: https://issues.apache.org/jira/browse/MRESOLVER-563 Project: Maven Resolver Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 2.0.0, 2.0.0-beta-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-562) Bump org.codehaus.mojo:exec-maven-plugin from 3.2.0 to 3.3.0
[ https://issues.apache.org/jira/browse/MRESOLVER-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-562. - Assignee: Tamas Cservenak Resolution: Fixed > Bump org.codehaus.mojo:exec-maven-plugin from 3.2.0 to 3.3.0 > > > Key: MRESOLVER-562 > URL: https://issues.apache.org/jira/browse/MRESOLVER-562 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-562) Bump org.codehaus.mojo:exec-maven-plugin from 3.2.0 to 3.3.0
Tamas Cservenak created MRESOLVER-562: - Summary: Bump org.codehaus.mojo:exec-maven-plugin from 3.2.0 to 3.3.0 Key: MRESOLVER-562 URL: https://issues.apache.org/jira/browse/MRESOLVER-562 Project: Maven Resolver Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 2.0.0, 2.0.0-beta-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8030) Backport: Add ability to ignore dependency repositories: mvn -itr
[ https://issues.apache.org/jira/browse/MNG-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8030: - Issue Type: New Feature (was: Improvement) > Backport: Add ability to ignore dependency repositories: mvn -itr > - > > Key: MNG-8030 > URL: https://issues.apache.org/jira/browse/MNG-8030 > Project: Maven > Issue Type: New Feature > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > Backport of MNG-7980 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8125) (build) Bump buildhelper-maven-plugin to 3.6.0 (was 3.4.0)
[ https://issues.apache.org/jira/browse/MNG-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-8125. Resolution: Fixed > (build) Bump buildhelper-maven-plugin to 3.6.0 (was 3.4.0) > -- > > Key: MNG-8125 > URL: https://issues.apache.org/jira/browse/MNG-8125 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap Build >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8127) Bump guava to 33.2.0-jre
[ https://issues.apache.org/jira/browse/MNG-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-8127. Resolution: Fixed > Bump guava to 33.2.0-jre > > > Key: MNG-8127 > URL: https://issues.apache.org/jira/browse/MNG-8127 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > Along with failureaccess to 1.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8126) Bump logback classic to 1.2.13 (was 1.2.12)
[ https://issues.apache.org/jira/browse/MNG-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-8126. Resolution: Fixed > Bump logback classic to 1.2.13 (was 1.2.12) > --- > > Key: MNG-8126 > URL: https://issues.apache.org/jira/browse/MNG-8126 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > To get rid of nasty alert for 1.2.12 and below versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8127) Bump guava to 33.2.0-jre
[ https://issues.apache.org/jira/browse/MNG-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8127: - Component/s: Dependencies > Bump guava to 33.2.0-jre > > > Key: MNG-8127 > URL: https://issues.apache.org/jira/browse/MNG-8127 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > Along with failureaccess to 1.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8125) (build) Bump buildhelper-maven-plugin to 3.6.0 (was 3.4.0)
[ https://issues.apache.org/jira/browse/MNG-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8125: - Component/s: Bootstrap & Build > (build) Bump buildhelper-maven-plugin to 3.6.0 (was 3.4.0) > -- > > Key: MNG-8125 > URL: https://issues.apache.org/jira/browse/MNG-8125 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap Build >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8126) Bump logback classic to 1.2.13 (was 1.2.12)
[ https://issues.apache.org/jira/browse/MNG-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8126: - Component/s: Dependencies > Bump logback classic to 1.2.13 (was 1.2.12) > --- > > Key: MNG-8126 > URL: https://issues.apache.org/jira/browse/MNG-8126 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > To get rid of nasty alert for 1.2.12 and below versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8125) (build) Bump buildhelper-maven-plugin to 3.6.0 (was 3.4.0)
[ https://issues.apache.org/jira/browse/MNG-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8125: Assignee: Tamas Cservenak > (build) Bump buildhelper-maven-plugin to 3.6.0 (was 3.4.0) > -- > > Key: MNG-8125 > URL: https://issues.apache.org/jira/browse/MNG-8125 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8126) Bump logback classic to 1.2.13 (was 1.2.12)
[ https://issues.apache.org/jira/browse/MNG-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8126: Assignee: Tamas Cservenak > Bump logback classic to 1.2.13 (was 1.2.12) > --- > > Key: MNG-8126 > URL: https://issues.apache.org/jira/browse/MNG-8126 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > To get rid of nasty alert for 1.2.12 and below versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8127) Bump guava to 33.2.0-jre
[ https://issues.apache.org/jira/browse/MNG-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8127: Assignee: Tamas Cservenak > Bump guava to 33.2.0-jre > > > Key: MNG-8127 > URL: https://issues.apache.org/jira/browse/MNG-8127 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > Along with failureaccess to 1.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8127) Bump guava to 33.2.0-jre
[ https://issues.apache.org/jira/browse/MNG-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8127: - Description: Along with failureaccess to 1.0.2 > Bump guava to 33.2.0-jre > > > Key: MNG-8127 > URL: https://issues.apache.org/jira/browse/MNG-8127 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > Along with failureaccess to 1.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8127) Bump guava to 33.2.0-jre
[ https://issues.apache.org/jira/browse/MNG-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8127: - Summary: Bump guava to 33.2.0-jre (was: Bump guava to latest) > Bump guava to 33.2.0-jre > > > Key: MNG-8127 > URL: https://issues.apache.org/jira/browse/MNG-8127 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8127) Bump guava to latest
Tamas Cservenak created MNG-8127: Summary: Bump guava to latest Key: MNG-8127 URL: https://issues.apache.org/jira/browse/MNG-8127 Project: Maven Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 3.9.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8126) Bump logback classic to 1.2.13 (was 1.2.12)
[ https://issues.apache.org/jira/browse/MNG-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8126: - Summary: Bump logback classic to 1.2.13 (was 1.2.12) (was: Bump logback classis to 1.2.13) > Bump logback classic to 1.2.13 (was 1.2.12) > --- > > Key: MNG-8126 > URL: https://issues.apache.org/jira/browse/MNG-8126 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > To get rid of nasty alert for 1.2.12 and below versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8125) (build) Bump buildhelper-maven-plugin to 3.6.0 (was 3.4.0)
[ https://issues.apache.org/jira/browse/MNG-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8125: - Summary: (build) Bump buildhelper-maven-plugin to 3.6.0 (was 3.4.0) (was: (build) Bump buildhelper-maven-plugin to 3.6.0) > (build) Bump buildhelper-maven-plugin to 3.6.0 (was 3.4.0) > -- > > Key: MNG-8125 > URL: https://issues.apache.org/jira/browse/MNG-8125 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8126) Bump logback classis to 1.2.13
Tamas Cservenak created MNG-8126: Summary: Bump logback classis to 1.2.13 Key: MNG-8126 URL: https://issues.apache.org/jira/browse/MNG-8126 Project: Maven Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 3.9.7 To get rid of nasty alert for 1.2.12 and below versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8125) (build) Bump buildhelper-maven-plugin to 3.6.0
Tamas Cservenak created MNG-8125: Summary: (build) Bump buildhelper-maven-plugin to 3.6.0 Key: MNG-8125 URL: https://issues.apache.org/jira/browse/MNG-8125 Project: Maven Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 3.9.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MNG-8116) Plugin configuration can randomly fail in case of method overloading as it doesn't take into account implementation attribute
[
https://issues.apache.org/jira/browse/MNG-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848513#comment-17848513
]
Tamas Cservenak edited comment on MNG-8116 at 5/22/24 8:55 AM:
---
Few comments: This issue is blocked by Eclipse Sisu release, that in turn, has
own "dust removal" issues:
* GH org migration and then repository consolidation
[https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4652]
* License change after EMO review
[https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/740]
* and both issues require PMC and Wayne Beaton approvals as well
Moreover, this issue should be assigned to Maven 4 beta-4 as well, as same Sisu
is used there, so same issue stands.
was (Author: cstamas):
Few comments: This issue is blocked by Eclipse Sisu release, that in turn, has
own "dust removal" issues:
* GH org migration and then repository consolidation
[https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4652]
* License change after EMO review
[https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/740]
* and both issues require PMC and Wayne Beaton approvals as well
Moreover, this issue should be assigned to Maven 4 beta-4 as well, as same Sisu
is used there, so same issue stands as well.
> Plugin configuration can randomly fail in case of method overloading as it
> doesn't take into account implementation attribute
> -
>
> Key: MNG-8116
> URL: https://issues.apache.org/jira/browse/MNG-8116
> Project: Maven
> Issue Type: Task
> Components: Plugin Requests
>Affects Versions: 3.9.6
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: 3.9.8
>
>
> Originally discovered via a Jetty bug report see
> https://github.com/jetty/jetty.project/issues/11732
> The bean to configured have the following overloading method naming:
> * public void setExtraClasspath(String extraClasspath)
> * public void setExtraClasspath(List extraClasspath)
> The plugin configuration:
>
> ${basedir}/config
>
> even forcing the implementation attribute doesn't help
>
>implementation="java.lang.String">${basedir}/config
>
> The fix is implemented via the PR
> https://github.com/eclipse/sisu.plexus/pull/52
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8116) Plugin configuration can randomly fail in case of method overloading as it doesn't take into account implementation attribute
[
https://issues.apache.org/jira/browse/MNG-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848513#comment-17848513
]
Tamas Cservenak commented on MNG-8116:
--
Few comments: This issue is blocked by Eclipse Sisu release, that in turn, has
own "dust removal" issues:
* GH org migration and then repository consolidation
[https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4652]
* License change after EMO review
[https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/740]
* and both issues require PMC and Wayne Beaton approvals as well
Moreover, this issue should be assigned to Maven 4 beta-4 as well, as same Sisu
is used there, so same issue stands as well.
> Plugin configuration can randomly fail in case of method overloading as it
> doesn't take into account implementation attribute
> -
>
> Key: MNG-8116
> URL: https://issues.apache.org/jira/browse/MNG-8116
> Project: Maven
> Issue Type: Task
> Components: Plugin Requests
>Affects Versions: 3.9.6
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: 3.9.8
>
>
> Originally discovered via a Jetty bug report see
> https://github.com/jetty/jetty.project/issues/11732
> The bean to configured have the following overloading method naming:
> * public void setExtraClasspath(String extraClasspath)
> * public void setExtraClasspath(List extraClasspath)
> The plugin configuration:
>
> ${basedir}/config
>
> even forcing the implementation attribute doesn't help
>
>implementation="java.lang.String">${basedir}/config
>
> The fix is implemented via the PR
> https://github.com/eclipse/sisu.plexus/pull/52
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8116) Plugin configuration can randomly fail in case of method overloading as it doesn't take into account implementation attribute
[
https://issues.apache.org/jira/browse/MNG-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8116:
-
Fix Version/s: 4.0.0-beta-4
> Plugin configuration can randomly fail in case of method overloading as it
> doesn't take into account implementation attribute
> -
>
> Key: MNG-8116
> URL: https://issues.apache.org/jira/browse/MNG-8116
> Project: Maven
> Issue Type: Task
> Components: Plugin Requests
>Affects Versions: 3.9.6
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: 3.9.8, 4.0.0-beta-4
>
>
> Originally discovered via a Jetty bug report see
> https://github.com/jetty/jetty.project/issues/11732
> The bean to configured have the following overloading method naming:
> * public void setExtraClasspath(String extraClasspath)
> * public void setExtraClasspath(List extraClasspath)
> The plugin configuration:
>
> ${basedir}/config
>
> even forcing the implementation attribute doesn't help
>
>implementation="java.lang.String">${basedir}/config
>
> The fix is implemented via the PR
> https://github.com/eclipse/sisu.plexus/pull/52
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8116) Plugin configuration can randomly fail in case of method overloading as it doesn't take into account implementation attribute
[
https://issues.apache.org/jira/browse/MNG-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8116:
-
Fix Version/s: 3.9.8
(was: 3.9.7)
> Plugin configuration can randomly fail in case of method overloading as it
> doesn't take into account implementation attribute
> -
>
> Key: MNG-8116
> URL: https://issues.apache.org/jira/browse/MNG-8116
> Project: Maven
> Issue Type: Task
> Components: Plugin Requests
>Affects Versions: 3.9.6
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: 3.9.8
>
>
> Originally discovered via a Jetty bug report see
> https://github.com/jetty/jetty.project/issues/11732
> The bean to configured have the following overloading method naming:
> * public void setExtraClasspath(String extraClasspath)
> * public void setExtraClasspath(List extraClasspath)
> The plugin configuration:
>
> ${basedir}/config
>
> even forcing the implementation attribute doesn't help
>
>implementation="java.lang.String">${basedir}/config
>
> The fix is implemented via the PR
> https://github.com/eclipse/sisu.plexus/pull/52
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MWRAPPER-140) only-script Type does not honor MAVEN_USER_HOME
[ https://issues.apache.org/jira/browse/MWRAPPER-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MWRAPPER-140. Resolution: Fixed > only-script Type does not honor MAVEN_USER_HOME > --- > > Key: MWRAPPER-140 > URL: https://issues.apache.org/jira/browse/MWRAPPER-140 > Project: Maven Wrapper > Issue Type: Bug > Components: Maven Wrapper Scripts >Affects Versions: 3.3.1 >Reporter: Adrian Shum >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.3.2 > > Attachments: patch > > > As per described in [https://maven.apache.org/wrapper/index.html] we could > set MAVEN_USER_HOME to define the location that Maven distro be downloaded to. > For type=bin, it seems working as expected. However for type=script-only, it > is trying to create director under ~/.m2 even I have MAVEN_USER_HOME set. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MWRAPPER-140) only-script Type does not honor MAVEN_USER_HOME
[ https://issues.apache.org/jira/browse/MWRAPPER-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MWRAPPER-140: Assignee: Tamas Cservenak > only-script Type does not honor MAVEN_USER_HOME > --- > > Key: MWRAPPER-140 > URL: https://issues.apache.org/jira/browse/MWRAPPER-140 > Project: Maven Wrapper > Issue Type: Bug > Components: Maven Wrapper Scripts >Affects Versions: 3.3.1 >Reporter: Adrian Shum >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.3.2 > > Attachments: patch > > > As per described in [https://maven.apache.org/wrapper/index.html] we could > set MAVEN_USER_HOME to define the location that Maven distro be downloaded to. > For type=bin, it seems working as expected. However for type=script-only, it > is trying to create director under ~/.m2 even I have MAVEN_USER_HOME set. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MWRAPPER-136) maven-wrapper.properties created with Windows line breaks which mvnw can't handle
[
https://issues.apache.org/jira/browse/MWRAPPER-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MWRAPPER-136.
Resolution: Fixed
> maven-wrapper.properties created with Windows line breaks which mvnw can't
> handle
> -
>
> Key: MWRAPPER-136
> URL: https://issues.apache.org/jira/browse/MWRAPPER-136
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.2.0, 3.3.0, 3.3.1
> Environment: Windows, Git BASH
>Reporter: Patrick Schmidt
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.3.2
>
>
> Since around version 3.2.0 the maven-wrapper.properties is created with
> Windows line breaks for me. Unfortunately mvnw can't handle that. The error I
> receive is:
> {noformat}
> 'istributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
> found
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.6/apache-maven-3.9.6-bin.zip{noformat}
> When I manually change it to Unix line breaks it works again. Version 3.1.0
> of the plug-in still creates it with Unix line breaks. Later versions seem to
> use the platform default instead. I.e. whenever I rerun wrapper:wrapper its
> broken again.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MWRAPPER-136) maven-wrapper.properties created with Windows line breaks which mvnw can't handle
[
https://issues.apache.org/jira/browse/MWRAPPER-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak reassigned MWRAPPER-136:
Assignee: Tamas Cservenak
> maven-wrapper.properties created with Windows line breaks which mvnw can't
> handle
> -
>
> Key: MWRAPPER-136
> URL: https://issues.apache.org/jira/browse/MWRAPPER-136
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.2.0, 3.3.0, 3.3.1
> Environment: Windows, Git BASH
>Reporter: Patrick Schmidt
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.3.2
>
>
> Since around version 3.2.0 the maven-wrapper.properties is created with
> Windows line breaks for me. Unfortunately mvnw can't handle that. The error I
> receive is:
> {noformat}
> 'istributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
> found
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.6/apache-maven-3.9.6-bin.zip{noformat}
> When I manually change it to Unix line breaks it works again. Version 3.1.0
> of the plug-in still creates it with Unix line breaks. Later versions seem to
> use the platform default instead. I.e. whenever I rerun wrapper:wrapper its
> broken again.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MWRAPPER-139) Shell scripts break on LF in config for Windows
[
https://issues.apache.org/jira/browse/MWRAPPER-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MWRAPPER-139.
Resolution: Fixed
> Shell scripts break on LF in config for Windows
> ---
>
> Key: MWRAPPER-139
> URL: https://issues.apache.org/jira/browse/MWRAPPER-139
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.1
>Reporter: Ashley Scopes
>Priority: Major
> Fix For: 3.3.2
>
>
> Today, I updated the Maven Wrapper in a project I have on GitHub by running
> `./mvnw wrapper:wrapper`, and then pushed it to GitHub.
> It appears that upon doing this, the bash scripts no longer work due to how
> newlines are being interpreted in the maven-wrapper.properties file.
> {code}
> + ./mvnw --version
> distributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
> found
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.6/apache-maven-3.9.6-bin.zip
> '
> {code}
> This appears to just affect when running on GitHub actions with a Windows
> runner and the `bash` shell.
> I will see if I can find the issue and raise a fix in an MR
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MWRAPPER-137) Can't match distributionUrl when using MINGW64
[
https://issues.apache.org/jira/browse/MWRAPPER-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MWRAPPER-137.
Resolution: Fixed
> Can't match distributionUrl when using MINGW64
> --
>
> Key: MWRAPPER-137
> URL: https://issues.apache.org/jira/browse/MWRAPPER-137
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.1
>Reporter: Robert Scholte
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.3.2
>
>
> Any mvnw command fails with the following message:
> {noformat}
> $ ./mvnw verify
> 'istributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
> found
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/4.0.0-alpha-13/apache-maven-4.0.0-alpha-13-bin.zip
> {noformat}
> Also notice that the {{d}} from distributionUrl has been replaced with a
> single quote.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MWRAPPER-139) Shell scripts break on LF in config for Windows
[
https://issues.apache.org/jira/browse/MWRAPPER-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak reassigned MWRAPPER-139:
Assignee: Tamas Cservenak
> Shell scripts break on LF in config for Windows
> ---
>
> Key: MWRAPPER-139
> URL: https://issues.apache.org/jira/browse/MWRAPPER-139
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.1
>Reporter: Ashley Scopes
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.3.2
>
>
> Today, I updated the Maven Wrapper in a project I have on GitHub by running
> `./mvnw wrapper:wrapper`, and then pushed it to GitHub.
> It appears that upon doing this, the bash scripts no longer work due to how
> newlines are being interpreted in the maven-wrapper.properties file.
> {code}
> + ./mvnw --version
> distributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
> found
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.6/apache-maven-3.9.6-bin.zip
> '
> {code}
> This appears to just affect when running on GitHub actions with a Windows
> runner and the `bash` shell.
> I will see if I can find the issue and raise a fix in an MR
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MWRAPPER-137) Can't match distributionUrl when using MINGW64
[
https://issues.apache.org/jira/browse/MWRAPPER-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak reassigned MWRAPPER-137:
Assignee: Tamas Cservenak
> Can't match distributionUrl when using MINGW64
> --
>
> Key: MWRAPPER-137
> URL: https://issues.apache.org/jira/browse/MWRAPPER-137
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.1
>Reporter: Robert Scholte
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.3.2
>
>
> Any mvnw command fails with the following message:
> {noformat}
> $ ./mvnw verify
> 'istributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
> found
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/4.0.0-alpha-13/apache-maven-4.0.0-alpha-13-bin.zip
> {noformat}
> Also notice that the {{d}} from distributionUrl has been replaced with a
> single quote.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MWRAPPER-141) Use distribution type of existing Maven Wrapper by default
[
https://issues.apache.org/jira/browse/MWRAPPER-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MWRAPPER-141.
Resolution: Fixed
> Use distribution type of existing Maven Wrapper by default
> --
>
> Key: MWRAPPER-141
> URL: https://issues.apache.org/jira/browse/MWRAPPER-141
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
>Reporter: Nils Breunese
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.3.2
>
>
> It would be great if the {{wrapper:wrapper}} goal would use the type of an
> existing Maven Wrapper as the default, because this would allow making
> changes to the Maven version or other configuration, without having to
> specify the type of the existing Maven Wrapper again. This would be
> especially handy when changing (updating) the Maven version, or the Maven
> Wrapper version.
> This would also avoid accidentally changing the distribution type when a user
> forgets to specify the type of the existing Maven Wrapper.
> It should still be possible call {{wrapper:wrapper -Dtype=$type}} to
> explicitly set a different type for an existing project.
> When there is no existing Maven Wrapper, or when it exists but doesn't have
> {{distributionType}} set in {{{}maven-wrapper.properties{}}}, then the
> default {{only-script}} type should still be used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MWRAPPER-141) Use distribution type of existing Maven Wrapper by default
[
https://issues.apache.org/jira/browse/MWRAPPER-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak reassigned MWRAPPER-141:
Assignee: Tamas Cservenak
> Use distribution type of existing Maven Wrapper by default
> --
>
> Key: MWRAPPER-141
> URL: https://issues.apache.org/jira/browse/MWRAPPER-141
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
>Reporter: Nils Breunese
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.3.2
>
>
> It would be great if the {{wrapper:wrapper}} goal would use the type of an
> existing Maven Wrapper as the default, because this would allow making
> changes to the Maven version or other configuration, without having to
> specify the type of the existing Maven Wrapper again. This would be
> especially handy when changing (updating) the Maven version, or the Maven
> Wrapper version.
> This would also avoid accidentally changing the distribution type when a user
> forgets to specify the type of the existing Maven Wrapper.
> It should still be possible call {{wrapper:wrapper -Dtype=$type}} to
> explicitly set a different type for an existing project.
> When there is no existing Maven Wrapper, or when it exists but doesn't have
> {{distributionType}} set in {{{}maven-wrapper.properties{}}}, then the
> default {{only-script}} type should still be used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-140) only-script Type does not honor MAVEN_USER_HOME
[ https://issues.apache.org/jira/browse/MWRAPPER-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MWRAPPER-140: - Fix Version/s: 3.3.2 > only-script Type does not honor MAVEN_USER_HOME > --- > > Key: MWRAPPER-140 > URL: https://issues.apache.org/jira/browse/MWRAPPER-140 > Project: Maven Wrapper > Issue Type: Bug > Components: Maven Wrapper Scripts >Affects Versions: 3.3.1 >Reporter: Adrian Shum >Priority: Major > Fix For: 3.3.2 > > Attachments: patch > > > As per described in [https://maven.apache.org/wrapper/index.html] we could > set MAVEN_USER_HOME to define the location that Maven distro be downloaded to. > For type=bin, it seems working as expected. However for type=script-only, it > is trying to create director under ~/.m2 even I have MAVEN_USER_HOME set. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MWRAPPER-141) Use distribution type of existing Maven Wrapper by default
[
https://issues.apache.org/jira/browse/MWRAPPER-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MWRAPPER-141:
-
Fix Version/s: 3.3.2
> Use distribution type of existing Maven Wrapper by default
> --
>
> Key: MWRAPPER-141
> URL: https://issues.apache.org/jira/browse/MWRAPPER-141
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
>Reporter: Nils Breunese
>Priority: Major
> Fix For: 3.3.2
>
>
> It would be great if the {{wrapper:wrapper}} goal would use the type of an
> existing Maven Wrapper as the default, because this would allow making
> changes to the Maven version or other configuration, without having to
> specify the type of the existing Maven Wrapper again. This would be
> especially handy when changing (updating) the Maven version, or the Maven
> Wrapper version.
> This would also avoid accidentally changing the distribution type when a user
> forgets to specify the type of the existing Maven Wrapper.
> It should still be possible call {{wrapper:wrapper -Dtype=$type}} to
> explicitly set a different type for an existing project.
> When there is no existing Maven Wrapper, or when it exists but doesn't have
> {{distributionType}} set in {{{}maven-wrapper.properties{}}}, then the
> default {{only-script}} type should still be used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-136) maven-wrapper.properties created with Windows line breaks which mvnw can't handle
[
https://issues.apache.org/jira/browse/MWRAPPER-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MWRAPPER-136:
-
Fix Version/s: 3.3.2
> maven-wrapper.properties created with Windows line breaks which mvnw can't
> handle
> -
>
> Key: MWRAPPER-136
> URL: https://issues.apache.org/jira/browse/MWRAPPER-136
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.2.0, 3.3.0, 3.3.1
> Environment: Windows, Git BASH
>Reporter: Patrick Schmidt
>Priority: Major
> Fix For: 3.3.2
>
>
> Since around version 3.2.0 the maven-wrapper.properties is created with
> Windows line breaks for me. Unfortunately mvnw can't handle that. The error I
> receive is:
> {noformat}
> 'istributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
> found
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.6/apache-maven-3.9.6-bin.zip{noformat}
> When I manually change it to Unix line breaks it works again. Version 3.1.0
> of the plug-in still creates it with Unix line breaks. Later versions seem to
> use the platform default instead. I.e. whenever I rerun wrapper:wrapper its
> broken again.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-137) Can't match distributionUrl when using MINGW64
[
https://issues.apache.org/jira/browse/MWRAPPER-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MWRAPPER-137:
-
Fix Version/s: 3.3.2
> Can't match distributionUrl when using MINGW64
> --
>
> Key: MWRAPPER-137
> URL: https://issues.apache.org/jira/browse/MWRAPPER-137
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.1
>Reporter: Robert Scholte
>Priority: Major
> Fix For: 3.3.2
>
>
> Any mvnw command fails with the following message:
> {noformat}
> $ ./mvnw verify
> 'istributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
> found
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/4.0.0-alpha-13/apache-maven-4.0.0-alpha-13-bin.zip
> {noformat}
> Also notice that the {{d}} from distributionUrl has been replaced with a
> single quote.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-139) Shell scripts break on LF in config for Windows
[
https://issues.apache.org/jira/browse/MWRAPPER-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MWRAPPER-139:
-
Fix Version/s: 3.3.2
> Shell scripts break on LF in config for Windows
> ---
>
> Key: MWRAPPER-139
> URL: https://issues.apache.org/jira/browse/MWRAPPER-139
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.1
>Reporter: Ashley Scopes
>Priority: Major
> Fix For: 3.3.2
>
>
> Today, I updated the Maven Wrapper in a project I have on GitHub by running
> `./mvnw wrapper:wrapper`, and then pushed it to GitHub.
> It appears that upon doing this, the bash scripts no longer work due to how
> newlines are being interpreted in the maven-wrapper.properties file.
> {code}
> + ./mvnw --version
> distributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
> found
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.6/apache-maven-3.9.6-bin.zip
> '
> {code}
> This appears to just affect when running on GitHub actions with a Windows
> runner and the `bash` shell.
> I will see if I can find the issue and raise a fix in an MR
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MRESOLVER-561) Refresh codebase, drop unused classes
[ https://issues.apache.org/jira/browse/MRESOLVER-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-561. - Resolution: Fixed > Refresh codebase, drop unused classes > - > > Key: MRESOLVER-561 > URL: https://issues.apache.org/jira/browse/MRESOLVER-561 > Project: Maven Resolver > Issue Type: Task > Components: Ant Tasks >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: ant-tasks-1.5.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-560) Use parent POM 42
[ https://issues.apache.org/jira/browse/MRESOLVER-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-560. - Resolution: Fixed > Use parent POM 42 > - > > Key: MRESOLVER-560 > URL: https://issues.apache.org/jira/browse/MRESOLVER-560 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Ant Tasks >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: ant-tasks-1.5.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-561) Refresh codebase, drop unused classes
[ https://issues.apache.org/jira/browse/MRESOLVER-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-561: - Assignee: Tamas Cservenak > Refresh codebase, drop unused classes > - > > Key: MRESOLVER-561 > URL: https://issues.apache.org/jira/browse/MRESOLVER-561 > Project: Maven Resolver > Issue Type: Task > Components: Ant Tasks >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: ant-tasks-1.5.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-560) Use parent POM 42
[ https://issues.apache.org/jira/browse/MRESOLVER-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-560: - Assignee: Tamas Cservenak > Use parent POM 42 > - > > Key: MRESOLVER-560 > URL: https://issues.apache.org/jira/browse/MRESOLVER-560 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Ant Tasks >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: ant-tasks-1.5.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-560) Use parent POM 42
Tamas Cservenak created MRESOLVER-560: - Summary: Use parent POM 42 Key: MRESOLVER-560 URL: https://issues.apache.org/jira/browse/MRESOLVER-560 Project: Maven Resolver Issue Type: Dependency upgrade Components: Ant Tasks Reporter: Tamas Cservenak Fix For: ant-tasks-1.5.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-561) Refresh codebase, drop unused classes
Tamas Cservenak created MRESOLVER-561: - Summary: Refresh codebase, drop unused classes Key: MRESOLVER-561 URL: https://issues.apache.org/jira/browse/MRESOLVER-561 Project: Maven Resolver Issue Type: Task Components: Ant Tasks Reporter: Tamas Cservenak Fix For: ant-tasks-1.5.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-524) "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null" with Nexus Staging plugin
[
https://issues.apache.org/jira/browse/MPLUGIN-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848112#comment-17848112
]
Tamas Cservenak commented on MPLUGIN-524:
-
Real solution: move off this unsupported and pretty much dead plugin. Maven4 is
soon coming, while this one is still from Maven2 times.
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null"
> with Nexus Staging plugin
>
>
> Key: MPLUGIN-524
> URL: https://issues.apache.org/jira/browse/MPLUGIN-524
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Metadata Model
>Affects Versions: 3.13.0
>Reporter: Tristan Tarrant
>Priority: Major
>
> While attempting to release a plugin with nexus-staging-maven-plugin, I get
> the following exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getP refix()" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to update
> metadata org.infinispan.maven-plugins/maven-metadata.xml: Cannot invoke
> "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null
> at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute
> (DeployMojo.java:216)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at
[jira] [Commented] (MPLUGIN-524) "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null" with Nexus Staging plugin
[
https://issues.apache.org/jira/browse/MPLUGIN-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848111#comment-17848111
]
Tamas Cservenak commented on MPLUGIN-524:
-
Possible circumvention: downgrade to "working" one (3.12.0), make your plugin
have a (now mandatory) prefix, deploy, upgrade.
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null"
> with Nexus Staging plugin
>
>
> Key: MPLUGIN-524
> URL: https://issues.apache.org/jira/browse/MPLUGIN-524
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Metadata Model
>Affects Versions: 3.13.0
>Reporter: Tristan Tarrant
>Priority: Major
>
> While attempting to release a plugin with nexus-staging-maven-plugin, I get
> the following exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getP refix()" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to update
> metadata org.infinispan.maven-plugins/maven-metadata.xml: Cannot invoke
> "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null
> at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute
> (DeployMojo.java:216)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at
[jira] [Comment Edited] (MPLUGIN-524) "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null" with Nexus Staging plugin
[
https://issues.apache.org/jira/browse/MPLUGIN-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848107#comment-17848107
]
Tamas Cservenak edited comment on MPLUGIN-524 at 5/21/24 8:45 AM:
--
I am keep saying that "staging" in Maven is not solved, and will never be
solved by these third-party sub-optimal plugins. We need to step up and do
something about this, like proof of concept MDK is
[https://github.com/maveniverse/mdk] Am really really clueless why no Maven dev
reviews and/or responds about it on ML.
was (Author: cstamas):
I am keep saying that "staging" in Maven is not solved, and will never be
solved by these sub-optimal plugins. We need to step up and do something about
this, like proof of concept MDK is [https://github.com/maveniverse/mdk] Am
really really clueless why no Maven dev reviews and/or responds about it on ML.
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null"
> with Nexus Staging plugin
>
>
> Key: MPLUGIN-524
> URL: https://issues.apache.org/jira/browse/MPLUGIN-524
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Metadata Model
>Affects Versions: 3.13.0
>Reporter: Tristan Tarrant
>Priority: Major
>
> While attempting to release a plugin with nexus-staging-maven-plugin, I get
> the following exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getP refix()" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to update
> metadata org.infinispan.maven-plugins/maven-metadata.xml: Cannot invoke
> "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null
> at
[jira] [Commented] (MPLUGIN-524) "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null" with Nexus Staging plugin
[
https://issues.apache.org/jira/browse/MPLUGIN-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848107#comment-17848107
]
Tamas Cservenak commented on MPLUGIN-524:
-
I am keep saying that "staging" in Maven is not solved, and will never be
solved by these sub-optimal plugins. We need to step up and do something about
this, like proof of concept MDK is [https://github.com/maveniverse/mdk] Am
really really clueless why no Maven dev reviews and/or responds about it on ML.
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null"
> with Nexus Staging plugin
>
>
> Key: MPLUGIN-524
> URL: https://issues.apache.org/jira/browse/MPLUGIN-524
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Metadata Model
>Affects Versions: 3.13.0
>Reporter: Tristan Tarrant
>Priority: Major
>
> While attempting to release a plugin with nexus-staging-maven-plugin, I get
> the following exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getP refix()" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to update
> metadata org.infinispan.maven-plugins/maven-metadata.xml: Cannot invoke
> "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null
> at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute
> (DeployMojo.java:216)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at
[jira] [Commented] (MPLUGIN-524) "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null" with Nexus Staging plugin
[
https://issues.apache.org/jira/browse/MPLUGIN-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848105#comment-17848105
]
Tamas Cservenak commented on MPLUGIN-524:
-
None of refd issues are related, cause is this MNG-8121.
Meaning, user had no prefix set beforehand, and now that m-p-p requires it, the
old MD used by staging plugin pukes.
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null"
> with Nexus Staging plugin
>
>
> Key: MPLUGIN-524
> URL: https://issues.apache.org/jira/browse/MPLUGIN-524
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Metadata Model
>Affects Versions: 3.13.0
>Reporter: Tristan Tarrant
>Priority: Major
>
> While attempting to release a plugin with nexus-staging-maven-plugin, I get
> the following exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getP refix()" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to update
> metadata org.infinispan.maven-plugins/maven-metadata.xml: Cannot invoke
> "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null
> at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute
> (DeployMojo.java:216)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
[jira] [Updated] (MRESOLVER-289) Remove "Aether wiki" link from site
[ https://issues.apache.org/jira/browse/MRESOLVER-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-289: -- Fix Version/s: 2.0.0-beta-1 > Remove "Aether wiki" link from site > --- > > Key: MRESOLVER-289 > URL: https://issues.apache.org/jira/browse/MRESOLVER-289 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > > It points to Eclipe wiki that is defunct. Possibly migrate something from > there, if needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-289) Remove "Aether wiki" link from site
[ https://issues.apache.org/jira/browse/MRESOLVER-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-289: - Assignee: Tamas Cservenak > Remove "Aether wiki" link from site > --- > > Key: MRESOLVER-289 > URL: https://issues.apache.org/jira/browse/MRESOLVER-289 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > It points to Eclipe wiki that is defunct. Possibly migrate something from > there, if needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-526) Import Eclipse Aether wiki content to Maven Site
[
https://issues.apache.org/jira/browse/MRESOLVER-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak reassigned MRESOLVER-526:
-
Assignee: Tamas Cservenak
> Import Eclipse Aether wiki content to Maven Site
>
>
> Key: MRESOLVER-526
> URL: https://issues.apache.org/jira/browse/MRESOLVER-526
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Reporter: Konrad Windszus
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-beta-1
>
> Attachments: EclipseAetherWikiExportAsMD.zip,
> Eclipsepedia-20240410130147.xml
>
>
> As the Eclipse wiki is gonna be shutdown soon the content currently only
> available on https://wiki.eclipse.org/Aether (and other pages with category
> {{Aether}}) should be migrated to the resolver site.
> The steps for exporting and converting to Markdown are outlined at
> https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-Move-FAQ.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPLUGIN-524) "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null" with Nexus Staging plugin
[
https://issues.apache.org/jira/browse/MPLUGIN-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848097#comment-17848097
]
Tamas Cservenak commented on MPLUGIN-524:
-
Just take a peek at stack trace:
*
{{org.sonatype.nexus.maven.staging.deploy.strategy.AbstractDeployStrategy.deployUp}}
initiates a deploy
* goes thru {{org.eclipse.aether.internal.impl.DefaultDeployer}}
* and then resolver ends up here, in a Maven2 class
[https://github.com/apache/maven/blob/master/maven-compat/src/main/java/org/apache/maven/artifact/repository/metadata/MetadataBridge.java]
* hence, it means that DeployRequest.metadata contained this Maven2 class, and
request was created by offender in first bullet
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null"
> with Nexus Staging plugin
>
>
> Key: MPLUGIN-524
> URL: https://issues.apache.org/jira/browse/MPLUGIN-524
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Metadata Model
>Affects Versions: 3.13.0
>Reporter: Tristan Tarrant
>Priority: Major
>
> While attempting to release a plugin with nexus-staging-maven-plugin, I get
> the following exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getP refix()" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to update
> metadata org.infinispan.maven-plugins/maven-metadata.xml: Cannot invoke
> "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null
> at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute
> (DeployMojo.java:216)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at
[jira] [Commented] (MRESOLVER-526) Import Eclipse Aether wiki content to Maven Site
[
https://issues.apache.org/jira/browse/MRESOLVER-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848077#comment-17848077
]
Tamas Cservenak commented on MRESOLVER-526:
---
I find 1/3 of exported content outdated: These pages
* GettingAether – is IMHO superfluous
* NewAndNoteworthy – is decade old and past
* SettingAetherUp – talks about dropped ServiceLocator, is outdated
I don't find any value in rewrite/update these pages, will instead omit them
from site completely.
> Import Eclipse Aether wiki content to Maven Site
>
>
> Key: MRESOLVER-526
> URL: https://issues.apache.org/jira/browse/MRESOLVER-526
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 2.0.0, 2.0.0-beta-1
>
> Attachments: EclipseAetherWikiExportAsMD.zip,
> Eclipsepedia-20240410130147.xml
>
>
> As the Eclipse wiki is gonna be shutdown soon the content currently only
> available on https://wiki.eclipse.org/Aether (and other pages with category
> {{Aether}}) should be migrated to the resolver site.
> The steps for exporting and converting to Markdown are outlined at
> https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-Move-FAQ.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MRESOLVER-553) Undo site redirection
[ https://issues.apache.org/jira/browse/MRESOLVER-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-553. - Resolution: Fixed > Undo site redirection > - > > Key: MRESOLVER-553 > URL: https://issues.apache.org/jira/browse/MRESOLVER-553 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > > Undo MRESOLVER-552 as it was done when 1.x was already staged and on vote. > It is actually 1.x that should go LATEST-1.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-553) Undo site redirection
[ https://issues.apache.org/jira/browse/MRESOLVER-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-553: - Assignee: Tamas Cservenak > Undo site redirection > - > > Key: MRESOLVER-553 > URL: https://issues.apache.org/jira/browse/MRESOLVER-553 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > > Undo MRESOLVER-552 as it was done when 1.x was already staged and on vote. > It is actually 1.x that should go LATEST-1.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-526) Import Eclipse Aether wiki content to Maven Site
[
https://issues.apache.org/jira/browse/MRESOLVER-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-526:
--
Component/s: Resolver
> Import Eclipse Aether wiki content to Maven Site
>
>
> Key: MRESOLVER-526
> URL: https://issues.apache.org/jira/browse/MRESOLVER-526
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 2.0.0, 2.0.0-beta-1
>
> Attachments: EclipseAetherWikiExportAsMD.zip,
> Eclipsepedia-20240410130147.xml
>
>
> As the Eclipse wiki is gonna be shutdown soon the content currently only
> available on https://wiki.eclipse.org/Aether (and other pages with category
> {{Aether}}) should be migrated to the resolver site.
> The steps for exporting and converting to Markdown are outlined at
> https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-Move-FAQ.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MRESOLVER-555) Existence check should lax the repository update policy
[ https://issues.apache.org/jira/browse/MRESOLVER-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-555: -- Fix Version/s: (was: 2.0.0) (was: 2.0.0-beta-1) > Existence check should lax the repository update policy > --- > > Key: MRESOLVER-555 > URL: https://issues.apache.org/jira/browse/MRESOLVER-555 > Project: Maven Resolver > Issue Type: Bug > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > > Maybe only when update policy is "never". > Order of events: > * attempt a build with not-yet-released-artifact (for example resolver in > maven) > * as it is not in central, build will fail, and central URL will be "cached" > as 404 for given artifact > * fix, rinse, repeat, add staging repository, rebuild > * build will pass ok, as staging repository will have the artifact, it is > cached to local repository (from staging repository) > * later, staging repository is dropped, release promoted to central. > * rebuild: here, Resolver will nag that "artifact is present but not > available", which is true: it was cached from staging repository > * it will go try to see is it available in central (existence check), but: > central has 404 cached (see step 1), and in this case update policy is being > obeyed, that is "never" > * due "never" update policy existence check will fail, and build will fail > Now, IMO, for "existence check" Resolver should lax the policy ONLY if it is > "never" maybe? As from this situation only escape route is build with -U that > will reset local repository state and build will pass. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-289) Remove "Aether wiki" link from site
[ https://issues.apache.org/jira/browse/MRESOLVER-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-289: -- Fix Version/s: 2.0.0 > Remove "Aether wiki" link from site > --- > > Key: MRESOLVER-289 > URL: https://issues.apache.org/jira/browse/MRESOLVER-289 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > It points to Eclipe wiki that is defunct. Possibly migrate something from > there, if needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-559) Bump commons-codec:commons-codec from 1.16.1 to 1.17.0
[ https://issues.apache.org/jira/browse/MRESOLVER-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-559. - Assignee: Tamas Cservenak Resolution: Fixed > Bump commons-codec:commons-codec from 1.16.1 to 1.17.0 > -- > > Key: MRESOLVER-559 > URL: https://issues.apache.org/jira/browse/MRESOLVER-559 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-559) Bump commons-codec:commons-codec from 1.16.1 to 1.17.0
Tamas Cservenak created MRESOLVER-559: - Summary: Bump commons-codec:commons-codec from 1.16.1 to 1.17.0 Key: MRESOLVER-559 URL: https://issues.apache.org/jira/browse/MRESOLVER-559 Project: Maven Resolver Issue Type: Dependency upgrade Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.0, 2.0.0-beta-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-558) (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.21.1 to 0.21.2
[ https://issues.apache.org/jira/browse/MRESOLVER-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-558. - Resolution: Fixed > (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.21.1 to > 0.21.2 > - > > Key: MRESOLVER-558 > URL: https://issues.apache.org/jira/browse/MRESOLVER-558 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-558) (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.21.1 to 0.21.2
[ https://issues.apache.org/jira/browse/MRESOLVER-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-558: - Assignee: Tamas Cservenak > (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.21.1 to > 0.21.2 > - > > Key: MRESOLVER-558 > URL: https://issues.apache.org/jira/browse/MRESOLVER-558 > Project: Maven Resolver > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-558) (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.21.1 to 0.21.2
[ https://issues.apache.org/jira/browse/MRESOLVER-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-558: -- Component/s: Resolver > (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.21.1 to > 0.21.2 > - > > Key: MRESOLVER-558 > URL: https://issues.apache.org/jira/browse/MRESOLVER-558 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-558) (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.21.1 to 0.21.2
Tamas Cservenak created MRESOLVER-558: - Summary: (build) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.21.1 to 0.21.2 Key: MRESOLVER-558 URL: https://issues.apache.org/jira/browse/MRESOLVER-558 Project: Maven Resolver Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 2.0.0, 2.0.0-beta-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-557) Bump org.redisson:redisson from 3.29.0 to 3.30.0
[ https://issues.apache.org/jira/browse/MRESOLVER-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-557. - Assignee: Tamas Cservenak Resolution: Fixed > Bump org.redisson:redisson from 3.29.0 to 3.30.0 > > > Key: MRESOLVER-557 > URL: https://issues.apache.org/jira/browse/MRESOLVER-557 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-556) Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 10.0.21
[ https://issues.apache.org/jira/browse/MRESOLVER-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-556: - Assignee: Tamas Cservenak > Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 10.0.21 > > > Key: MRESOLVER-556 > URL: https://issues.apache.org/jira/browse/MRESOLVER-556 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-556) Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 10.0.21
[ https://issues.apache.org/jira/browse/MRESOLVER-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-556. - Resolution: Fixed > Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 10.0.21 > > > Key: MRESOLVER-556 > URL: https://issues.apache.org/jira/browse/MRESOLVER-556 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-557) Bump org.redisson:redisson from 3.29.0 to 3.30.0
Tamas Cservenak created MRESOLVER-557: - Summary: Bump org.redisson:redisson from 3.29.0 to 3.30.0 Key: MRESOLVER-557 URL: https://issues.apache.org/jira/browse/MRESOLVER-557 Project: Maven Resolver Issue Type: Dependency upgrade Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.0, 2.0.0-beta-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-556) Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 10.0.21
Tamas Cservenak created MRESOLVER-556: - Summary: Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 10.0.21 Key: MRESOLVER-556 URL: https://issues.apache.org/jira/browse/MRESOLVER-556 Project: Maven Resolver Issue Type: Dependency upgrade Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.0, 2.0.0-beta-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8089) Introduce "fat" type for JAR
[
https://issues.apache.org/jira/browse/MNG-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8089:
-
Description: Add {{fatjar}} type supported out of the box.
> Introduce "fat" type for JAR
>
>
> Key: MNG-8089
> URL: https://issues.apache.org/jira/browse/MNG-8089
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 4.0.0, 4.0.0-beta-2
>
>
> Add {{fatjar}} type supported out of the box.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8089) Introduce "fat" type for JAR
[ https://issues.apache.org/jira/browse/MNG-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8089: - Summary: Introduce "fat" type for JAR (was: Introduce "fat" types for JAR) > Introduce "fat" type for JAR > > > Key: MNG-8089 > URL: https://issues.apache.org/jira/browse/MNG-8089 > Project: Maven > Issue Type: Improvement > Components: Core >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MGPG-92) `--pinentry-mode error` cannot be used with gpg-agent "extra" socket
[
https://issues.apache.org/jira/browse/MGPG-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847418#comment-17847418
]
Tamas Cservenak commented on MGPG-92:
-
True, in case of HW device BouncyCastle signer will not help.
Am not quite educated with HW keys, could you maybe provide a PR or at least a
"hint" what should be modified to make it work for you?
> `--pinentry-mode error` cannot be used with gpg-agent "extra" socket
>
>
> Key: MGPG-92
> URL: https://issues.apache.org/jira/browse/MGPG-92
> Project: Maven GPG Plugin
> Issue Type: Bug
>Reporter: Nick Dimiduk
>Priority: Major
>
> Over on HBASE-27312, we found an issue in our release automation, which
> relies on using this plugin and a GnuPG agent for performing builds inside of
> an isolated environment. With GPG version >= 2.1, the plugin will make use of
> {{--pinentry-mode error}}. This feature appears to not be available using the
> "extra" gpg-agent socket. We had to "upgrade" to using the "standard" socket,
> which probably exposes more gpg features to the isolated environment than we
> would like.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MWRAPPER-135) Provide a reliable way to determine the Maven Wrapper type
[ https://issues.apache.org/jira/browse/MWRAPPER-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MWRAPPER-135. Assignee: Tamas Cservenak Resolution: Fixed Thanks [~breun] > Provide a reliable way to determine the Maven Wrapper type > -- > > Key: MWRAPPER-135 > URL: https://issues.apache.org/jira/browse/MWRAPPER-135 > Project: Maven Wrapper > Issue Type: Task > Components: Maven Wrapper Plugin >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.3.2 > > > Just like MWRAPPER-134 but for type. I completely forgot about this. As this > way, tooling can figure out not only version but type (also for humans, just > peek at properties). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MINDEXER-223) Upgrade slf4j to version 2.0.13
[ https://issues.apache.org/jira/browse/MINDEXER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MINDEXER-223. Resolution: Fixed > Upgrade slf4j to version 2.0.13 > --- > > Key: MINDEXER-223 > URL: https://issues.apache.org/jira/browse/MINDEXER-223 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.1.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MINDEXER-222) RR backend in case of GAVCE search should use Last-Modified HTTP header
[ https://issues.apache.org/jira/browse/MINDEXER-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MINDEXER-222. Resolution: Fixed > RR backend in case of GAVCE search should use Last-Modified HTTP header > --- > > Key: MINDEXER-222 > URL: https://issues.apache.org/jira/browse/MINDEXER-222 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.1.3 > > > And fill out Record last modified field. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MINDEXER-223) Upgrade slf4j to version 2.0.13
[ https://issues.apache.org/jira/browse/MINDEXER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MINDEXER-223: Assignee: Tamas Cservenak > Upgrade slf4j to version 2.0.13 > --- > > Key: MINDEXER-223 > URL: https://issues.apache.org/jira/browse/MINDEXER-223 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.1.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MINDEXER-223) Upgrade slf4j to version 2.0.13
Tamas Cservenak created MINDEXER-223: Summary: Upgrade slf4j to version 2.0.13 Key: MINDEXER-223 URL: https://issues.apache.org/jira/browse/MINDEXER-223 Project: Maven Indexer Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 7.1.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MINDEXER-222) RR backend in case of GAVCE search should use Last-Modified HTTP header
[ https://issues.apache.org/jira/browse/MINDEXER-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MINDEXER-222: Assignee: Tamas Cservenak > RR backend in case of GAVCE search should use Last-Modified HTTP header > --- > > Key: MINDEXER-222 > URL: https://issues.apache.org/jira/browse/MINDEXER-222 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.1.3 > > > And fill out Record last modified field. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINDEXER-206) Search Backend SMO and RR handle different Artifact.extension
[ https://issues.apache.org/jira/browse/MINDEXER-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MINDEXER-206: - Fix Version/s: (was: 7.1.3) > Search Backend SMO and RR handle different Artifact.extension > - > > Key: MINDEXER-206 > URL: https://issues.apache.org/jira/browse/MINDEXER-206 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamas Cservenak >Priority: Major > > The two backends should not force caller to construct Query differently, but > handle their own implementation specifics silently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MINDEXER-222) RR backend in case of GAVCE search should use Last-Modified HTTP header
Tamas Cservenak created MINDEXER-222: Summary: RR backend in case of GAVCE search should use Last-Modified HTTP header Key: MINDEXER-222 URL: https://issues.apache.org/jira/browse/MINDEXER-222 Project: Maven Indexer Issue Type: Improvement Reporter: Tamas Cservenak Fix For: 7.1.3 And fill out Record last modified field. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7375) Potential NPE in o.a.m.artifact.repository.metadata.Metadata.merge(...) with invalid/incomplete plugin metadata
[
https://issues.apache.org/jira/browse/MNG-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846724#comment-17846724
]
Tamas Cservenak commented on MNG-7375:
--
According to today's XSD files, those elements are still optional.
> Potential NPE in o.a.m.artifact.repository.metadata.Metadata.merge(...) with
> invalid/incomplete plugin metadata
> ---
>
> Key: MNG-7375
> URL: https://issues.apache.org/jira/browse/MNG-7375
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
>Affects Versions: 3.8.4
>Reporter: Konrad Windszus
>Priority: Major
> Attachments: NEXUS-30749 - Broken groupId metadata and follow-up NPE
> during
> org.sonatype.nexus.maven.staging.deploy.strategy.AbstractDeployStrategy.deployUp
> - Sonatype JIRA.pdf
>
>
> Currently the metadata at
> https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
> contains an invalid entry without a prefix:
> {code:xml}
>
>
>
> Apache Jackrabbit FileVault - Package Maven Plugin
> filevault-package
> filevault-package-maven-plugin
>
>
> filevault-package-maven-plugin
> filevault-package-maven-plugin
>
>
>
> {code}
> This leads to an NPE when trying to deploy a new version with
> {{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:
> {noformat}
> Caused by: java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:276)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
> (AbstractRepositoryMetadata.java:121)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
> (AbstractRepositoryMetadata.java:67)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge
> (MetadataBridge.java:65)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload
> (DefaultDeployer.java:433)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:321)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:213)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy
> (DefaultRepositorySystem.java:386)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> (DefaultArtifactDeployer.java:142)
> {noformat}
> Although this happened in the context of using
> "[org.sonatype.plugins:nexus-staging-maven-plugin|https://github.com/sonatype/nexus-maven-plugins]:1.6.8;
> (issue https://issues.sonatype.org/browse/NEXUS-30749 opened, exported to
> [^NEXUS-30749 - Broken groupId metadata and follow-up NPE during
> org.sonatype.nexus.maven.staging.deploy.strategy.AbstractDeployStrategy.deployUp
> - Sonatype JIRA.pdf] ), the affected code is in Maven.
> The metadata is probably invalid but the Metadata class should be more robust
> when trying to do the merge in
> https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100
> and just ignore all plugin entries without all mandatory elements.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7375) Potential NPE in o.a.m.artifact.repository.metadata.Metadata.merge(...) with invalid/incomplete plugin metadata
[
https://issues.apache.org/jira/browse/MNG-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846723#comment-17846723
]
Tamas Cservenak commented on MNG-7375:
--
IMHO, this issue is fixed with MNG-8121
> Potential NPE in o.a.m.artifact.repository.metadata.Metadata.merge(...) with
> invalid/incomplete plugin metadata
> ---
>
> Key: MNG-7375
> URL: https://issues.apache.org/jira/browse/MNG-7375
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
>Affects Versions: 3.8.4
>Reporter: Konrad Windszus
>Priority: Major
> Attachments: NEXUS-30749 - Broken groupId metadata and follow-up NPE
> during
> org.sonatype.nexus.maven.staging.deploy.strategy.AbstractDeployStrategy.deployUp
> - Sonatype JIRA.pdf
>
>
> Currently the metadata at
> https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
> contains an invalid entry without a prefix:
> {code:xml}
>
>
>
> Apache Jackrabbit FileVault - Package Maven Plugin
> filevault-package
> filevault-package-maven-plugin
>
>
> filevault-package-maven-plugin
> filevault-package-maven-plugin
>
>
>
> {code}
> This leads to an NPE when trying to deploy a new version with
> {{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:
> {noformat}
> Caused by: java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:276)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
> (AbstractRepositoryMetadata.java:121)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
> (AbstractRepositoryMetadata.java:67)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge
> (MetadataBridge.java:65)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload
> (DefaultDeployer.java:433)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:321)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:213)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy
> (DefaultRepositorySystem.java:386)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> (DefaultArtifactDeployer.java:142)
> {noformat}
> Although this happened in the context of using
> "[org.sonatype.plugins:nexus-staging-maven-plugin|https://github.com/sonatype/nexus-maven-plugins]:1.6.8;
> (issue https://issues.sonatype.org/browse/NEXUS-30749 opened, exported to
> [^NEXUS-30749 - Broken groupId metadata and follow-up NPE during
> org.sonatype.nexus.maven.staging.deploy.strategy.AbstractDeployStrategy.deployUp
> - Sonatype JIRA.pdf] ), the affected code is in Maven.
> The metadata is probably invalid but the Metadata class should be more robust
> when trying to do the merge in
> https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100
> and just ignore all plugin entries without all mandatory elements.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-8121) NullPointerException at org.apache.maven.artifact.repository.metadata.Metadata.merge (Metadata.java:293)
[
https://issues.apache.org/jira/browse/MNG-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MNG-8121.
Resolution: Fixed
> NullPointerException at
> org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
>
>
> Key: MNG-8121
> URL: https://issues.apache.org/jira/browse/MNG-8121
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.9.6
> Environment: Maven 3.9.6
> maven-plugin-plugin 3.13.0
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13
>Reporter: Gili
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.7, 4.0.0, 4.0.0-beta-3
>
>
> TL;DR {{org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)}} throws {{NullPointerException}} if previous releases of
> a plugin did not have a goalPrefix set.
>
> At least, this is my interpretation of what is going on.
>
> Background
> -
>
> I have an open-source project at
> [https://github.com/cmake-maven-project/cmake-maven-project/tree/v3.27.1-b1]
> with the following coordinates:
>
> com.googlecode.cmake-maven-project
> cmake
>
> If I upgrade "maven-plugin-plugin" from version 3.10.1 to 3.13.0 I am forced
> to set "" because of
> https://issues.apache.org/jira/browse/MPLUGIN-450 and
> [https://github.com/apache/maven-plugin-tools/commit/ed4774bcd8b8d2d1f7ff1196cf7644054cb3ae14#diff-624cbd32cd7fc0f3f9154fbec92b8a1aebb04614360b4a0b5fc28a407e99d743L96]
>
> In my particular case, I set "cmake-binaries" inside
> cmake-binaries-plugin/pom.xml.
> Now, when I try deploying a release to Maven Central I get the following
> exception stack trace:
>
>
> {noformat}
> java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
> (AbstractRepositoryMetadata.java:99)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
> (AbstractRepositoryMetadata.java:59)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge
> (MetadataBridge.java:56)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload
> (DefaultDeployer.java:399)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:294)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:202)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy
> (DefaultRepositorySystem.java:393)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> (DefaultArtifactDeployer.java:131)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.AbstractDeployStrategy.deployUp
> (AbstractDeployStrategy.java:213)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.StagingDeployStrategy.finalizeDeploy
> (StagingDeployStrategy.java:125)
> at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute
> (DeployMojo.java:213)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126){noformat}
>
> I assume that this is caused by {{preExisting.getPrefix()}} returning null,
> but I have no idea why this is happening. Perhaps this is caused by previous
> versions not have a goalPrefix set? Shouldn't the implementation handle this
> possibility?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8121) NullPointerException at org.apache.maven.artifact.repository.metadata.Metadata.merge (Metadata.java:293)
[
https://issues.apache.org/jira/browse/MNG-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8121:
-
Fix Version/s: 4.0.0
4.0.0-beta-3
> NullPointerException at
> org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
>
>
> Key: MNG-8121
> URL: https://issues.apache.org/jira/browse/MNG-8121
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.9.6
> Environment: Maven 3.9.6
> maven-plugin-plugin 3.13.0
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13
>Reporter: Gili
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.7, 4.0.0, 4.0.0-beta-3
>
>
> TL;DR {{org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)}} throws {{NullPointerException}} if previous releases of
> a plugin did not have a goalPrefix set.
>
> At least, this is my interpretation of what is going on.
>
> Background
> -
>
> I have an open-source project at
> [https://github.com/cmake-maven-project/cmake-maven-project/tree/v3.27.1-b1]
> with the following coordinates:
>
> com.googlecode.cmake-maven-project
> cmake
>
> If I upgrade "maven-plugin-plugin" from version 3.10.1 to 3.13.0 I am forced
> to set "" because of
> https://issues.apache.org/jira/browse/MPLUGIN-450 and
> [https://github.com/apache/maven-plugin-tools/commit/ed4774bcd8b8d2d1f7ff1196cf7644054cb3ae14#diff-624cbd32cd7fc0f3f9154fbec92b8a1aebb04614360b4a0b5fc28a407e99d743L96]
>
> In my particular case, I set "cmake-binaries" inside
> cmake-binaries-plugin/pom.xml.
> Now, when I try deploying a release to Maven Central I get the following
> exception stack trace:
>
>
> {noformat}
> java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
> (AbstractRepositoryMetadata.java:99)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
> (AbstractRepositoryMetadata.java:59)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge
> (MetadataBridge.java:56)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload
> (DefaultDeployer.java:399)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:294)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:202)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy
> (DefaultRepositorySystem.java:393)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> (DefaultArtifactDeployer.java:131)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.AbstractDeployStrategy.deployUp
> (AbstractDeployStrategy.java:213)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.StagingDeployStrategy.finalizeDeploy
> (StagingDeployStrategy.java:125)
> at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute
> (DeployMojo.java:213)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126){noformat}
>
> I assume that this is caused by {{preExisting.getPrefix()}} returning null,
> but I have no idea why this is happening. Perhaps this is caused by previous
> versions not have a goalPrefix set? Shouldn't the implementation handle this
> possibility?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MNG-8121) NullPointerException at org.apache.maven.artifact.repository.metadata.Metadata.merge (Metadata.java:293)
[
https://issues.apache.org/jira/browse/MNG-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak reassigned MNG-8121:
Assignee: Tamas Cservenak
> NullPointerException at
> org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
>
>
> Key: MNG-8121
> URL: https://issues.apache.org/jira/browse/MNG-8121
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.9.6
> Environment: Maven 3.9.6
> maven-plugin-plugin 3.13.0
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13
>Reporter: Gili
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.7
>
>
> TL;DR {{org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)}} throws {{NullPointerException}} if previous releases of
> a plugin did not have a goalPrefix set.
>
> At least, this is my interpretation of what is going on.
>
> Background
> -
>
> I have an open-source project at
> [https://github.com/cmake-maven-project/cmake-maven-project/tree/v3.27.1-b1]
> with the following coordinates:
>
> com.googlecode.cmake-maven-project
> cmake
>
> If I upgrade "maven-plugin-plugin" from version 3.10.1 to 3.13.0 I am forced
> to set "" because of
> https://issues.apache.org/jira/browse/MPLUGIN-450 and
> [https://github.com/apache/maven-plugin-tools/commit/ed4774bcd8b8d2d1f7ff1196cf7644054cb3ae14#diff-624cbd32cd7fc0f3f9154fbec92b8a1aebb04614360b4a0b5fc28a407e99d743L96]
>
> In my particular case, I set "cmake-binaries" inside
> cmake-binaries-plugin/pom.xml.
> Now, when I try deploying a release to Maven Central I get the following
> exception stack trace:
>
>
> {noformat}
> java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
> (AbstractRepositoryMetadata.java:99)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
> (AbstractRepositoryMetadata.java:59)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge
> (MetadataBridge.java:56)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload
> (DefaultDeployer.java:399)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:294)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:202)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy
> (DefaultRepositorySystem.java:393)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> (DefaultArtifactDeployer.java:131)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.AbstractDeployStrategy.deployUp
> (AbstractDeployStrategy.java:213)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.StagingDeployStrategy.finalizeDeploy
> (StagingDeployStrategy.java:125)
> at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute
> (DeployMojo.java:213)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126){noformat}
>
> I assume that this is caused by {{preExisting.getPrefix()}} returning null,
> but I have no idea why this is happening. Perhaps this is caused by previous
> versions not have a goalPrefix set? Shouldn't the implementation handle this
> possibility?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8121) NullPointerException at org.apache.maven.artifact.repository.metadata.Metadata.merge (Metadata.java:293)
[
https://issues.apache.org/jira/browse/MNG-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8121:
-
Fix Version/s: 3.9.7
> NullPointerException at
> org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
>
>
> Key: MNG-8121
> URL: https://issues.apache.org/jira/browse/MNG-8121
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.9.6
> Environment: Maven 3.9.6
> maven-plugin-plugin 3.13.0
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13
>Reporter: Gili
>Priority: Major
> Fix For: 3.9.7
>
>
> TL;DR {{org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)}} throws {{NullPointerException}} if previous releases of
> a plugin did not have a goalPrefix set.
>
> At least, this is my interpretation of what is going on.
>
> Background
> -
>
> I have an open-source project at
> [https://github.com/cmake-maven-project/cmake-maven-project/tree/v3.27.1-b1]
> with the following coordinates:
>
> com.googlecode.cmake-maven-project
> cmake
>
> If I upgrade "maven-plugin-plugin" from version 3.10.1 to 3.13.0 I am forced
> to set "" because of
> https://issues.apache.org/jira/browse/MPLUGIN-450 and
> [https://github.com/apache/maven-plugin-tools/commit/ed4774bcd8b8d2d1f7ff1196cf7644054cb3ae14#diff-624cbd32cd7fc0f3f9154fbec92b8a1aebb04614360b4a0b5fc28a407e99d743L96]
>
> In my particular case, I set "cmake-binaries" inside
> cmake-binaries-plugin/pom.xml.
> Now, when I try deploying a release to Maven Central I get the following
> exception stack trace:
>
>
> {noformat}
> java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
> (AbstractRepositoryMetadata.java:99)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
> (AbstractRepositoryMetadata.java:59)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge
> (MetadataBridge.java:56)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload
> (DefaultDeployer.java:399)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:294)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:202)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy
> (DefaultRepositorySystem.java:393)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> (DefaultArtifactDeployer.java:131)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.AbstractDeployStrategy.deployUp
> (AbstractDeployStrategy.java:213)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.StagingDeployStrategy.finalizeDeploy
> (StagingDeployStrategy.java:125)
> at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute
> (DeployMojo.java:213)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126){noformat}
>
> I assume that this is caused by {{preExisting.getPrefix()}} returning null,
> but I have no idea why this is happening. Perhaps this is caused by previous
> versions not have a goalPrefix set? Shouldn't the implementation handle this
> possibility?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8121) NullPointerException at org.apache.maven.artifact.repository.metadata.Metadata.merge (Metadata.java:293)
[
https://issues.apache.org/jira/browse/MNG-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846685#comment-17846685
]
Tamas Cservenak commented on MNG-8121:
--
As I see, your GH action already has $STAGING_REPOSITORY_ID:
[https://github.com/cmake-maven-project/cmake-maven-project/blob/master/.github/workflows/deploy_to_maven_central.yml#L76]
So all you need is to:
* drop nexus-staging-plugin alltogether
* use plain maven-deploy-plugin and use
{{-DaltDeploymentRepository=someId::https://s01.oss.sonatype.org/service/local/staging/deployByRepositoryId/$STAGING_REPOSITORY_ID/}}
> NullPointerException at
> org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
>
>
> Key: MNG-8121
> URL: https://issues.apache.org/jira/browse/MNG-8121
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.9.6
> Environment: Maven 3.9.6
> maven-plugin-plugin 3.13.0
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13
>Reporter: Gili
>Priority: Major
>
> TL;DR {{org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)}} throws {{NullPointerException}} if previous releases of
> a plugin did not have a goalPrefix set.
>
> At least, this is my interpretation of what is going on.
>
> Background
> -
>
> I have an open-source project at
> [https://github.com/cmake-maven-project/cmake-maven-project/tree/v3.27.1-b1]
> with the following coordinates:
>
> com.googlecode.cmake-maven-project
> cmake
>
> If I upgrade "maven-plugin-plugin" from version 3.10.1 to 3.13.0 I am forced
> to set "" because of
> https://issues.apache.org/jira/browse/MPLUGIN-450 and
> [https://github.com/apache/maven-plugin-tools/commit/ed4774bcd8b8d2d1f7ff1196cf7644054cb3ae14#diff-624cbd32cd7fc0f3f9154fbec92b8a1aebb04614360b4a0b5fc28a407e99d743L96]
>
> In my particular case, I set "cmake-binaries" inside
> cmake-binaries-plugin/pom.xml.
> Now, when I try deploying a release to Maven Central I get the following
> exception stack trace:
>
>
> {noformat}
> java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
> (AbstractRepositoryMetadata.java:99)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
> (AbstractRepositoryMetadata.java:59)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge
> (MetadataBridge.java:56)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload
> (DefaultDeployer.java:399)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:294)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:202)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy
> (DefaultRepositorySystem.java:393)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> (DefaultArtifactDeployer.java:131)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.AbstractDeployStrategy.deployUp
> (AbstractDeployStrategy.java:213)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.StagingDeployStrategy.finalizeDeploy
> (StagingDeployStrategy.java:125)
> at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute
> (DeployMojo.java:213)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126){noformat}
>
> I assume that this is caused by {{preExisting.getPrefix()}} returning null,
> but I have no idea why this is happening. Perhaps this is caused by previous
> versions not have a goalPrefix set? Shouldn't the implementation handle this
> possibility?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8121) NullPointerException at org.apache.maven.artifact.repository.metadata.Metadata.merge (Metadata.java:293)
[
https://issues.apache.org/jira/browse/MNG-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846681#comment-17846681
]
Tamas Cservenak commented on MNG-8121:
--
Basically it boils down to this gist
https://gist.github.com/cstamas/69e6365bbb70521923020d68369bf8e5
> NullPointerException at
> org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
>
>
> Key: MNG-8121
> URL: https://issues.apache.org/jira/browse/MNG-8121
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.9.6
> Environment: Maven 3.9.6
> maven-plugin-plugin 3.13.0
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13
>Reporter: Gili
>Priority: Major
>
> TL;DR {{org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)}} throws {{NullPointerException}} if previous releases of
> a plugin did not have a goalPrefix set.
>
> At least, this is my interpretation of what is going on.
>
> Background
> -
>
> I have an open-source project at
> [https://github.com/cmake-maven-project/cmake-maven-project/tree/v3.27.1-b1]
> with the following coordinates:
>
> com.googlecode.cmake-maven-project
> cmake
>
> If I upgrade "maven-plugin-plugin" from version 3.10.1 to 3.13.0 I am forced
> to set "" because of
> https://issues.apache.org/jira/browse/MPLUGIN-450 and
> [https://github.com/apache/maven-plugin-tools/commit/ed4774bcd8b8d2d1f7ff1196cf7644054cb3ae14#diff-624cbd32cd7fc0f3f9154fbec92b8a1aebb04614360b4a0b5fc28a407e99d743L96]
>
> In my particular case, I set "cmake-binaries" inside
> cmake-binaries-plugin/pom.xml.
> Now, when I try deploying a release to Maven Central I get the following
> exception stack trace:
>
>
> {noformat}
> java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge
> (Metadata.java:293)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
> (AbstractRepositoryMetadata.java:99)
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
> (AbstractRepositoryMetadata.java:59)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge
> (MetadataBridge.java:56)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload
> (DefaultDeployer.java:399)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:294)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy
> (DefaultDeployer.java:202)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy
> (DefaultRepositorySystem.java:393)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> (DefaultArtifactDeployer.java:131)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.AbstractDeployStrategy.deployUp
> (AbstractDeployStrategy.java:213)
> at
> org.sonatype.nexus.maven.staging.deploy.strategy.StagingDeployStrategy.finalizeDeploy
> (StagingDeployStrategy.java:125)
> at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute
> (DeployMojo.java:213)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126){noformat}
>
> I assume that this is caused by {{preExisting.getPrefix()}} returning null,
> but I have no idea why this is happening. Perhaps this is caused by previous
> versions not have a goalPrefix set? Shouldn't the implementation handle this
> possibility?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
