Skip to content

Conversation

rastislavpapp
Copy link
Collaborator

property placeholders instyle of ${...}, in blueprint xml files

@davsclaus
Copy link
Collaborator

This style with ${ } is also the same for classic Spring <beans> XML files. Would you be able to add that also in a new PR?

@davsclaus
Copy link
Collaborator

And also remember to update the changelog in plugin.xml

@rastislavpapp
Copy link
Collaborator Author

And also remember to update the changelog in plugin.xml

I've managed not to forget this time :-)

This style with ${ } is also the same for classic Spring XML files. Would you be able to add that also in a new PR?

This should already be handled by spring plugin itself. Which is part of Ultimate, and I don't know how would Jetbrains react to us replicating ultimate features in a CE plugin :-)
I've actually thought about whether the blueprint support should be a part of this camel plugin or should be split into a separate blueprint plugin, because it does not really have anything to do with camel :-) but there's some overlap (e.g. knowing about blueprint beans we can interact with them in @BeanInject etc. But it could be possible to have some kind of inter-plugin communication, or awareness.

@davsclaus
Copy link
Collaborator

osgi blueprint is dead - its only camel karaf users that use it - so it doe not make sense to build new plugins

you can add a [x] in settings to turn this on | off then users can enable this that do not use ultimate version (which is also a lot of users)

@davsclaus davsclaus merged commit 1cfd675 into camel-tooling:main Aug 22, 2025
3 checks passed
@rastislavpapp rastislavpapp deleted the blueprint_property_placeholders branch August 22, 2025 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants