Eclipse.ini is a text file containing command-line options that are added to the command line used when Eclipse is started up. There are many options available, please see here. Important: You can, and should, experiment with changes to the launch command from your Command Prompt/Terminal before changing the eclipse.ini itself.
Checkout Source and Create Project. File → New → Project → Checkout Maven Projects From SCM.
For SCM, choose 'svn' and browse to the project. In older versions of the m2eclipse Eclipse plugin (prior to 0.11.0), you have an option to place all modules within a single project; this feature is. Click Advanced, and uncheck 'separate projects for modules' (if that doesn't exist, change m2eclipse setting in Window → Preferences → Maven → Support multiple maven modules). Click Finish to download and create the Maven project(s). Note: If you get the following error while trying to check out the code, switch the SVN URL from http to https.
(i.e. ) checkout -r HEAD -depth=infinity -force RA layer request failed svn: REPORT of '/!svn/vcc/default': Could not read status line: connection was closed by server Develop with Maven There are five projects shown in the workspace: openmrs, openmrs-api, openmrs-test, openmrs-tools, openmrs-web, and openmrs-webapp. The openmrs project is a parent project.
When we run any maven goal on the parent project, it will run the same goal on its children, according to the dependency order. A Maven menu item is added on the context menu, which lets you modify the pom.xml, manage dependencies and plugins, etc. Common maven goals are also added on the menu items Run As and Debug As. You can also create your own Maven Run Configurations.
How to run the build. Right click the openmrs project to bring up the context menu, select 'Run as → Maven build.' (notice the '.' At the end). Enter the Goals: clean install. Make sure the Maven Runtime at the bottom is correct for your installation (Configure for Embedded/External as necessary). Select Apply, then Run.
The build output will be displayed in the Console. The output contains links to the results of each test. To re-run the build, right click the root project to bring up the context menu, select 'Run as - Maven build.' If you have multiple configurations, select the 'clean install' one to run.
To manage these configurations, right click the root project to bring up the context menu, select 'Run as - Run configurations.' Select the configuration under the Maven Build section. Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m -XX:NewSize=128m If on running, you get error messages including this: 'java.net.BindException: Address already in use', most likely the default 8080 port is in use. You may want to change to any other different port for jetty.
For instance if you want to change to port 8081, then on the JRE tab, in the VM parameters box, add something like this: -Djetty.port=8081 See or or Jetty is currently configured to reload static resources like jsp, javascript files, etc. Changes to Java classes will require recompiling and restarting Jetty. (run maven:compile goal (if auto build is not enabled) and restart Jetty). How to Profile Web Application with YourKit Set up a run configuration as specified in 'How to Run Web Application' but in the JRE tab, set the -agentpath VM option as specified in the. Common values:. Linux x86, 32-bit Java: -agentpath:/bin/linux-x86-32/libyjpagent.so.
Mac OS X: -agentpath:/bin/mac/libyjpagent.jnilib. Windows, 32-bit Java: -agentpath: bin win32 yjpagent.dll (This assumes you have YourKit installed already.) How to Debug Web Application Jetty plugin can pick up any changes of static resources, so changes of jsp, property or css files don't require a restart. However changes of java class will have to restart. The following solutions could help in some situations. Not yet documented. Use JRebel Here is how you configure JRebel to work with OpenMRS.
Download JRebel and install it. Install JRebel plugin for Eclipse and restart. Configure JRebel plugin for Eclipse. Specify location of JRebel installation Tick 'Use Step filters' and also add com.zeroturnaround.
and org.zeroturnaround. to the filters Tick 'filter synthetic fields'. Configure JRebel Agent Setting provided by JRebel installation Untick 'Spring Framework Plugin'. Change 'OpenMRS' Run configuration to increase Permgen and enable JRebel. Run or Debug 'OpenMRS' When you change any java classes, just wait for eclipse auto build to finish, reload the web page, and JRebel will reload the class for you. I have 64 bit Windows 7, I ran into a bunch of errors when trying to set up my development environment, including the one mentioned in the previous comment. Here is how I fixed them all.
At one point I didn't get Java HL working. So when I went to Window - Preferences and then Team - SVN, the SVN Interface: Client was blank.
I discovered that the SubVersion was 1.6 and the JavaHL was 1.7. According to the list 1.7 only works with 1.8 of SubVersion.
So my first attempt to fix was to put in the newer version of SubVersion (1.8). But then I discovered that Maven doesn't support the newer version. What I did to get this fixed was to download eclipse and start from scratch (I was unable to uninstall and then reinstall the correct versions). After getting a clean version of Eclipse, I clicked on the link to about how to download Java HL. The link for 64 bit windows was to. The trick though is to not install the version that it displays. You have to click on the link for 'Old Versions Are Available Here' which takes you to Then I installed the 64 bit (I have windows 7) version of '.
This worked with the 1.6 version of SubClipse which is the default (as of Feb 2012) in the Eclipse Market Place. The next error that I got was the one about the JRE. What I needed to do was download a JDK. If you read the instructions, it says you need a JDK, instead of a JRE. After installing the 1.6 JDK (off of Sun / Oracle we site), I set eclipse to use it via Windows - Preferences then Java - Installed JREs.
I clicked the Add button and added the JDK for 1.6 (by choosing the directory that it got installed to - for me that was C: Program Files Java jdk1.6.030) and then clicked the checkbox for it (mine was JDK1.6.030). That fixed the error that you mentioned about the JRE. The 3rd error that I got had to do with the fact that when I was trying to run the Jetty:Run that I set up via the instructions. I didn't put the base directory that they have in the picture. You need to change it to that exactly. If I had had this comment when I did my set up, it would have saved me a ton of time. I hope this helps other developers using 64 bit windows 7.