Chapter 12. Frequently Asked Questions
Prev | Antelope Users Guide, Version 3.5.1 | Next

## Chapter 12. Frequently Asked Questions

- When I try to use the <javac> task, I keep getting a "no compiler found" error, but I have JAVA_HOME set correctly. How can I fix this?

  Check two things: (1) make sure JAVA_HOME is really set correctly. Windows JDK installations by default set JAVA_HOME to point to the jre directory under your JDK installation. This is fine for running Java programs, but not for compiling. Set JAVA_HOME up one directory to point to the root of your JDK installation, not the jre directory. (2) make sure JAVA_HOME/bin is in your PATH. This is the directory that contains javac.

  Here are some example settings from my Windows 2000 computer:

      JAVA_HOME = c:\j2sdk1.4.1_02
      PATH = (path to windows,etc);c:\j2sdk1.4.1_02\bin;

- I'd like to assign a key to a target button when running Antelope as a jEdit plugin. Is there anyway I can do this?

  Mark Pollard and I worked out this solution:

  In jEdit, open a new buffer and paste this in:

      jEdit.saveAllBuffers(view, false);
      VFSManager.waitForRequests();
      ise.antelope.plugin.AntelopePlugin plugin =
      jEdit.getPlugin("ise.antelope.plugin.AntelopePlugin");
      plugin.executeTarget(view, plugin.getBuildFile(view), "compile");

  Replace 'compile' with the name of the target you want to run. Save it in your ${user.home}/.jedit/macros directory (on my Windows machine, this is c:\Documents and Settings\danson\.jedit\macros, on my Linux box, it's /home/danson/.jedit/macros). Name it whatever you want, but be sure to give it a .bsh extention.

  Depending on your jEdit version, it will either be automatically loaded or use the 'Macros' menu, then 'Rescan macros' item. Then under the 'Utilities' menu -> 'Global Options' -> 'Shortcuts', pick 'Macros' from the drop down box on the right, and assign a key to the macro you just saved.

  If you name your targets consistently across your build files, this will work well for the targets that you run a lot, like 'compile' and 'test'.

- I get out of memory errors when trying to run my build file in Antelope. How can I avoid this problem?

  If you are starting Antelope with the run.xml file, edit this file and adjust this line:

      <java classname="ise.antelope.app.Antelope" fork="true">

  to look like this:

      <java classname="ise.antelope.app.Antelope" fork="true" maxmemory="128m">

  Adjust the maxmemory attribute as needed for your build.

  If you are starting Antelope from command-line java, add the -Xmx parameter to the command line like this:

      java -Xmx128m -jar AntelopeApp_3.5.1.jar

- All the buttons disappeared from Antelope. How do I get them back?

  This means that you have an error in your build file and Antelope does not recognize it as valid xml. Usually the the output window will give some indication of the problem. Correct the build file and save it, and the buttons will reappear. (See the next question also.)

- My build file uses external entities to include standard targets and properties. When I try to open this build file, all the buttons disappear. How do I get them back?

  Antelope version 2.53 and earlier did not support external entities. Upgrade to a version later than 2.53. Also, be sure your external entities are declared correctly. This example is from the Ant FAQ:

      <?xml version="1.0"?>

      <!DOCTYPE project [
          <!ENTITY common SYSTEM "file:./common.xml">
      ]>

      <project name="test" default="test" basedir=".">

        <target name="setup">
          ...
        </target>

        &common;

        ...

      </project>

Prev | Up | Next
API for jEdit Plugin Developers | Home | Chapter 13. Support