Skip to Content

Changes for page Embedding WOFrameworks

Last modified by Gavin Eadie on 2011/07/29 18:09
From version 48.1
edited by Ulrich Köster
on 2006/09/08 05:45
Change comment: There is no comment for this version
To version 51.1
edited by Ulrich Köster
on 2006/09/08 05:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,11 +1,33 @@
1 -A good idea is to create your own targets in the build.xml or even create your own build.xml (with a different name).
1 +Example for embedding WOFrameworks.
2 2  
3 -This leaves the door open for an update of the default build.xml.
3 +It's an good idea is 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.
4 4  
5 5  Assume two projects: One named Foo( a framework) and the other named Uli (an application). The parent folder has another folder named packandgo.
6 6  
7 -The packageandgobuild.xml from the application. One minor change to the default build.xml:
7 +The [[^packageandgobuild.xml]] from the application. Two minor changes to the default build.xml:
8 +1 application target
8 8  
9 -The build.xml from the packageandgo folder:
10 +{{code}}
10 10  
12 +<!-- package and go example-->
13 +<frameworks root="../packageandgo/frameworks" embed="true">
14 + <include name="*.framework"/>
15 +</frameworks>
16 +
17 +{{/code}}
18 +
19 +2 compile target
20 +
21 +{{code}}
22 +
23 +<fileset dir="../packageandgo/frameworks">
24 + <include name = "**/*.jar"/>
25 +</fileset>
26 +
27 +{{/code}}
28 +
29 +
30 +
31 +The [[^build.xml]] from the packageandgo folder:
32 +
11 11  Just invoke ant in the packageandgo folder and grap the App from applications folder within the packageandgo folder