Changes for page Embedding WOFrameworks
Last modified by Gavin Eadie on 2011/07/29 18:09
From version 44.1
edited by Ulrich Köster
on 2006/09/08 05:53
on 2006/09/08 05:53
Change comment:
There is no comment for this version
To version 39.1
edited by chuckhill
on 2007/01/11 15:18
on 2007/01/11 15:18
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.u li1 +XWiki.chuckhill - Content
-
... ... @@ -1,3 +1,5 @@ 1 +See also [[FrameworkSet>>WOProject-FrameworkSet]] documentation. 2 + 1 1 Example for embedding WOFrameworks. 2 2 3 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,8 +4,10 @@ 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 9 +[[image:Folders.png]] 10 + 7 7 The [[^packageandgobuild.xml]] from the application. Two minor changes to the default build.xml: 8 - (Appliedto the compileand application target.)12 +1 application target 9 9 10 10 {{code}} 11 11 ... ... @@ -16,8 +16,21 @@ 16 16 17 17 {{/code}} 18 18 19 - 23 +2 compile target 20 20 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 + 21 21 The [[^build.xml]] from the packageandgo folder: 22 22 23 -Just invoke ant in the packageandgo folder and grap the App from applications folder within the packageandgo folder 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]]