This is an Eclipse project intended get you started with a debug environment for hacking on the Lucee 5 source code. Most of the environment is ready to go, however there are some additional steps you will need to take in order for you to begin debugging.
This guide is written with Eclipse 4.5.1 Mars in mind, but should be applicable to older versions.
Prerequisites:
Step 1: Import the Lucee 5 projects into your workspace
loader
and core
projects into your workspaceStep 2: Configure lucee-debug to use the current Maven version of Lucee
In order to load the dependency libraries properly, you must configure this project's pom.xml to use the specific version of Lucee that you have checked out into your workspace.
pom.xml
file in the loader
project. Find the version number for the project and copy it.pom.xml
in the lucee-debug
project and paste the lucee version number into the lucee.project.version
propertyJetty is extremely simple to get started, however, it dumps all the config into your project. To combat this, I've included .gitignore entries to keep all the extra junk from being accidentally committed.
Tomcat is a bit more setup, but it deploys your code outside the project folder for runtime, and auto-syncs the files, keeping your project a bit cleaner.
Step 3a: Add Lucee 5 projects to debug project's Deployment Assembly:
core
project from the list (the loader
project should already be added, but if not select it as well) - the core and loader projects must remain open in order to run the debug appStep 3b:
lucee-debug
project and click Debug As > Run on ServerCongrats! You are now able to begin hacking on the Lucee runtime code! Changes in either the loader
or core
projects should be hot-swapped in, although Eclipse will let you know if you need to restart the servlet container. You can also set breakpoints and do stop-debugging within Eclipse on the loader or core projects.