Update Docker LS to version 0.7.2

Approved as per
https://clearlydefined.io/definitions/npm/npmjs/-/dockerfile-language-server-nodejs/0.7.2
.
Changes in the LS since last update are:
- prevent infinite loop when calculating semantic tokens if an escape
character is not followed by any actual content
(https://github.com/rcjsuen/dockerfile-language-service/issues/95)
- prevent infinite loop when calculating semantic tokens if an escape
character is embedded within a variable
(https://github.com/rcjsuen/dockerfile-language-service/issues/96)
- textDocument/publishDiagnostics
  - prevent merging of instructions if it contains an escape character
and spans multiple lines
(https://github.com/rcjsuen/dockerfile-utils/issues/103)
  - ignore comments embedded in an instruction's keyword
(https://github.com/rcjsuen/dockerfile-utils/issues/104)
- textDocument/semanticTokens/full
  - prevent infinite loop when calculating semantic tokens for an
instruction with a keyword that spans multiple lines
(https://github.com/rcjsuen/dockerfile-language-service/issues/94)
- textDocument/publishDiagnostics
  - support BuildKit by ignoring RUN instructions with no arguments
(https://github.com/rcjsuen/dockerfile-utils/issues/102)
- textDocument/publishDiagnostics
  - duplicated escape parser directive errors will now only flag the
duplicates (https://github.com/rcjsuen/dockerfile-utils/issues/100)
  - duplicated CMD, ENTRYPOINT, and HEALTHCHECK instructions will no
longer flag the last one found as it is the valid one
(https://github.com/rcjsuen/dockerfile-utils/issues/101)
- textDocument/completion
  - consider escaped words when calculating prefixes for code completion
(https://github.com/rcjsuen/dockerfile-language-service/issues/60)
- textDocument/publishDiagnostics
  - fix incorrect merging of error ranges if escape character embedded
in the keyword (https://github.com/rcjsuen/dockerfile-utils/issues/99)
- textDocument/semanticTokens/full
  - prevent infinite loop when computing semantic tokens for a keyword
with an escape character
(https://github.com/rcjsuen/dockerfile-language-service/issues/91)
- textDocument/completion
  - process heredoc syntax correctly when deciding what completion items
to return for ADD and COPY
(https://github.com/rcjsuen/dockerfile-language-service/issues/90)
- textDocument/publishDiagnostics
  - flag duplicated escape parser directive declarations as being
unnecessary (https://github.com/rcjsuen/dockerfile-utils/issues/82)
  - flag duplicated CMD, ENTRYPOINT, and HEALTHCHECK instructions as
being unnecessary diagnostics
(https://github.com/rcjsuen/dockerfile-utils/issues/82)
  - support heredoc syntax in ADD and COPY instructions
(https://github.com/rcjsuen/dockerfile-utils/issues/98)

Change-Id: Ibd8414068402bb32b676a64def3ff4754eead292
Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
Reviewed-on: https://git.eclipse.org/r/c/linuxtools/org.eclipse.linuxtools/+/187583
Tested-by: Linux Tools Bot <linuxtools-bot@eclipse.org>
1 file changed
tree: 5736e75924c6f03aa7ea90df6497dbd1a00b89b0
  1. changelog/
  2. containers/
  3. gcov/
  4. gprof/
  5. javadocs/
  6. libhover/
  7. lttng/
  8. man/
  9. perf/
  10. profiling/
  11. releng/
  12. rpm/
  13. systemtap/
  14. vagrant/
  15. valgrind/
  16. .gitignore
  17. .project
  18. LICENSE
  19. pom.xml
  20. README.md
README.md

Contributing to Linux Tools

Thanks for your interest in this project.

Project description:

The Linux Tools project aims to bring a full-featured C and C++ IDE to Linux developers. We build on the source editing and debugging features of the CDT and integrate popular native development tools such as the GNU Autotools, Valgrind, OProfile, RPM, SystemTap, GCov, GProf, LTTng, etc. Current projects include LTTng trace viewers and analyzers, an RPM .spec editor, Autotools build integration, a Valgrind heap usage analysis tool, and OProfile call profiling tools. The project also provides a place for Linux distributions to collaboratively overcome issues surrounding distribution packaging of Eclipse technology. The project produces both best practices and tools related to packaging. One of our features is a source archive of the Eclipse SDK that can be used by all Linux distributions building and distributing it.

Developer resources:

Information regarding source code management, builds, coding standards, and more.

Eclipse Contributor Agreement:

Before your contribution can be accepted by the project team contributors must electronically sign the Eclipse Contributor Agreement (ECA).

Commits that are provided by non-committers must have a Signed-off-by field in the footer indicating that the author is aware of the terms by which the contribution has been provided to the project. The non-committer must additionally have an Eclipse Foundation account and must have a signed Eclipse Contributor Agreement (ECA) on file.

For more information, please see the Eclipse Committer Handbook: https://www.eclipse.org/projects/handbook/#resources-commit

Contact:

Contact the project developers via the project's “dev” list.

Search for bugs:

This project uses Bugzilla to track ongoing development and issues.

Create a new bug:

Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!