[
https://issues.apache.org/jira/browse/MRELEASE-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mani Sarkar updated MRELEASE-912:
---------------------------------
Description:
I get the below error message when trying to download the artefact:
....Could not find artifact gamesys:gamesys-parent:pom:1.12.5 in
internal-repository (https://nexus.gamesys.co.uk/content/groups/all-thirdparty,
this is not the repo where it should look for artefacts.
There are two other repos in the list of repos, i.e. {{release}} and
{{snapshots}}, instead of searching there, it searches in the
{{all-thirdparty}} one.
This renders the whole release process unsuccessful.
Is there a version where this issue is resolved ?
was:
I get the below error message when trying to download the artefact:
....Could not find artifact gamesys:gamesys-parent:pom:1.12.5 in
internal-repository (https://nexus.gamesys.co.uk/content/groups/all-thirdparty,
this is not the repo where it should look for artefacts.
There are two other repos in the list of repos, i.e. {{release}} and
{{snapshots}}, instead of searching there, it searches in the
{{all-thirdparty}} one.
> mvn release plugin is trying to download artefacts from the incorrect repo
> --------------------------------------------------------------------------
>
> Key: MRELEASE-912
> URL: https://issues.apache.org/jira/browse/MRELEASE-912
> Project: Maven Release Plugin
> Issue Type: Bug
> Affects Versions: 2.5.2
> Environment: MacOS, Bamboo
> Reporter: Mani Sarkar
>
> I get the below error message when trying to download the artefact:
> ....Could not find artifact gamesys:gamesys-parent:pom:1.12.5 in
> internal-repository
> (https://nexus.gamesys.co.uk/content/groups/all-thirdparty, this is not the
> repo where it should look for artefacts.
> There are two other repos in the list of repos, i.e. {{release}} and
> {{snapshots}}, instead of searching there, it searches in the
> {{all-thirdparty}} one.
> This renders the whole release process unsuccessful.
> Is there a version where this issue is resolved ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
