-
Bug
-
Resolution: Done
-
Blocker
-
camel-quarkus-2.2-GA
-
None
-
False
-
False
-
%
-
CQ4
-
Todo
-
We have changed the maven repo generation strategy and we currently cannot compile all the supported extensions (we weren't even before, but now there are missing dependencies from RHBQ) e.g.:
- org.jsoup:jsoup:jar:1.14.2.redhat-00002
- io.quarkus:quarkus-project-core-extension-codestarts:jar:2.2.5.Final-redhat-00010
- io.quarkus:quarkus-devtools-common:jar:2.2.5.Final-redhat-00010
07:57:18 [ERROR] [ERROR] Some problems were encountered while processing the POMs: 07:57:18 [ERROR] Unresolveable build extension: Plugin io.quarkus:quarkus-maven-plugin:2.2.5.Final-redhat-00010 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.jsoup:jsoup:jar:1.14.2.redhat-00002, io.quarkus:quarkus-project-core-extension-codestarts:jar:2.2.5.Final-redhat-00010, io.quarkus:quarkus-devtools-common:jar:2.2.5.Final-redhat-00010: Could not find artifact org.jsoup:jsoup:jar:1.14.2.redhat-00002 in maven-central (https://repo.maven.apache.org/maven2) @ 07:57:18 @ 07:57:18 [ERROR] The build could not read 1 project -> [Help 1] 07:57:18 [ERROR] 07:57:18 [ERROR] The project org.apache.camel.quarkus.qe:camel-exts-for-quarkus-supported-extensions:1.0-snapshot (/mnt/hudson_workspace/workspace/camel-quarkus/rhi-cq-2.2/supported-extensions/workdir/pom.xml) has 1 error 07:57:18 [ERROR] Unresolveable build extension: Plugin io.quarkus:quarkus-maven-plugin:2.2.5.Final-redhat-00010 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.jsoup:jsoup:jar:1.14.2.redhat-00002, io.quarkus:quarkus-project-core-extension-codestarts:jar:2.2.5.Final-redhat-00010, io.quarkus:quarkus-devtools-common:jar:2.2.5.Final-redhat-00010: Could not find artifact org.jsoup:jsoup:jar:1.14.2.redhat-00002 in maven-central
There was a suggestion from ppalaga or janstey@redhat.com that we should use the RHBQ local maven repo zip. If we agree that this is the way, there are few action items for 2.2.1:
- probably Release Notes or update a documentation that we change the maven repo zip and that if customer wants to speed up the builds they should even use the corresponding one - (or maybe CEQ isn't affected, because we also have QP deliverables, but Camel K may be affected)
and for 2.7.0: - CEQ UMB message have to contain a link on a coresponding Quarkus Maven Repo