Closed nbiancolin closed 1 month ago
Further digging reveals this only happens on packages from camel (eg. groupId is org.apache.camel
)
Closing this because I didn't realize I was using a deprecated package. (Camel swagger components are deprecated and I did not realize haha)
Describe the bug
When adding custom dependences (by adding
camel.jbang.dependencies=<<<>>>
to application.properties, it ignores the version provided and overwrites the version to 4.6.0, causing maven to not properly run or package the file. If I manually modify the pom.xml file, changing the version to the correct version (in this case, 3.2.2) and repackage it (without camel-jbang recompiling it) it functions as expected.Steps to reproduce the behavior
camel.jbang.dependencies=org.apache.camel:camel-rest-swagger:jar:3.22.2
toapplication.properties
.export/pom.xml
and see that the version has been overwritten to 4.6.0Variant
Vs Code Extension
Container Management (if applicable)
Docker
Operating System (if applicable)
Windows
Version
4.6.0
Relevant log output