Add Japanese l10N

git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@9254 71c3de6d-444a-0410-be80-ed276b4c234a

war/resources/help/ant/ant-buildfile_ja.html

+<div>
+  <!-- TODO:誰か訳して -->
+  If your build requires a custom <a href="http://ant.apache.org/manual/running.html#options">-buildfile</a>,
+  specify it here.  By default Ant will use the <code>build.xml</code> in the root directory, 
+  this option can be used to use build files with a different name or in a subdirectory.
+</div>

war/resources/help/ant/ant-opts_ja.html

+<div>
+  <!-- TODO:誰か訳して -->
+  If your build requires a custom <a href="http://ant.apache.org/manual/running.html#envvars">ANT_OPTS</a>,
+  specify it here.  Typically this may be used to specify java memory limits to use, for example <code>-Xmx512m</code>.
+  Note that other Ant options (such as <tt>-lib</tt>) should go to the "Ant targets" field.  
+</div>
\ No newline at end of file

war/resources/help/ant/ant-properties_ja.html

+<div>
+  <!-- TODO:誰か訳して -->
+  Properties needed by your ant build can be specified here (in the standard properties file format):
+  <pre># comment
+name1=value1
+name2=value2
+</pre>
+  These are passed to Ant like <tt>"-Dname1=value1 -Dname2=value2"</tt>
+</div>

war/resources/help/ant/ant-targets_ja.html

+<div>
+  <!-- TODO:誰か訳して -->
+  Specify a list of Ant targets to be invoked, or leave it empty to invoke the default Ant target
+  specified in the build script. Additionally, you can also this field to specify other Ant options. 
+</div>
\ No newline at end of file

war/resources/help/matrix/axes_ja.html

+<div>
+  <!-- TODO:誰か訳して -->
+  If your configuration matrix needs additional axes, you can specify them here.
+  <p>
+  For example, let's say you are trying to run a test for your database application,
+  and you need to test it with three databases: MySQL, PostgreSQL, and Oracle. Your
+  build script is designed so that you can test with a particular database by doing
+  <tt>ant -Ddatabase=mysql</tt>.
+  <p>
+  This is the concept of an axis. You can have a variable called "database",
+  which takes three values. When you configure it, Hudson will run 3 builds, each with
+  different values assigned to the "database" variable to exhaustively cover
+  the configuration matrix.
+  <p>
+  Variables specified here are made available to the build as environment variables.
+  In addition, for Ant and Maven, variables are also exposed as properties, as if
+  <tt>-D<i>variableName</i>=<i>value</i></tt> are specified on the command line.
+  <p>
+  When multiple axes are specified, all of the possible combinations of axes are built
+  exhaustively. Multiple values in labels and JDKs are treated in the same way. So
+  if you specify jdk=[JDK5,JDK6], database=[mysql,postgresql,oracle], container=[jetty,tomcat],
+  then each build will consists of 2x3x2=12 different sub-builds.
+</div>
\ No newline at end of file

war/resources/help/matrix/axis-value_ja.html

+<div>
+  <!-- TODO:誰か訳して -->
+  Values assigned to variables. Multiple values are separated by whitespace or newlines.
+</div>
\ No newline at end of file

war/resources/help/matrix/jdk_ja.html

+<div>
+  <!-- TODO:誰か訳して -->
+  Specify the JDK(s) with which builds are performed. If none is selected,
+  the default JDK is used (no explicit <tt>JAVA_HOME</tt>, and <tt>java</tt> command
+  is assumed to be in <tt>PATH</tt>.) If multiple JDKs are selected,
+  the configuration matrix will include all of the specified JDKs.
+  <br>
+  Selecting multiple values is typically useful when this job is running tests,
+  and you need to run tests on multiple different versions of JDKs.
+  <br>
+  During a build, the selected JDK value for the given run is available as the "jdk" axis.
+  See the help of "axes" below for more information about how to access the axis value.
+</div>
\ No newline at end of file

war/resources/help/matrix/label_ja.html

+<div>
+  <!-- TODO:誰か訳して -->
+  Specify nodes where builds are performed.
+
+  <ul>
+    <li>
+      If none is selected, Hudson will choose
+      an available node to perform a build (this is the same behavior as the free-style
+      project when "tie this project to node" is not selected).  This is useful
+      when the project doesn't have a dependency on any particular node, as
+      it allows Hudson to utilize nodes in an optimal fashion.
+    <li>
+      If one is selected, Hudson will always run the build on the specified node
+      (if you select one from "specific nodes")
+      or one of the nodes that belongs to the label (if you select one from "label").
+      This is useful when the build is required to run on a specific computer,
+      or a subset of computers. For example, maybe your build requires MacOS X.
+    <li>
+      If multiple values are selected, the configuration matrix will be expanded to include
+      all of them, and builds will be performed on all of the selected nodes/labels.
+      This is useful, for example, when you'd like to run tests on Windows, Linux,
+      and Solaris.
+  </ul>
+
+  <br>
+  During a build, the selected node name / label name for the given run is available as the "label" axis.
+  See the help of "axes" below for more information about how to access the axis value.
+</div>
\ No newline at end of file