ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@bost.de>
Subject Re: Ant and Emacs compilation
Date Tue, 25 Jul 2000 08:15:30 GMT
I use the following in my JDE setup in ~/.emacs:

(require 'compile)
(setq compilation-error-regexp-alist
      (append (list 
               ;; works for jikes
               '("^\\s-*\\[[^]]*\\]\\s-*\\(.+\\):\\([0-9]+\\):\\([0-9]+\\):[0-9]+:[0-9]+:"
1 2 3)
               ;; works for javac 
               ;; thanks to Barrie Treloar <Barrie.Treloar@camtech.com.au>
               '("^\\s-*\\[[^]]*\\]\\s-*\\(.+\\):\\([0-9]+\\):" 1 2))
      compilation-error-regexp-alist))

Both regexps work whether [javac] is present or not, this means the
first one solves the problem XEmacs has with jikes +E as well.

The jikes version needs to be prepended to the list because the (4bsd
gnu) regexp seems to match (badly) in XEmacs' compile.el but doesn't
parse the message correctly.

As for other editors - we probably need a way to not use DefaultLogger
and add a PlainLogger. While the second is possible, the first one is
not yet.

On a side note. How are you invoking Ant from JDE?

I'm currently switching between two approaches

(1) an approach Peter Donald has posted to this list, which requires
me to modify an elisp variable to switch between projects and adds a
key sequence to jde-mode-map to invoke Ant.

(2) write a shell script in each directory that changes the working
dir to my projects basedir, invokes ant with the arguments I might
have supplied and changes back the directory. Say "compile using make"
and set the compilation command to the name of my shell script.

I'm not thrilled by each of these ways.

Stefan

Mime
View raw message