You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/04/30 09:45:42 UTC
[GitHub] [camel-quarkus] hakuseki opened a new issue #1171: camel-quarkus-core throws exception
hakuseki opened a new issue #1171:
URL: https://github.com/apache/camel-quarkus/issues/1171
Using 1.0.0-M6 or 1.0.0-M7 on 1.4.1.Final, **camel-quarkus-core** throws the following exception:
```
2020-04-30 11:24:03,079 ERROR [io.qua.dep.dev.DevModeMain] (main) Failed to start Quarkus: java.lang.NoSuchMethodError: 'void io.quarkus.builder.BuildChainBuilder.setClassLoader(java.lang.ClassLoader)'
at io.quarkus.deployment.QuarkusAugmentor.run(QuarkusAugmentor.java:92)
at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment(AugmentActionImpl.java:245)
at io.quarkus.runner.bootstrap.AugmentActionImpl.createInitialRuntimeApplication(AugmentActionImpl.java:130)
at io.quarkus.runner.bootstrap.AugmentActionImpl.createInitialRuntimeApplication(AugmentActionImpl.java:52)
at io.quarkus.deployment.dev.IsolatedDevModeMain.firstStart(IsolatedDevModeMain.java:61)
at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:265)
at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:40)
at io.quarkus.bootstrap.app.CuratedApplication.runInCl(CuratedApplication.java:129)
at io.quarkus.bootstrap.app.CuratedApplication.runInAugmentClassLoader(CuratedApplication.java:82)
at io.quarkus.deployment.dev.DevModeMain.start(DevModeMain.java:116)
at io.quarkus.deployment.dev.DevModeMain.main(DevModeMain.java:56)
```
Removing camel-quartkus-core from dependencies removes this error.
Sample available here
https://github.com/hakuseki/CamelQuarkusDynamicHttp
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] lburgazzoli commented on issue #1171: camel-quarkus-core throws exception
Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on issue #1171:
URL: https://github.com/apache/camel-quarkus/issues/1171#issuecomment-621737595
yep but I think there is an issue as there's no quarkus platform that supports camel-quarkus m7 so there may be some conflicts with the version
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] lburgazzoli commented on issue #1171: camel-quarkus-core throws exception
Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on issue #1171:
URL: https://github.com/apache/camel-quarkus/issues/1171#issuecomment-621730065
1.0.0-M6 was tested against quarkus 1.3.1
there's a new release of camel quakrus 1.0.0-M7 that supports 1.4.1
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #1171: camel-quarkus-core throws exception
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1171:
URL: https://github.com/apache/camel-quarkus/issues/1171#issuecomment-621805132
Thanks for the feedback, @hakuseki !
Yes, this seems to be caused by maven choosing wrong paths to solve the dependency conflicts between the versions declared in camel-quarkus-bom 1.0.0-M7 and quarkus-universe-bom 1.4.1 (that in turn imports camel-quarkus-bom 1.0.0-M6).
I have found two ways, how to solve it:
(a) remove
```
<dependency>
<groupId>${quarkus.platform.group-id}</groupId>
<artifactId>${quarkus.platform.artifact-id}</artifactId>
<version>${quarkus.platform.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
```
You can do that, because camel-quarkus-bom imports quarkus-bom where all your quarkus deps are managed
(b) Move camel-quarkus-bom before quarkus-universe-bom in your pom, so that it gets a higher precedence.
```
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifactId>camel-quarkus-bom</artifactId>
<version>1.0.0-M7</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>${quarkus.platform.group-id}</groupId>
<artifactId>${quarkus.platform.artifact-id}</artifactId>
<version>${quarkus.platform.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
```
Universe 1.3.2 and CQ 1.0.0-M6 should be another valid combination:
```
<quarkus-plugin.version>1.3.2.Final</quarkus-plugin.version>
<quarkus.platform.artifact-id>quarkus-universe-bom</quarkus.platform.artifact-id>
<quarkus.platform.group-id>io.quarkus</quarkus.platform.group-id>
<quarkus.platform.version>1.3.2.Final</quarkus.platform.version>
<surefire-plugin.version>2.22.1</surefire-plugin.version>
</properties>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifactId>camel-quarkus-bom</artifactId>
<version>1.0.0-M6</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>${quarkus.platform.group-id}</groupId>
<artifactId>${quarkus.platform.artifact-id}</artifactId>
<version>${quarkus.platform.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
```
This kind of issues boils down to the problem of synchronization between our (Camel Quarkus) releases and Quarkus Universe releases. Quarkus Universe sometimes upgrades Quarkus without waiting for a compatible Camel Quarkus version. There is some testing in place, but dev mode tests are not part of it. Hence we should either find a way to test dev mode in the platform or we should bind our release schedule to Quarkus.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #1171: Dev mode does not work using platform 1.4.1
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1171:
URL: https://github.com/apache/camel-quarkus/issues/1171#issuecomment-623326803
Unless somebody has a better idea, I am going to try to
1. Create a new dev mode test to cover cases like the above
2. Make the platform to execute it.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] hakuseki commented on issue #1171: camel-quarkus-core throws exception
Posted by GitBox <gi...@apache.org>.
hakuseki commented on issue #1171:
URL: https://github.com/apache/camel-quarkus/issues/1171#issuecomment-621808300
Thank you, I moved the camel bom over quarkus and now it works
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #1171: Dev mode does not work using platform 1.4.1
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1171:
URL: https://github.com/apache/camel-quarkus/issues/1171#issuecomment-633452711
The platform's CI now runs a basic dev mode test https://github.com/quarkusio/quarkus-platform/pull/64
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] hakuseki commented on issue #1171: camel-quarkus-core throws exception
Posted by GitBox <gi...@apache.org>.
hakuseki commented on issue #1171:
URL: https://github.com/apache/camel-quarkus/issues/1171#issuecomment-621731211
> 1.0.0-M6 was tested against quarkus 1.3.1
> there's a new release of camel quakrus 1.0.0-M7 that supports 1.4.1
Yes, I know, tested on 1.4.1.Final
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga closed issue #1171: Dev mode does not work using platform 1.4.1
Posted by GitBox <gi...@apache.org>.
ppalaga closed issue #1171:
URL: https://github.com/apache/camel-quarkus/issues/1171
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org