You don't have a jde-autoload because your build failed. This file is generated from the build itself.
You're have a lot of issues on a platform that's been tested and working for others. I have a feeling this might be your environment.
What version of ant are you using?
On Oct 1, 2011, at 2:45 PM, Olivier Lefevre wrote:
> On 10/1/2011 9:14 PM, Paul Landes wrote:
>> Did you add a "-D"?
> No. I added it to build.properties so as to have a written record
> of the tweak. Now with -D it worked. But what is build.properties
> for, then???
> Next problem is that "ant dist" fails because there is no dist target;
> I assume it is package instead. You need to update doc/flat/install.html
> That failed, too, with
> C:\tmp\jdee-20110110\jdee\build.xml:210: Problem: failed to create task or type changelog
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:481)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:413)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:160)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at org.apache.tools.ant.Target.performTasks(Target.java:385)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
> at org.apache.tools.ant.Main.runBuild(Main.java:698)
> at org.apache.tools.ant.Main.startAnt(Main.java:199)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
> These archives are merely a convenience, though, so I moved on to install,
> which succeeded. I then removed the old site-lisp/jde-126.96.36.199, updated my
> .emacs file, started emacs (no more errors), loaded a Java file and got:
> Debugger entered--Lisp error: (file-error "Cannot open load file" "jde-autoload")
> eval-buffer(#<buffer *load*<2>> nil "c:/emacs/23.3/site-lisp/jdee-20110110/lisp/jde.el" nil t) ; Reading at buffer position 2769
> load-with-code-conversion("c:/emacs/23.3/site-lisp/jdee-20110110/lisp/jde.el" "c:/emacs/23.3/site-lisp/jdee-20110110/lisp/jde.el" nil t)
> eval-buffer(#<buffer *load*> nil "c:/emacs/23.3/.emacs" nil t) ; Reading at buffer position 2429
> load-with-code-conversion("c:/emacs/23.3/.emacs" "c:/emacs/23.3/.emacs" nil t)
> load("c:/emacs/23.3/.emacs" nil t)
> command-line-1(("-l" "c:\\emacs\\23.3\\.emacs"))
> There is indeed no jde-autoload.el, whether in the sources or under
> -- O.L.
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> jdee-users mailing list