This section covers some of the problems that may occur when using Evolvica.
Evolvica does not behave as expected:
This is most likely a bug. The first (and only) thing to do is to take a look into the logfile.
The logfile is located at EvolvicaInstallDir/workspace/.metadata/.log. If something went wrong
exception traces and error messages are printed in this logfile. If you think you have discovered
a bug, describe the bug and attach the logfile and send an email to bugs@evolvica.org.
If you can reproduce the bug you can put Evolvica into debug mode to generate more log messages.
To do this create a file with the name ".log4j.xml" and put it in your home directory. The file
contains configuration data for Log4J, so if you're familiar with Log4J you can write such a
configuration file yourself. People not familiar with Log4J may use this configuration:
<?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd"> <log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/'> <logger name="evolvica"> <level value="debug"/> </logger> </log4j:configuration>
An own operator does not show up in the operator palette:
Make sure your operator contains a constructor that is public and does not take any parameters. Also ensure that you create a descriptor for your operator.
A property in an operator cannot be set or does not show up:
Make sure that there are appropriate get- and set-methods. They must take the right arguments and must be public.
Creating an algorithm ends up with the error message "Could not create editpart":
Make sure that the directory path where Evolvica is installed is not longer than 64 characters. It seems that the underlying Eclipse platform has a problem with such long paths.