# Strange thing: metasfresh organizational repository has no entry for mandatory 5.159.1-21669+master de.metas.parent.general artifact **URL:** \ **Category:** Uncategorized\ **Created:** [December 22, 2020, 11:25pm UTC](https://forum.metasfresh.org/t/strange-thing-metasfresh-organizational-repository-has-no-entry-for-mandatory-5-159-1-21669-master-de-metas-parent-general-artifact/1972 "2020-12-22T23:25:35Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![alexbrugere](https://forum.metasfresh.org/user_avatar/forum.metasfresh.org/alexbrugere/32/785_2.png) [@alexbrugere](https://forum.metasfresh.org/u/alexbrugere)\ **Post date:** [December 22, 2020, 11:25pm UTC](https://forum.metasfresh.org/t/strange-thing-metasfresh-organizational-repository-has-no-entry-for-mandatory-5-159-1-21669-master-de-metas-parent-general-artifact/1972/1 "2020-12-22T23:25:35Z")
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](https://forum.metasfresh.org/t/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-util10-0-0/1968/2). 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](https://repo.metasfresh.com/repository/mvn-master/)) → [Help 1] And it clearly shows that [repo.metasfresh.com](http://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/](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: 1. 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. 2. 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? ---
**Author:** ![alexbrugere](https://forum.metasfresh.org/user_avatar/forum.metasfresh.org/alexbrugere/32/785_2.png) [@alexbrugere](https://forum.metasfresh.org/u/alexbrugere)\ **Post date:** [December 25, 2020, 9:17pm UTC](https://forum.metasfresh.org/t/strange-thing-metasfresh-organizational-repository-has-no-entry-for-mandatory-5-159-1-21669-master-de-metas-parent-general-artifact/1972/2 "2020-12-25T21:17:24Z")
From the maven log: > [INFO] Building jar: C:\Workspace-Brugere\metasfresh\backend\de.metas.adempiere.adempiere\migration\target\de.metas.adempiere.adempiere.migration-sql-10.0.0.jar > [INFO] > [INFO] — maven-assembly-plugin:3.0.0:single (make-postgresql-assembly) @ de.metas.adempiere.adempiere.migration-sql — > Downloading: [https://repository.apache.org/snapshots/de/metas/metasfresh-assemblies/maven-metadata.xml](https://repository.apache.org/snapshots/de/metas/metasfresh-assemblies/maven-metadata.xml) > Downloading: [https://repo.metasfresh.com/repository/mvn-master/de/metas/metasfresh-assemblies/maven-metadata.xml](https://repo.metasfresh.com/repository/mvn-master/de/metas/metasfresh-assemblies/maven-metadata.xml) > Downloaded: [https://repo.metasfresh.com/repository/mvn-master/de/metas/metasfresh-assemblies/maven-metadata.xml](https://repo.metasfresh.com/repository/mvn-master/de/metas/metasfresh-assemblies/maven-metadata.xml) (8.7 kB at 5.5 kB/s) > Downloading: [https://repo.metasfresh.com/repository/mvn-master/de/metas/de.metas.parent.general/5.159.1-21669+master/de.metas.parent.general-5.159.1-21669+master.pom](https://repo.metasfresh.com/repository/mvn-master/de/metas/de.metas.parent.general/5.159.1-21669+master/de.metas.parent.general-5.159.1-21669+master.pom) > Downloading: [https://repo.metasfresh.com/repository/mvn-master/de/metas/de.metas.parent.general/5.159.1-21672+master/de.metas.parent.general-5.159.1-21672+master.pom](https://repo.metasfresh.com/repository/mvn-master/de/metas/de.metas.parent.general/5.159.1-21672+master/de.metas.parent.general-5.159.1-21672+master.pom) I can see that the list of asseblies is available at: [https://repo.metasfresh.com/repository/mvn-master/de/metas/metasfresh-assemblies/maven-metadata.xml](https://repo.metasfresh.com/repository/mvn-master/de/metas/metasfresh-assemblies/maven-metadata.xml) and there is entry: > 5.159.1-21669+master And maven tries to fetch this resource (as well as some others) from [https://repo.metasfresh.com/repository/mvn-master/de/metas/de.metas.parent.general/5.159.1-21669+master/de.metas.parent.general-5.159.1-21669+master.pom](https://repo.metasfresh.com/repository/mvn-master/de/metas/de.metas.parent.general/5.159.1-21669+master/de.metas.parent.general-5.159.1-21669+master.pom) But, apparently - this resource is not available. Of course, I can try to save maven-metadala.xml in my local repository, edit edit, remove the missing entries and then I can see what will hapen. But well, there is no reason to do this… I am consulting SO about the best practices to resolve this issue with maven-assembly-plugin