Skip to Content

Changes for page Embedding WOFrameworks

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

Summary

Details

Page properties
Content
... ... @@ -1,38 +1,11 @@
1 -Example for embedding WOFrameworks.
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).
2 2  
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.
3 +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 -[[image:Folders.png]]
7 +The packageandgobuild.xml from the application. One minor change to the default build.xml:
8 8  
9 -The [[^packageandgobuild.xml]] from the application. Two minor changes to the default build.xml:
10 -1 application target
9 +The build.xml from the packageandgo folder:
11 11  
12 -{{code}}
13 -
14 -<!-- package and go example-->
15 -<frameworks root="../packageandgo/frameworks" embed="true">
16 - <include name="*.framework"/>
17 -</frameworks>
18 -
19 -{{/code}}
20 -
21 -2 compile target
22 -
23 -{{code}}
24 -
25 -<!-- package and go example-->
26 -<fileset dir="../packageandgo/frameworks">
27 - <include name = "**/*.jar"/>
28 -</fileset>
29 -
30 -{{/code}}
31 -
32 -
33 -
34 -The [[^build.xml]] from the packageandgo folder:
35 -
36 -Just invoke ant in the packageandgo folder and grap the App from applications folder within the packageandgo folder.
37 -
38 -[[image:FoldersAfterBuild.png]]
11 +Just invoke ant in the packageandgo folder and grap the App from applications folder within the packageandgo folder