|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (11)
View Page History| h2. Objective |
| {toc} |
| |
| h1. Objective |
| Link Eclipse WO project directly to Project Wonder frameworks source instead of the installed Wonder binaries. |
| h21. Prerequisites |
| Import the Wonder projects from local checked out cvs source tree into your workspace: [Wonder:Working With Wonder Source in Eclipse] |
| h21. Procedure |
| * Edit the Build Path on your Project. (Right-click your project \-> Build Path/Configure Build Path...) |
| {panel:bgColor=#FFFFFF} {info} |
| !JavaBuildPathProjectsTab.jpg|align=center! |
| {panel} {info} |
| * Go to the Projects tab and Add Project References to the ERExtensions, Ajax, or other checked-out Project Wonder projects. |
| {panel:bgColor=#FFFFFF} {info} |
| !SelectProjectsToAdd.jpg|align=center! |
| {panel} {info} |
| * Go to the Build Order tab and move the project references (typically default to the bottom) up above the WO Frameworks library by multiple selecting those cvs projects and clicking 'Up'. This will cause Eclipse to resolve Project Wonder references from the Eclipse project first, before the frameworks. |
| {panel:bgColor=#FFFFFF} {info} |
| !JavaBuildPath.jpg|align=center! |
| {panel} {info} |
| * So what does this procedure actually do? Well, it changes the file named ".classpath" that resides in your project directory. If you use a version control system, such as Subversion (which you should use), you will see that this is the file that changed upon your next commit attempt. |