Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

malabar-run-maven-command - nothing happens #71

lmdic opened this Issue Oct 4, 2011 · 1 comment


None yet
2 participants

lmdic commented Oct 4, 2011

my .emacs

(add-to-list 'load-path (expand-file-name "~/site-lisp/malabar-1.5-SNAPSHOT/lisp"))

(require 'cedet)
(semantic-load-enable-minimum-features) ;; or enable more if you wish
(require 'malabar-mode)
(setq malabar-groovy-lib-dir "~/site-lisp/malabar-1.5-SNAPSHOT/lib")
(add-to-list 'auto-mode-alist '(".java'" . malabar-mode))

;;(optional) If you want to mimic the IDEish compile-on-save behaviour, add the following as well::
(add-hook 'malabar-mode-hook
(lambda ()
(add-hook 'after-save-hook 'malabar-compile-file-silently
nil t)))

but when I try to e.g. start maven package by:


nothing happens

Show empty buffer Malabar Compilation

The buffer Malabar Groovy has the next content

compile-server: port=56758
eval-server: port=56759
Groovy Shell (1.7.4, JVM: 1.6.0_13)
Type 'help' or '\h' for help.

groovy:[] 000>


m0smith commented Dec 10, 2013

Version 1.5.1-SNAPSHOT seems to fix this problem

@m0smith m0smith closed this Dec 10, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment