camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [camel-quarkus] ppalaga commented on issue #1171: camel-quarkus-core throws exception
Date Thu, 30 Apr 2020 12:34:07 GMT

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



Mime
View raw message