|Table of Contents|
Having a a portable environment to easily share among developers using the zero footprint service approach if possible.
There is a working implementation of this for SiteMesh at the SiteMesh Wiki.
Let's try and do Eclipse using Java 64 but then have Tomcat 32-bit use Java 32-bit.
You want to download the portal (tar.gz for Linux, zip for Windows) version of Eclipse and not the installer.
Download Eclipse IDE for Java EE Developers.
Select a drive and directory your computer where you will be keeping everything. The Bonsai Framework uses,
- Right click
- Select "Show Package Contents"
- Go into the "Eclipse" folder
Setup Package Java
Download Oracle's JRE (Java Runtime Environment) and follow the manual Java setup instructions.
- Windows = C:\apps\eclipse\jre1.6.0_18
- Linux or Unix = /home/tpham/apps/eclipse/opt/jre1.6.0_18
- Mac OS X = same as Linux
Modify the eclipse.ini to point to your JRE with by adding -vm and a reference to Java.
# --------------------------- # Start Bonsai Framework # ----------------------- # Use local version of Java. # Note, these lines must come just before -vmwargs -vm /Users/tin.pham/apps/eclipse/opt/java/jre1.8.0_121.jre/Contents/Home/bin/java # ----------------------- # End Bonsai Framework # ---------------------------
Start Eclipse by running the Eclipse executable included with the release. In our example the directories would be,
There are two ways of fixing this.
Clicking to Add to GateKeeper Rules
By manually adding Eclipse, you can remove yourself in the future.
When time permits, I will do a capture of the all registered rules to see exactly what the new rule fingerprint looks like and document the process here.
Manually Adding Eclipse to GateKeeper Rules
|This would be the preferred method but I found it did not quite work right. I noticed a typo so need to try again on a fresh machine.|
su - setup.admin # My normal Mac User does not have sudo privileges, yours might. spctl --remove --label "eclipse" Eclipse.app # Eclipse.app is the Eclipse package.
Similar to Eclipse, Tomcat also is also packaged without an installer. For windows we download the x86 .zip and for Linux or Unix download the .tar.gz file. Following the Bonsai Framework standards, decompress to the following folder,
Configure Eclipse to Use Tomcat
Ok this is where we have a problem. Once the Tomcat instance is created there seems to be no way to dynamically specify the various classpath entries... double-click on the server, Overview, Open Launch configuration, Classpath.