- Right click your project
- Select Properties -> Builders
Then restart your Eclipse.
Welcome to KPME! If this is your first time setting up your environment, please ensure that you have administrator access to the computer, otherwise some portions of this guide may not work.
This page extends on KPME Developer Setup Guide, to include instructions for setting up KPME versions 2.0+. If you are setting up a workspace for projects earlier than V2.0, please refer to the original setup guide KPME Developer Setup Guide.
The following is a list of software that is essential to install in order to get a working KPME development environment up and running.
Follow the steps outlined by each bold heading below in order to configure the default development stack.
JAVA_HOMEto your environment variables and set it to the base directory of your installation (Example:
JAVA_HOME/binto your path.
M2_HOMEto your O.S. environment variables and set it to the base directory of your installation (Example:
M2_HOME/binto your path.
Note: You MUST use the variable name M2_HOME. The launch configuration files reference this environment variable at run-time, and will give you a class load error if it is not defined correctly in your environment.
(Optional) If you wish to change the location of your repository to something other than your home folder, create a file named "settings.xml" in USER_HOME/.m2 with the following contents, replacing the path with your preferred location:
The default database for KPME is MySQL 5.1 or above. While Oracle is also supported in releases, it is untested and therefore not ready for developers.
If you are on Linux or MacOSX, you need to set a parameter to force MySQL to store tables in lower case. To do this, go to
/etc/my.confand make sure the following is set:
The easiest way to set up databases and permissions is to do it via the command line, however you may wish to do this via your MySQL Workbench. Developers typically use two databases for their server and one database for their unit tests. The following table lists the default settings for these databases that will give the most minimal setup.
KPME Client Database
Rice Server Database
Unit Test Database
To configure the database from the command line, use the root user name and password you created during MySQL Server installation to log into your database server, then issue the following two commands for each row in the above table. Replace dbname with the entries from column "Schema/Name" and username and password from the corresponding Username and Password columns.
To configure the database using MySQL Workbench:
localhostand select the database you are editing, and click OK.
The default development environment for KPME is Eclipse 3.5 or above. Any flavor should be ok, but it is recommended to start out with the Eclipse IDE for Java Developers since it is small.
Go to your install directory and edit
eclipse.ini. You will need to add your JDK and other memory arguments to make sure your environment will run smoothly. The following has the recommended defaults but you may need to increase them in order to match your machine.
http://download.eclipse.org/releasesentry that matches your Eclipse version. Go to Collaboration and select all required Subversive entries.
Note: Only complete this step if using Eclipse 3.6 or below. Eclipse 3.7 and above have switched to an internal Maven implementation, m2e.
You will be loading the project into your workspace from a repository via the Subversive plugin.
trunkif you are not given any additional instructions.
kpme. Click Finish to begin the install process.
At this point, Subversive for Eclipse will begin the checkout process for KPME and create a new project in your workspace. When the checkout process is complete, do the following
kpmeproject and select Maven -> Enable Dependency Management.
Maven for Eclipse will download all the jars and files that are listed in the project POM's dependencies.
In your new project, go to
env/src/main/config and copy the config files in the folder into your
Now that we have our base project imported into our workspace, we also need to import each of the projects sub modules. This import will not create duplicate projects folders on disk, but rather derive themselves from the existing project.
You'll notice the disdain in the workspace with all the newly imported projects. With eclipse, we can employ the use of working sets to organize our workspace.
Optionally you can set up Working Sets in Eclipse using the steps described here:
src/main/scripts, right-click on the launch file KPME Jetty 7.launch and select Run As...and the file name.
At a command prompt:
1) Exclude from Path (best solution)
Sourcetab. ( It looks identical to Java Build Path Source tab )
Addbutton next to
Exclusion patternsbox and add the exclusion for the js folder.
Here is how configuration looks with the js folder removed from validation
Then restart your Eclipse.
Go to your install directory, then open the 'bin' folder and edit
idea64.vmoptions. You will want to increase the base memory settings, but the below should be a good starting point.
After intellij restarts, you should be presented with a gray (or black) window that looks similar to this:
Several run configurations can be set up to make life easier.
In the Run Configuration window (Run --> Edit Configurations), expand the Defaults, and select JUnit
Note: for this to work, Tomcat needs to be installed, or unzipped on your computer somewhere. You can then tell intellij where it is located by clicking "Configure" on the screen below. Additionally, you will need to copy the jdbc driver you are using to the Tomcat Servers "lib" directory.