[jira] [Commented] (MNG-7187) Maven should not attempt to download the jar when pom
[
https://issues.apache.org/jira/browse/MNG-7187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382575#comment-17382575
]
Michael Osipov commented on MNG-7187:
-
Please provide an upate to the relocation guide.
> Maven should not attempt to download the jar when pom
>
>
> Key: MNG-7187
> URL: https://issues.apache.org/jira/browse/MNG-7187
> Project: Maven
> Issue Type: Improvement
>Reporter: S L
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> Hello,
> maybe a corner case of what exactly should be part of a "relocation pom"
> ([https://maven.apache.org/guides/mini/guide-relocation.html]), but I created
> a release just consisting of the relocation-info
> ([https://repo1.maven.org/maven2/pl/project13/maven/git-commit-id-plugin/4.9.9/git-commit-id-plugin-4.9.9.pom])
> as type `pom` (since I only wanted to publish the
> relocation information).
> Using this depdendency.e.g. via:
> {code}
>
>
>
> pl.project13.maven
> git-commit-id-plugin
> 4.9.9
>
>
>
> {code}
> yields in the incorrect attempt of downloading a JAR-File from the new
> repository location:
> {code}
> [INFO] Building Git Commit Id Plugin Maven Mojo Debugging 0.0.3-SNAPSHOT
> [1/3]
> [INFO] [ pom
> ]-
> Downloading from central-secure:
> https://repo.maven.apache.org/maven2/io/github/git-commit-id/git-commit-id-maven-plugin/4.9.9/git-commit-id-maven-plugin-4.9.9.pom
> [WARNING] The POM for
> io.github.git-commit-id:git-commit-id-maven-plugin:jar:4.9.9 is missing, no
> dependency information available
> Downloading from central-secure:
> https://repo.maven.apache.org/maven2/io/github/git-commit-id/git-commit-id-maven-plugin/4.9.9/git-commit-id-maven-plugin-4.9.9.jar
> [INFO]
>
> [INFO] Reactor Summary for Git Commit Id Plugin Maven Mojo Debugging
> 0.0.3-SNAPSHOT:
> [INFO]
> [INFO] Git Commit Id Plugin Maven Mojo Debugging .. FAILURE [ 0.850
> s]
> [INFO] submodule-one .. SKIPPED
> [INFO] submodule-two .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.000 s
> [INFO] Finished at: 2021-07-12T21:42:15+02:00
> [INFO]
>
> [ERROR] Plugin pl.project13.maven:git-commit-id-plugin:4.9.9 or one of its
> dependencies could not be resolved: Could not find artifact
> io.github.git-commit-id:git-commit-id-maven-plugin:jar:4.9.9 in
> central-secure (https://repo.maven.apache.org/maven2) -> [Help 1]
> {code}
> IMHO Maven should not even try to search for a jar when
> `pom`. Simply raise an error that the package was
> relocated. the new location is at least detected, since it tries to download
> the artifact from a new location.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7187) Maven should not attempt to download the jar when pom
[
https://issues.apache.org/jira/browse/MNG-7187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381540#comment-17381540
]
S L commented on MNG-7187:
--
I have published a jar under the new location which fixes the issue. So I guess
the only remaining item is to enhance the relocation-guide.
>From this tiny experiment I believe the relocation can be one of the following
>publication-types:
1) A (full) publication with a jar and a pom stating the relocation
2) A pom-only publication pointing to the new location, however the jar is
residing under the new location
Mine is now a 2). But that should perhaps be better explained. I would be happy
to provide input on that.
> Maven should not attempt to download the jar when pom
>
>
> Key: MNG-7187
> URL: https://issues.apache.org/jira/browse/MNG-7187
> Project: Maven
> Issue Type: Improvement
>Reporter: S L
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> Hello,
> maybe a corner case of what exactly should be part of a "relocation pom"
> ([https://maven.apache.org/guides/mini/guide-relocation.html]), but I created
> a release just consisting of the relocation-info
> ([https://repo1.maven.org/maven2/pl/project13/maven/git-commit-id-plugin/4.9.9/git-commit-id-plugin-4.9.9.pom])
> as type `pom` (since I only wanted to publish the
> relocation information).
> Using this depdendency.e.g. via:
> {code}
>
>
>
> pl.project13.maven
> git-commit-id-plugin
> 4.9.9
>
>
>
> {code}
> yields in the incorrect attempt of downloading a JAR-File from the new
> repository location:
> {code}
> [INFO] Building Git Commit Id Plugin Maven Mojo Debugging 0.0.3-SNAPSHOT
> [1/3]
> [INFO] [ pom
> ]-
> Downloading from central-secure:
> https://repo.maven.apache.org/maven2/io/github/git-commit-id/git-commit-id-maven-plugin/4.9.9/git-commit-id-maven-plugin-4.9.9.pom
> [WARNING] The POM for
> io.github.git-commit-id:git-commit-id-maven-plugin:jar:4.9.9 is missing, no
> dependency information available
> Downloading from central-secure:
> https://repo.maven.apache.org/maven2/io/github/git-commit-id/git-commit-id-maven-plugin/4.9.9/git-commit-id-maven-plugin-4.9.9.jar
> [INFO]
>
> [INFO] Reactor Summary for Git Commit Id Plugin Maven Mojo Debugging
> 0.0.3-SNAPSHOT:
> [INFO]
> [INFO] Git Commit Id Plugin Maven Mojo Debugging .. FAILURE [ 0.850
> s]
> [INFO] submodule-one .. SKIPPED
> [INFO] submodule-two .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.000 s
> [INFO] Finished at: 2021-07-12T21:42:15+02:00
> [INFO]
>
> [ERROR] Plugin pl.project13.maven:git-commit-id-plugin:4.9.9 or one of its
> dependencies could not be resolved: Could not find artifact
> io.github.git-commit-id:git-commit-id-maven-plugin:jar:4.9.9 in
> central-secure (https://repo.maven.apache.org/maven2) -> [Help 1]
> {code}
> IMHO Maven should not even try to search for a jar when
> `pom`. Simply raise an error that the package was
> relocated. the new location is at least detected, since it tries to download
> the artifact from a new location.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7187) Maven should not attempt to download the jar when pom
[
https://issues.apache.org/jira/browse/MNG-7187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17379400#comment-17379400
]
Michael Osipov commented on MNG-7187:
-
Can you covert this to a simple test case?
> Maven should not attempt to download the jar when pom
>
>
> Key: MNG-7187
> URL: https://issues.apache.org/jira/browse/MNG-7187
> Project: Maven
> Issue Type: Improvement
>Reporter: S L
>Priority: Major
>
> Hello,
> maybe a corner case of what exactly should be part of a "relocation pom"
> ([https://maven.apache.org/guides/mini/guide-relocation.html]), but I created
> a release just consisting of the relocation-info
> ([https://repo1.maven.org/maven2/pl/project13/maven/git-commit-id-plugin/4.9.9/git-commit-id-plugin-4.9.9.pom])
> as type `pom` (since I only wanted to publish the
> relocation information).
> Using this depdendency.e.g. via:
> {code}
>
>
>
> pl.project13.maven
> git-commit-id-plugin
> 4.9.9
>
>
>
> {code}
> yields in the incorrect attempt of downloading a JAR-File from the new
> repository location:
> {code}
> [INFO] Building Git Commit Id Plugin Maven Mojo Debugging 0.0.3-SNAPSHOT
> [1/3]
> [INFO] [ pom
> ]-
> Downloading from central-secure:
> https://repo.maven.apache.org/maven2/io/github/git-commit-id/git-commit-id-maven-plugin/4.9.9/git-commit-id-maven-plugin-4.9.9.pom
> [WARNING] The POM for
> io.github.git-commit-id:git-commit-id-maven-plugin:jar:4.9.9 is missing, no
> dependency information available
> Downloading from central-secure:
> https://repo.maven.apache.org/maven2/io/github/git-commit-id/git-commit-id-maven-plugin/4.9.9/git-commit-id-maven-plugin-4.9.9.jar
> [INFO]
>
> [INFO] Reactor Summary for Git Commit Id Plugin Maven Mojo Debugging
> 0.0.3-SNAPSHOT:
> [INFO]
> [INFO] Git Commit Id Plugin Maven Mojo Debugging .. FAILURE [ 0.850
> s]
> [INFO] submodule-one .. SKIPPED
> [INFO] submodule-two .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.000 s
> [INFO] Finished at: 2021-07-12T21:42:15+02:00
> [INFO]
>
> [ERROR] Plugin pl.project13.maven:git-commit-id-plugin:4.9.9 or one of its
> dependencies could not be resolved: Could not find artifact
> io.github.git-commit-id:git-commit-id-maven-plugin:jar:4.9.9 in
> central-secure (https://repo.maven.apache.org/maven2) -> [Help 1]
> {code}
> IMHO Maven should not even try to search for a jar when
> `pom`. Simply raise an error that the package was
> relocated. the new location is at least detected, since it tries to download
> the artifact from a new location.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
