Classpath entries set using the Eclipse Run Configuration Classpath tab do not appear to take effect when the run configuration (aka .launch file) is run. Specifically, we use the "Add Projects..." feature of the .launch configuration editor (Run Configuration) to add dependent projects from the same Eclipse workspace to the runtime classpath. This feature works for other app servers (i.e. JBoss) but not for Glassfish. The .launch files created by the Glassfish plugin have the classpath entries in the .launch file, but don't appear to make it to the runtime classpath of Glassfish.