Skip to Content

Wiki source code of Embedding WOFrameworks

Version 35.1 by Kieran Kelleher on 2007/03/30 15:58
Show last authors
1 **Caveat:** This example assumes that each framework you want to embed has an ant build.xml file with a buildAndCompile target. For frameworks you create yourself using WOLips, you will have this, but for a case where you are checking out individual Wonder framework projects from CVS, then you probably will not have such a build.xml file, so this approach is not quick to implement in that case unless you want to spend a lot of time working on ant build files to resolve the missing build.xml having a buildAndCompile target for those external projects. (KK 3/30/2007)
2
3 ----
4
5 See also [[FrameworkSet>>WOProject-FrameworkSet]] documentation.
6
7 Example for embedding WOFrameworks.
8
9 It's often a good idea to create your own targets in the build.xml or even create your own build.xml (with a different name). This leaves the door open for an update of the default build.xml.
10
11 Assume two projects: One named Foo( a framework) and the other named Uli (an application). The parent folder has another folder named packandgo.
12
13 [[image:Folders.png]]
14
15 The [[^packageandgobuild.xml]] from the application. Two minor changes to the default build.xml:
16 1 application target
17
18 {{code}}
19
20 <!-- package and go example-->
21 <frameworks root="../packageandgo/frameworks" embed="true">
22 <include name="*.framework"/>
23 </frameworks>
24
25 {{/code}}
26
27 2 compile target
28
29 {{code}}
30
31 <!-- package and go example-->
32 <fileset dir="../packageandgo/frameworks">
33 <include name = "**/*.jar"/>
34 </fileset>
35
36 {{/code}}
37
38 The [[^build.xml]] from the packageandgo folder:
39
40 Just invoke ant in the packageandgo folder and grap the App from the applications folder within the packageandgo folder.
41
42 [[image:FoldersAfterBuild.png]]