Re: Jde Xref problem
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 a digitally signed message part
RE: Problem with jde-ant-build
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= buildfile "")) (setq ant-command
(concat ant-command
" -buildfile " delimiter
(jde-normalize-path buildfile)
delimiter)))
`delimiter' is set to single
quote.
Putting quotes around the value of the -buildfile
parameter also causes the same problem when running `ant' directly from the
command line with zsh, bash and cmd. It just seems a bug to be adding the
single quotes.
When I delete the 2 occurrences of `delimiter' from the
above snippet, it works fine.
--- John
From: Brian Rumple [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 19:36To: John Cooper;
[EMAIL PROTECTED]Subject: RE: Problem with
jde-ant-build
I have had this problem a long time in the past and I
wasn't sure the exact solution that I used. I don't think that it is a
code issue, but probably a configuration one.
Do you have jde-cygwin-path-converter set? Mine
is set like '(jde-cygwin-path-converter (quote
(jde-cygwin-path-converter-internal)))
I also believe that set jde-ant-buildfile would be more
appropriate than setting buildfile, but maybe you have a good reason for
it.
-Brian
From: John Cooper
[mailto:[EMAIL PROTECTED] Sent: Tuesday, August 17, 2004
1:56 PMTo: Brian Rumple; John Cooper;
[EMAIL PROTECTED]Subject: RE: Problem with
jde-ant-build
Unfortunately the patch doesn't make any difference for me,
because the setq is only done when bulidfile is null, andmy buildfile is
set to "c:/javabld/build.xml". I think the problem is that buildfile is later
being surrounded by quotes (the value of the delimiter
variable).
--- John
From: Brian Rumple [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 18:37To: John Cooper;
[EMAIL PROTECTED]Subject: RE: Problem with
jde-ant-build
I made a change to the jde-ant.el file that I believe
solves this problem. The diff is below:
Index:
lisp/jde-ant.el===RCS
file: /pack/anoncvs/jde/lisp/jde-ant.el,vretrieving revision 1.72diff
-r1.72 jde-ant.el246c246 (setq buildfile
jde-ant-buildfile))--- (setq buildfile
(jde-normalize-path jde-ant-buildfile)))
From: John Cooper
[mailto:[EMAIL PROTECTED] Sent: Tuesday, August 17, 2004
12:38 PMTo: '[EMAIL PROTECTED]'Subject: Problem with
jde-ant-build
[I'm using jde 2.3.4beta5]
jde-ant-build fails for me, with the following error:
cd h:/elisp/jde-2.3.4beta5/lisp/ ant -Dant.home=c:/javabld/ant -buildfile 'c:/javabld/build.xml'
-emacs -Dbuild.compiler.emacs=true clean
Buildfile: 'c:\javabld\build.xml' does not exist!
Build failed
Compilation finished at Tue Aug 17 17:33:18
I have jde-ant-invocation-method set to the default value
("Script"). To get it working, I had to remove the use
of `delimiter' in the following section of jde-build-ant-command:
(if (not (string= buildfile ""))
(setq ant-command
(concat ant-command
" -buildfile " delimiter
(jde-normalize-path buildfile)
delimiter)))
I use cygwin zsh as my cmd line shell (Windows XP), and passing
the single quotes to ant also cause the same error:
$ ant -Dant.home=c:/javabld/ant -buildfile
\'c:/javabld/build.xml\' -emacs -Dbuild.compiler.emacs=true clean
Buildfile: 'c:\javabld\build.xml' does not exist!
Build failed
I also have the following set in my .emacs: explicit-sh-args nil
shell-execute-helper "shelex.exe"
shell-file-name "cmdproxy"
Should delimer be removed from here, or are there some
circumstances where it is required?
--- John
Re: Jde Xref problem
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 stuff by the jde-usages plugin? While I really think jde-xref is cool, maybe we should think about integrating jde-usages itself... jtl
Re: Jde Xref problem
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 equivalent of jde-xref-first-caller and jde-xref-next-caller because I didn't use them. But there is a function which moves to the next usage line in the *usages* buffer and hits enter. I shall make the buffer name customizable and add functions to allow navigation between the usages without popping up the *usages* buffer. Also I find that having most of the code in java does not make for a pleasant experience while developing. I'm constantly restarting the bsh process to test new changes. I'm considering using beanshell functions instead of straight java code for parts of the project. Right now, I am, as time permits, working on two subprojects: 1) Using qdox (http://qdox.codehaus.org/) to parse files in jde-sourcepath so that the class hierarchy and class navigation functions don't require the source to be compiled to work. I really need this because compiling my entire project at work from scratch takes more than an hour and during that time JDE can't help me much because the class files are not yet available. 2) Allowing jde-usages to return the same kind of class info structures that jde.util.Completion does. Plusses for this: a) a smaller beanshell process size, since there would be just one component that looked at class files, b) Since jde-usages doesn't keep the files in the classpath open across invocations, on windows it would allow me to delete jar files in the classpath without shutting down the beanshell process. c) You wouldn't have to, in theory, call jde-complete-flush-classinfo-cache manually if you built your project from outside of emacs. This would come at the cost of each completion being slower because of the extra time spent checking if the files in the classpath have changed, but I'm thinking of ways to make this check less aggressive and still useful. Suraj On Wed, 18 Aug 2004 06:29:32 -0400, Andrew Hyatt [EMAIL PROTECTED] wrote: 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 stuff by the jde-usages plugin? While I really think jde-xref is cool, maybe we should think about integrating jde-usages itself... jtl
