Changes for page Embedding WOFrameworks
Last modified by Gavin Eadie on 2011/07/29 18:09
From version 37.1
edited by Lachlan Deck
on 2007/01/15 02:55
on 2007/01/15 02:55
Change comment:
There is no comment for this version
To version 35.1
edited by Kieran Kelleher
on 2007/03/30 15:58
on 2007/03/30 15:58
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ldeck1 +XWiki.kieran - Content
-
... ... @@ -1,3 +1,7 @@ 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 + 1 1 See also [[FrameworkSet>>WOProject-FrameworkSet]] documentation. 2 2 3 3 Example for embedding WOFrameworks. ... ... @@ -13,7 +13,7 @@ 13 13 14 14 {{code}} 15 15 16 -<!-- package and go example--> 20 +<!-- package and go example--> 17 17 <frameworks root="../packageandgo/frameworks" embed="true"> 18 18 <include name="*.framework"/> 19 19 </frameworks> ... ... @@ -20,11 +20,11 @@ 20 20 21 21 {{/code}} 22 22 23 -2 compile target 27 +2 compile target 24 24 25 25 {{code}} 26 - 27 -<!-- package and go example--> 30 + 31 +<!-- package and go example--> 28 28 <fileset dir="../packageandgo/frameworks"> 29 29 <include name = "**/*.jar"/> 30 30 </fileset> ... ... @@ -31,8 +31,6 @@ 31 31 32 32 {{/code}} 33 33 34 - 35 - 36 36 The [[^build.xml]] from the packageandgo folder: 37 37 38 38 Just invoke ant in the packageandgo folder and grap the App from the applications folder within the packageandgo folder.