Maybe OT, but does anybody know what feature the normal jde-xref has
that isn't done faster and without all the db stuff by the jde-usages
plugin? While I really think jde-xref is cool, maybe we should think
about integrating jde-usages itself...
jtl
signature.asc
Description: This is
Title: Problem with jde-ant-build
I have the default value for jde-cygwin-path-converter,
which is the same as yours.
This isn't a path problem anyway - the problem is that
jde-build-ant-command puts quotes around the value specified for the -buildfile
parameter:
(if (not (string=
I think jde-usages is a perfectly acceptable replacement, and there is
really no difference in functionality as far as I know.
On Aug 18, 2004, at 4:08 AM, Jens Lautenbacher wrote:
Maybe OT, but does anybody know what feature the normal jde-xref has
that isn't done faster and without all the db
There are no missing pieces in jde-usages as far as I know too, but it
does some things
differently, based on my personal preference:
1) Instead of creating a new buffer each time you call one of the
usage functions, jde-usages just reuses one buffer called *usages*
2) I did not implement the
