Apache Ant makes the task of concatenating files together extremely easy by using concat.
<concat destfile="${build.dir}/concatenated.js">
<filelist dir="${src.dir}/js"
files="one.js, two.js"/>
</concat>
This is a simple solution but I chose not to use it for the following reasons:
1. I don't always want every single javascript/css to be included for all pages.
You could create multiple concatenated files with different combinations but that would be too messy.
2. We are creating a dependency between the jsps and the ant build script. Do you really want to do that?
3. Javascript, css can be notoriously difficult to debug, so for development purposes
it is useful not to do any concatenation.
Ant has a neat feature that allows to do string replacement on any file by using a filterset.
<copy file="${build.dir}/version.txt" toFile="${dist.dir}/version.txt">
<filterset>
<filter token="DATE" value="whatever"/>
</filterset>
</copy>
You can specify the string that you want to be replaced at build time by surrounding it with ampersands. So in the template jsps instead of including javascripts/css in the normal way, I did the following:
@IncludeCSS css/file1.css css/file2.css ...@
...
@IncludeJS js/jquery.js js/thickbox.js js/vmSlider.js js/blockUI.js@
Then I created the following ant task:
ExtendedFileTransform is a custom task I created, based on Julien Lecombte's File Transform.
<ExtendedFileTransform concatenate="true" propertiesfile="${build.dir}/static.mapping.properties" >
<jspfileset refid="jspFileset">
</jspfileset>
<staticfileset dir="${static_content.dir}">
<include name="**/*.js" />
<include name="**/*.css" />
<include name="**/*.png" />
<include name="**/*.jpg" />
<include name="**/*.jpeg" />
<include name="**/*.gif" />
<include name="**/*.PNG" />
<include name="**/*.JPG" />
<include name="**/*.GIF" />
</staticfileset>
</ExtendedFileTransform>
This custom task inspects all the jsps and searches for javascript(IncludeJS) and css includes(IncludeCSS). If concatenated="true" we concatenate the files specified within the IncludeXXX directory and we replace it with a valid html javascript/css include to the generated files. If concatenated="false", i.e. for development, there is no concatenation and the IncludeXXX directory is replaced with an include for each javascript/css file.
The full ant target that you could use for production looks like this:
<target name="-copy.static.files-prod">
<taskdef name="ExtendedFileTransform" classname="uk.co.simpletech.ant.ExtendedFileTransform" classpath="${build.dir}/classes" />
<mkdir dir="${build.dir}/staticpre" />
<!-- we copy all jsp files to a temporary location -->
<copy todir="${build.dir}/jsppre">
<fileset dir="jsp" includes="**/*" />
</copy>
<fileset dir="${build.dir}/jsppre" id="jspFileset">
<include name="**/*.jsp" />
</fileset>
<!-- we concatenate the files together -->
<ExtendedFileTransform concatenate="true">
<jspfileset refid="jspFileset">
</jspfileset>
<staticfileset dir="${build.dir}/static">
<include name="**/*.js" />
<include name="**/*.css" />
</staticfileset>
</ExtendedFileTransform>
<delete dir="${build.dir}/jsppre" />=
</target>
Here is an example project where you can see the css/js concatenation in action.
No comments:
Post a Comment