You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Ignore the nexus proxy, I do not think it is relevant)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 27.891 s
[INFO] Finished at: 2021-06-17T15:09:11+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project quarkus-admin-starter: Could not resolve dependencies for project com.github.adminfaces:quarkus-admin-starter:jar:1.0-SNAPSHOT: Failed to collect dependencies at com.github.adminfaces:quarkus-omnifaces:jar:1.0.1: Failed to read artifact descriptor for com.github.adminfaces:quarkus-omnifaces:jar:1.0.1: Could not find artifact com.github.adminfaces:quarkus-omnifaces-parent:pom:1.0.1 in nexus (http://nexus3:8081/repository/public/) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
Updating the pom to use version 1.1.0 or 1.4.0 seems to solve the problem.
perhaps something wrong with the 1.0.1 pom in the public maven repo?
The text was updated successfully, but these errors were encountered:
escay
changed the title
Omnifaces dependency 1.0.1 does not work, 1.4.0 seems to work
quarkus-omnifaces dependency 1.0.1 does not work, 1.4.0 seems to work
Jun 17, 2021
Building with a clean maven repo seems to fail.
To reproduce:
(Ignore the nexus proxy, I do not think it is relevant)
Updating the pom to use version 1.1.0 or 1.4.0 seems to solve the problem.
perhaps something wrong with the 1.0.1 pom in the public maven repo?
The text was updated successfully, but these errors were encountered: