Skip to content

Maven CLI: use recipes for platform extensions #36568

@JiriOndrusek

Description

@JiriOndrusek

Describe the bug

With the recent change #34391, the migration detects extensions of the migrated application. Recipes for the detected extensions are executed during the update.

The list of the extensions is filtered for simple version updates (see code and code). This condition filteres out camel-quarkus-core extension (which is part of the platform) and therefore does not upgrade the camel-quarkus code.

Expected behavior

Recipes for camel-quarkus extensions should be applied if camel-quarkus-core dependency is present (and part of the platform)

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/cliRelated to quarkus cli (not maven/gradle/etc.)area/mavenkind/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions