Skip to Content

Changes for page Add a Jar Dependency

Last modified by Pascal Robert on 2010/10/03 00:50
From version 6.1
edited by Pascal Robert
on 2007/12/15 16:44
Change comment: There is no comment for this version
To version 8.1
edited by Pascal Robert
on 2010/10/03 00:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,7 +3,7 @@
3 3  Adding these to your project is very simple.
4 4  
5 5  1. By default WOLips will create a ##Libraries## folder in your project directory. Populate this with any jars you like.
6 -1. In Eclipse, right-click (or ctrl-click) on the jar and choose ##Build Path > Add to Build Path##. This simple adjusts your project classpath but doesn't affect your final build.
6 +1. In Eclipse, right-click (or ctrl-click) on the jar and choose ##Build Path > Add to Build Path##. This simply adjusts your project classpath but doesn't affect your final build.
7 7  1. For frameworks, you should turn on the Export checkbox in the build path window as hown below in Fig. 1. Doing so ensures that other WebObjects projects the reference the framework "see" the jar library in their Eclipse build path.
8 8  
9 9  {{info title="Fig. 1 Export jars when in a framework"}}
... ... @@ -11,22 +11,3 @@
11 11  !Picture 11.jpg!
12 12  
13 13  {{/info}}
14 -
15 -1. Adjust your ##build.xml## file to ensure that the jar is also embedded in ##Contents/Resources/Java## directory of the final build as below.
16 -
17 -Either add an include entry for each jar...
18 -
19 -{{noformat}}
20 -
21 -<target name="build.woapp" depends="setProps,init.build,compile">
22 - <...>
23 - <lib dir="Libraries">
24 - <include name="Add .jar's that should be copied in the woa."/>
25 - <exclude name="**/*.woa/**"/>
26 - </lib>
27 - </woapplication>
28 -</target>
29 -
30 -{{/noformat}}
31 -
32 -... or have a single ##<include name="**/**.jar"/>## to include all jars in the specified directory.