Re: [jdee-devel] [jdee-users] Call to Fork or simply for JDEE TODO items
Brought to you by:
paullandes
From: Shyamal P. <sh...@me...> - 2013-05-01 23:58:22
|
>>>>> "Paul" == Paul Landes <la...@ma...> writes: Paul> My thinking is that maven will be a dependency. JDEE Paul> supporting ant, maven, javac compilations is one huge Paul> contributing reason for its bloat. You mean drop ant/javac support? That would be a no-no in my mind. I need all three :-) The ant support is, IMHO, fantastic. Maven actually "works" for me right now, though I have to set up my prj.el file manually. In my init.el I do (require 'jde) (require 'compile) (add-to-list 'compilation-error-regexp-alist 'maven) (add-to-list 'compilation-error-regexp-alist-alist '(maven "\\(^/.+?\\):\\[\\([0-9]+\\),\\([0-9]+\\)\\].*" 1 2 3)) since Maven, unlike ant, does not support an -emacs flag. Then in my prj.el file (at the same level as pom.xml) I add something like (setq compile-command "mvn -f ~/path/to/pom.xml compile assembly:single") and off I go with M-x compile. If JDEE would build my prj.el from pom.xml I would have everything I need (and there are *many* such .el files I've found around the interwebs, I beliee we just need to get a reliable version integrated). Cheers! Shyamal |