[
https://issues.apache.org/jira/browse/CAMEL-25422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-25422.
---------------------------------
Resolution: Fixed
> camel-jbang - camel run pom.xml runs a Quarkus project as Camel Main when the
> BOM coordinates are properties
> ------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25422
> URL: https://issues.apache.org/jira/browse/CAMEL-25422
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.23.0
>
>
> camel run pom.xml on a Quarkus project generated by code.quarkus.io (for
> example camel-quarkus-examples/timer-log) prints "Running Camel Main project"
> and runs mvn camel:run, which fails:
> {noformat}
> [ERROR] No plugin found for prefix 'camel' in the current project and in the
> plugin groups [io.quarkus.platform, ...]
> {noformat}
> RunHelper.detectRuntimeFromPom compares the artifactIds of
> dependencyManagement as written, but these poms declare the BOMs with
> properties:
> {code:xml}
> <groupId>${quarkus.platform.group-id}</groupId>
> <artifactId>${quarkus.platform.artifact-id}</artifactId>
> {code}
> so quarkus-bom / quarkus-camel-bom is never matched and the runtime falls
> back to Camel Main. The project properties should be resolved before the
> comparison (and the io.quarkus.platform quarkus-maven-plugin can be a sign of
> Quarkus too). The same detection is used when an opened Maven project is run
> from the monitor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
