unable to use without Groovy about malabar-mode

[m0smith]

Two things to try:

First, make sure groovy-mode is installed. Do not use the marmalade version as it is old.
Second, run malabar-run-groovy to get the java process started.

If neither of those suggestions help, please post more of the errors.

[doublep]

Installed groovy-mode, it went without problems. Tried to reinstall malabar-mode, got the same errors as before. malabar-run-groovy is not available, so I grepped and found it in malabar-mode.el. Evalling that buffer fails with "eval-buffer: Cannot open load file: No such file or directory, ede/maven2" even though package ede is listed as built-in.

Note that I don't use marmalade, I used melpa from standard Emacs package list (M-x package-list-packages). It shows that version 20150428.1004 is available, which matches the last commit date as I can see.

[doublep]

Full list of installation errors: http://paste.ubuntu.com/11097691/

[doublep]

The first warning is unrelated, it is due to a defadvice in my .emacs.

[fvbock]

having the same issue. installed latest groovy-mode and malabar-mode from melpa. didnt see any compile errors. getting the same error:
eval-buffer: Cannot open load file: no such file or directory, ede/maven2

any idea what else could be missing?

[liuzhishan]

the reason of "Cannot open load file: no such file or directory, ede/maven" might be that built-in cedet is already loaded, so that the cedet from https://github.com/alexott/cedet/tree/devel is not loaded.

try the following steps to load the needed cedet, not the built-in cedet. hope it helps.

1. try to use "make clean-all" and then "make all" in the cedet directory. make sure it doesnt have errors.
2. then put the (load-file "/path/to/cedet-devel-load.el") in the beginning of init.el.
3. restart emacs.

[glasserc]

I hit the same errors following the instructions on https://github.com/m0smith/malabar-mode#installation. gvmtool is now called sdkman, and the directory previously called ~/.gvm/groovy is now in ~/.sdkman/candidates/groovy. The malabar-variables module was trying to look around in this file to find current versions of groovy and so on, which was causing compilation to fail on a bunch of files. As a workaround you can do ln -s ~/.sdkman/candidates/ ~/.gvm.