Details
-
Enhancement
-
Resolution: Unresolved
-
Major
-
9.0.0
-
None
-
None
Description
currently, we have a conflicting content-type which leads to several glitch (even if some of them are fixed with FUSETOOLS-2117 )
last one known: if importing a project, the camel spring file will open by default with Spring editor and not Camel one.
The solution that I can imagine is to provide 2 camel content-types, one extending the Spring beans content type and one for blueprint and java.
Attachments
Issue Links
- relates to
-
FUSETOOLS-2117 Camel tooling not compatible with Spring IDE
- Closed