Installation and initial setup of RapidClipse

1. RapidClipse does not start.

Possible causes:

  1. System does not meet the minimum requirements needed by RapidClipse

    1. Ensure that sufficient RAM memory and processor power are available.

  2. Incorrect download or corrupted files

    1. Download the archive or installer again and try again

  3. User does not have the necessary rights to launch the application

    1. Start RapidClipse as administrator

    2. Unpack the RapidClipse archive to a location where the future user has sufficient rights.

  4. Missing internet connection

    1. Make sure that your computer is connected to the Internet.

    2. Verify that RapidClipse has sufficient permissions to load required content through the firewall or a proxy.

General problem solving:

  1. Starting the IDE via PowerShell:

    1. Change to the installation directory of RapidClipse

    2. File → Open Windows PowerShell or pressed Shift key + right click in the installation folder → "Open PowerShell window here ".

    3. Enter the following command ".\rapidclipse.exe".

    4. Any errors should now be displayed to you on the command line

  2. Starting the IDE in "Clean Mode

    1. Starting the IDE via PowerShell looks above

    2. Enter the following command ".\rapidclipse.exe -clean".

3. Internet or firewall settings.

RapidClipse and especially Maven require a constant Internet connection for smooth operation. So make sure that your computer has a sufficient internet connection.

If you need special proxy settings, define them in the menu Windows > Preferences > General > Network Connections.

image not found

4. Use of special characters.

Do not use special characters or umlauts for subsequent elements:

  • RapidClipse

    • Directories for RapidClipse IDE

    • Workspaces which the IDE will use later on

  • Project

    • Project or package name

    • Otherwise the Java code conventions apply to all projects

5. Settings and notes for the workspace.

  1. Never put the workspace on a network drive.

  2. For the name of the workspace do not use special characters or umlauts.

  3. Never use a particular workspace with multiple different RapidClipse installations

  4. Never share a particular workspace with multiple colleagues

  5. Do not edit or delete files in the workspace manually or via Windows Explorer.

  6. The workspace has a directory named ".metadata" which contains all meta information of the IDE.

    1. Colors, Themes, Arrangements

    2. Database connections

    3. Plugins installed

    4. Included projects with their classes and files

    5. Included repositories with all information

  7. This directory is always regenerated when the IDE is started, if it does not already exist. It happens that errors creep into this metadata over time or due to crashes. Then it can be useful to create a new workspace or to delete the folder ".metadata". Please remember to export important elements such as database connections beforehand so that you can import them again later in the new workspace.

6. Performance problems within the IDE.

There are a number of external influences that have a negative impact on the performance of the IDE. Below is a list of the most serious errors and possible solutions to them.

  1. Insufficient system performance in general (processor, graphics card)

    1. Basically, it must be said that RapidClipse / Eclipse are highly complex development tools. They have to manage thousands of files and processes in the background.

    2. Especially with RapidClipse and the UI Builder, it is also a very complex graphic design tool. It has been shown that a mid-range graphics card can definitely bring the performance of the rendering in the UI Builder.

  2. Not enough RAM memory. RapidClipse usually needs between 4 - 6 GB depending on the project size when working with it permanently.

    1. Expand the RAM memory of your system

    2. Close unneeded projects regularly or do not keep them open in project management all the time

    3. Restart RapidClipse at regular intervals

    4. Allocate additional memory to RapidClipse via the "RapidClipse.ini" in the installation directory

      1. To do this, increase the values -Xms1024m -Xmx4096m at the end to -Xms4096m -Xmx8192m.

  3. On access scans of the virus scanner. Due to the fact that RapidClipse has to compile, move and check files constantly in the background, such scans have a massive impact on the performance of the IDE.

    1. Add exception rules for your workspaces and IDE directories so that they are not scanned again and again

    2. Or disable the virus scanner for certain areas

  4. Installed plugins in RapidClipse. Generally, RapidClipse is delivered with a minimum required setup of plugins and addons. This setup is checked by us regularly and adjusted if necessary. Each additional plugin that is installed by the later user can negatively influence the performance of the IDE. In many cases we observe that plugins do not "get along" with each other which leads to errors and poor performance of the IDE. Therefore, check regularly which addons you really need and which can be deleted.

  5. Activated functions in RapidClipse. Activated functions which start processes in the background of course also need resources. This includes e.g. Windows → Preferences → Validations.

    1. You should therefore regularly check which processes, checks and validations you really need in the background. Because these also require a not inconsiderable amount of system performance.

7. No access to the supplied H2 test database.

Release port 5435 via menu Windows > Preferences > XDEV > Sample Database. If port 5435 is already in use, change it.

image not found