File: build.html

package info (click to toggle)
jswat2 2.37-1
  • links: PTS
  • area: contrib
  • in suites: etch, etch-m68k
  • size: 7,092 kB
  • ctags: 5,592
  • sloc: java: 43,576; xml: 1,086; sh: 66; makefile: 57
file content (73 lines) | stat: -rw-r--r-- 2,887 bytes parent folder | download
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
73
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta name="generator" content=
  "HTML Tidy for Linux/x86 (vers 1st February 2004), see www.w3.org" />

  <title>JSwat - How to Build JSwat</title>
</head>

<body style="background-color: #fff">
  <h2>How to Build JSwat</h2>

  <h3>Requirements</h3>

  <p>You will need the the latest version of the <a href=
  "http://ant.apache.org/">Apache Ant</a> tool. This Java tool makes
  building a JSwat distribution very easy. Download and install Ant
  before continuing.</p>

  <h3>Making the Build</h3>

  <p>Building a JSwat binary or source package with Ant is very
  straight-forward. First, download and install Ant, which is really
  quite easy. Next, invoke Ant from the directory containing the JSwat
  <code>build.xml</code> file. This will run the default target which
  should make the source and binary packages. The distributions are
  packed in <code>.tar.gz</code> and <code>.zip</code> files. The
  <code>.tar.gz</code> files are compressed tape archive files, common
  on Unix platforms, while the <code>.zip</code> files are popular on
  Windows platforms.</p>

  <h3>Testing the Build</h3>

  <p>Testing the build is pretty straightforward. Extract the files
  from the archive created during the build process described above,
  then start JSwat as described in the <code>README.html</code> file.
  The general idea is to make sure the JSwat jar file contains all the
  necessary classes and resource bundles. If any errors occur you may
  want to check that the <code>build.xml</code> includes all of the
  necessary files for JSwat to run properly.</p>

  <p>Some ideas for what to test:</p>

  <ul>
    <li>Access the help files. Search the help for a keyword, like
    &quot;session&quot;.</li>

    <li>Access the command help. Search for a keyword using
    &#39;<code>apropos</code>&#39;.</li>

    <li>Set the language to Japanese to test the translation.</li>

    <li>Open a Java source file, ensuring that the Java parser is
    activated, to confirm that the Java parser library is
    included.</li>
  </ul>

  <h3>Releasing the Build</h3>

  <p>All of the <code>.tar.gz</code> and <code>.zip</code> files should
  now be uploaded to the SourceForge <a href=
  "http://sourceforge.net/projects/jswat/">project</a> site. If you do
  not know how this is done, see the <a href=
  "http://sourceforge.net/">SourceForge</a> documentation. Be sure to
  notify the people watching the project so they know of the new
  release. Once this is done, visit the Freshmeat <a href=
  "http://freshmeat.net/projects/jswat/">project</a> page and add a new
  release there. And finally, send out an email to the jswat-announce
  mailing list with the list of changes in this release.</p>
</body>
</html>