This my question is the continuation from Error building from maven on Windows: Failed to execute goal on project de.metas.util: Could not resolve dependencies for project de.metas.util:de.metas.util🫙10.0.0 - #2 by alexbrugere.
Actually the build process of the backend Java project is very robust, stable and reliable, if only one knows that 3 projects should be build and the command is, of course mvn install (not just mvn package).
But the strange thing is that nonetheless the build fails with error message:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single (make-postgresql-assembly) on project de.metas.adempiere.adempiere.migration-sql: Execution make-postgresql-assembly of goal org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single failed: Plugin org.apache.maven.plugins:maven-assembly-plugin:3.0.0 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-assembly-plugin:jar:3.0.0 → de.metas:metasfresh-assemblies:jar:5.159.1-21669+master: Failed to read artifact descriptor for de.metas:metasfresh-assemblies:jar:5.159.1-21669+master: Could not find artifact de.metas:de.metas.parent.general:pom:5.159.1-21669+master in metasfresh-repo (Repository - Sonatype Nexus Repository) → [Help 1]
And it clearly shows that repo.metasfresh.com can not be read.
And indeed - if I am browsing the repository:
https://repo.metasfresh.com/service/rest/repository/browse/mvn-master/de/metas/de.metas.parent.general/
then I can see artifacts for all releases and there are ones for
5.159.1-21668+master
and one for
5.159.1-21670+master
but there is no entry for 5.159.1-21669+master - as the build error shows!
So - I am stuck here.
I have 2 paths here:
- I will check that the generated build task indeed is generated correctly. Maybe it is generated incorrectly and the requirement for 5.159.1-21669+master is by error, by some strange change.
- Well, if all is correctly then I don’t know what to do. Of course, I can change the build process and to remove the requirement for 5.159.1-21669+master but this is very irrational behavior. How can I expect that the future processes do not rely on 5.159.1-21669+master?
It is strange thing that there are some other gaps too - like 5.159.1-21672+master, maybe it is OK. It is the issue of aesthetics, harmony and symmetry and irrelevant as such.
So… maybe there is some solution? Maybe one can update the organizational repository?