Warning: For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.
Introduction
To work with Wonder source in Eclipse we import, without copying, the source projects from the Wonder source tree we downloaded in an earlier tutorial. By doing so, we make sure our workspace Wonder source projects are the same source as what we have used for our build and install.
Prerequisites
Wonder source tree is checked out from source control: Getting the Wonder Source Code
Importing Wonder Projects into Eclipse
- Right-click in WO Explorer and select "Import..." from the context menu.
- The [panel] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.Select "Existing Projects into Workspace" as the import source. - The [panel] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.Click "Browse..." to select the root directory containing the projects. - The [panel] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.To import framework projects, for example, navigate to and select ".../Wonder/Frameworks" and click "Choose". - The [tip] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.The list of projects inside that folder appear checked. Uncheck the "Copy Projects into Workspace" checkbox and uncheck the projects you don't want and click "Finish". - The [panel] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.Eclipse will build the projects and you can now browse, inspect and use Wonder source in Eclipse.
WarningAnt Builds on your Development Machine
WOlips' "Incremental Builder" is an incredibly helpful feature during development, but it does things that the Ant deployment build does not do. If you are either using WOLips to build your WebObjects Applications (WOLips Ant Tools > Install) or are running Hudson/Jenkins locally to do it, you must also build and install your workspace's Frameworks that your Application depends upon – including your own, Project Wonder's and any others. The standard Ant build does NOT do this for you.