eclipse

Describe the bug

Some devfiles have several commands that need to be executed in a precise order to succeed.
Some are named with prefixed numbers that help the user, but some others are not.

For instance:

• angular
• python-django

Che version

• latest
• nightly
• other: please spec

Document the commands that clients should implement and their expected behaviour on https://github.com/eclipse/eclipse.jdt.ls/wiki/JDT-LS-Extensions

Brief feature description

The current posix wrapper are tested in a way that only the wrapper itself is used and tested with itself. If possible, we should call the posix calls directly in one part of a tests and verify that the posixWrapper behaves as intended when it works on the structure.

Detailed information

Consider the following:

void meth(Closure closure) {
  closure.|
}

When invoking content assist (Ctrl+Space) at |, the methods and properties of groovy.lang.Closure are very low in the list of proposals. This is due to very-well-known type adjustments made within org.codehaus.groovy.eclipse.codeassist.proposals.AbstractGroovyProposal.getRelevanceClass().