Changes for page Embedding WOFrameworks

Last modified by Gavin Eadie on 2011/07/29 18:09

From version 36.1
edited by Kieran Kelleher
on 2007/03/30 15:58
Change comment: There is no comment for this version
To version 39.1
edited by chuckhill
on 2007/01/11 15:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kieran
1 +XWiki.chuckhill
Content
... ... @@ -1,12 +5,8 @@
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 5  See also [[FrameworkSet>>WOProject-FrameworkSet]] documentation.
6 6  
7 7  Example for embedding WOFrameworks.
8 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.
5 +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.
10 10  
11 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 12  
... ... @@ -17,7 +17,7 @@
17 17  
18 18  {{code}}
19 19  
20 -<!-- package and go example-->
16 +<!-- package and go example-->
21 21  <frameworks root="../packageandgo/frameworks" embed="true">
22 22   <include name="*.framework"/>
23 23  </frameworks>
... ... @@ -24,11 +24,11 @@
24 24  
25 25  {{/code}}
26 26  
27 -2 compile target
23 +2 compile target
28 28  
29 29  {{code}}
30 -
31 -<!-- package and go example-->
26 +
27 +<!-- package and go example-->
32 32  <fileset dir="../packageandgo/frameworks">
33 33   <include name = "**/*.jar"/>
34 34  </fileset>
... ... @@ -35,6 +35,8 @@
35 35  
36 36  {{/code}}
37 37  
34 +
35 +
38 38  The [[^build.xml]] from the packageandgo folder:
39 39  
40 40  Just invoke ant in the packageandgo folder and grap the App from the applications folder within the packageandgo folder.