Skip to content

Latest commit

 

History

History
36 lines (32 loc) · 2.45 KB

Contributing.md

File metadata and controls

36 lines (32 loc) · 2.45 KB
Raw

How to start development

  • call npm install
  • right-click on the package.json and call install dependencies
  • go to Run and Debug perspective (Ctrl+Shift+D)
  • select Launch Camel LSP client Extension
  • click on the "green arrow"

When testing new version of the Camel Language Server, just replace the jar in jars folder respecting the name language-server.jar

How to provide a new version on VS Code Marketplace and Open VSX Registry

  • Check that the version in package.json has not been published yet
    • If already published:
      • Run npm version --no-git-tag-version patch so that the version is updated
      • Push changes in a PR
      • Wait for PR to be merged
  • Point to a release version of Camel Language Server. During development it can point to snapshots but for release it must be a released version.
    • The version used is mentioned in scripts/postinstall.js
    • If a new release of Camel Language Server must be done, see how to release it documentation
    • To update the version from a SNAPSHOT to a released version, the Maven repository must be updated. You can check the file history to see how it was done.
  • Check that someone listed as submitter in Jenkinsfile is available
  • Create a tag
  • Push the tag to camel-tooling/camel-lsp-client-vscode repository
  • Start build on Jenkins CI with publishToMarketPlace and publishToOVSX parameters checked
  • Wait the build is waiting on step Publish to Marketplace
  • For someone from submitter list:
    • Ensure you are logged in
    • Go to the console log of the build and click Proceed
  • Wait few minutes and check that it has been published on VS Code Marketplace and Open VSX Marketplace
  • Keep build forever for later reference and edit build information to indicate the version
  • Prepare next iteration:
    • Run npm version --no-git-tag-version patch to update the version
    • Push changes in a PR
    • Follow PR until it is approved/merged
  • It is often interesting to move to next SNAPSHOT version of the Camel Language Server