jvanzyl 01/09/15 08:42:26
Modified: src/tdk build.xml
Log:
- flux now works again: wasn't catching the different versions of flux.
templates are now copied too so the sample app works as it always has
in classic mode and in cvslayout mode.
Revision Changes Path
1.8 +11 -1 jakarta-turbine-tdk/src/tdk/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-tdk/src/tdk/build.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- build.xml 2001/09/15 01:46:31 1.7
+++ build.xml 2001/09/15 15:42:26 1.8
@@ -149,17 +149,27 @@
<!-- Right now these are stored in Turbine's CVS but eventually -->
<!-- they will probably become part of the TDK. -->
<!-- ================================================================= -->
-
+
+ <!-- FIX: this is a problem that will need a more elegant solution.
+ We need to make sure that when version N of turbine is used
+ that the corresponding turbine jar files and all subapps
+ base on that version N are copied while versions not of N
+ are not. We just need a more general way to deal with versioned
+ subapps. This may not be a serious problem as flux is the only
+ real app regularly used in conjunction with a turbine application. -->
+
<target name="libs">
<copy todir="webapps/${turbine.app}/WEB-INF/lib">
<fileset dir="${lib.dir}">
<exclude name="turbine*.jar"/>
+ <exclude name="flux*.jar"/>
</fileset>
</copy>
<copy todir="webapps/${turbine.app}/WEB-INF/lib">
<fileset dir="${lib.dir}">
<include name="turbine-${turbine.version}*.jar"/>
+ <include name="flux-${turbine.version}*.jar"/>
</fileset>
</copy>
</target>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
