Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-19418

Development support for VS Code Language Support for Apache Camel extension

XMLWordPrintable

      Motivation

      Camel 3 products, Camel Extensions for Quarkus, Camel for Spring Boot and Camel K include developer tools with community support only.

      Red Hat cannot provide full “production” support for developer extensions on VSCode.

      Customers need support for developer tools, at least to file customer tickets and get fixes in the latest versions under best effort SLA.

      Goal

      Add development support for VS Code Language Support for Apache Camel extension

      Scenarios

      As a developer I need to install a supported Language support extension to VSCode so that I get language assistance when writing integrations in DSLs (Java, XML, Camel K)

      As a developer I need the language support for a specific Camel product version (Camel catalog version in Extension Settings, default latest, CEQ 2.7 -> Camel 3.14)

      Expected outcomes

      Continuous testing with productized Camel catalog

      Manual configuration of Camel catalog version in Extension Settings because most of the time it is complicated to set it automatically (there are some parts for which the version cannot be specified currently - traits for Camel K for instance)

      Remove preview tag from VS Code Language Support for Apache Camel extension https://marketplace.visualstudio.com/items?itemName=redhat.vscode-apache-camel 

      Document use of VS Code Language Support for Apache Camel extension including configuration to use the developer tool with specific product version(s)

      Add link to the development support notice to the documentation and supported configurations / components https://access.redhat.com/support/offerings/developer/soc 

              apupier@redhat.com Aurélien Pupier
              ibek1@redhat.com Ivo Bek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: