1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
<?xml version="1.0"?>
<document>
<properties>
<title>Migration To Velocity</title>
<author email="jvanzyl@zenplex.com">Velocity Documentation Team</author>
</properties>
<body>
<section name="Converting Templates">
<p>
Legacy documents are the bane of any software migration. The
Velocity Team has tried to ensure that existing templates can be
converted for use within Velocity in as painless a manner as
possible.
</p>
<p>
Currently there is only a WebMacro to Velocity template converter,
but there are plans for a Tea to Velocity template converter, and a
FreeMarker to Velocity template converter.
</p>
</section>
<section name="WebMacro to Velocity Template Converter">
<p>
The <code>convert-wm.sh</code> script in the <code>convert</code>
directory converts a single WebMacro template (<code>*.wm</code>) to
a Velocity template (<code>*.vm</code>), or converts an entire
directory structure of WebMacro templates to Velocity templates.
</p>
<p>
The <code>convert-wm.sh</code> script can convert a single WebMacro
template to a Velocity template.
</p>
<source><![CDATA[
./convert-wm.sh template.wm
]]></source>
<p>
This will produce a single Velocity template named
<code>template.vm</code> from the WebMacro template
<code>template.wm</code>. The original WebMacro template will be
preserved.
</p>
<p>
To convert an entire directory structure of WebMacro templates using
the <code>convert-wm.sh</code> script, simply include the directory
name instead of the template name, as indicated below.
</p>
<source><![CDATA[
./convert-wm.sh templates
]]></source>
<p>
This will produce a directory structure of templates named
<code>templates/[template].vm</code>. The original WebMacro templates
will be preserved during the conversion process.
</p>
</section>
</body>
</document>
|
