Skip to Content

Changes for page Embedding WOFrameworks

Last modified by Gavin Eadie on 2011/07/29 18:09
From version 38.1
edited by Lachlan Deck
on 2007/01/15 02:55
Change comment: There is no comment for this version
To version 44.1
edited by Ulrich Köster
on 2006/09/08 05:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ldeck
1 +XWiki.uli
Content
... ... @@ -1,15 +3,11 @@
1 -See also [[FrameworkSet>>WOProject-FrameworkSet]] documentation.
2 -
3 3  Example for embedding WOFrameworks.
4 4  
5 -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.
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.
6 6  
7 7  Assume two projects: One named Foo( a framework) and the other named Uli (an application). The parent folder has another folder named packandgo.
8 8  
9 -[[image:Folders.png]]
10 -
11 11  The [[^packageandgobuild.xml]] from the application. Two minor changes to the default build.xml:
12 -1 application target
8 +(Applied to the compile and application target.)
13 13  
14 14  {{code}}
15 15  
... ... @@ -20,21 +20,8 @@
20 20  
21 21  {{/code}}
22 22  
23 -2 compile target
19 +
24 24  
25 -{{code}}
26 -
27 -<!-- package and go example-->
28 -<fileset dir="../packageandgo/frameworks">
29 - <include name = "**/*.jar"/>
30 -</fileset>
31 -
32 -{{/code}}
33 -
34 -
35 -
36 36  The [[^build.xml]] from the packageandgo folder:
37 37  
38 -Just invoke ant in the packageandgo folder and grap the App from the applications folder within the packageandgo folder.
39 -
40 -[[image:FoldersAfterBuild.png]]
23 +Just invoke ant in the packageandgo folder and grap the App from applications folder within the packageandgo folder