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

Required information

When acquiring a too large chunk via the publisher so that no mempool is available the memory manager calls the error handler despite having a fitting enum value to return - AllocationError::RUNNING_OUT_OF_CHUNKS.

Maybe we could also add a new enum value called AllocationError::CHUNK_SIZE_TOO_LARGE and return this to the user. There is no need to call the error ha

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().