youys
/
ant
Not watched
1
0
Fork 1
Code
Releases 0 Wiki Activity
Issues 0 Pull Requests 0 Datasets Model Cloudbrain
Browse Source

Like requested by Pavel Vlasov on the user list "Please re-add SQLC and Transformica to the External tools and tasks page" 

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@452757 13f79535-47bb-0310-9956-ffa450edef68
master
Jan Materne 18 years ago
parent
ef789dfa9b
commit
8e4085c37e
2 changed files with 166 additions and 26 deletions
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. +107
    -10
      docs/external.html
  2. +59
    -16
      xdocs/external.xml

+ 107
- 10
docs/external.html View File

@@ -1001,14 +1001,14 @@
<a name="Build Number"></a>
Build Number
</h4>
<p> Build Number is a tool to track software artifacts such as files and automatically assign
proper version/build numbers to them. It ensures that two different artifacts will have different
version/build numbers, but identical artifacts/builds will be assigned the same number. It doesn't
take version management away from you and doesn't replace your build process, but rather plugs
into the process and introduces version/build number governance by defining who is in charge of
which part of version number. With Build Number you are still in charge of the head of the version
number. E.g. you may decide to have 4 numbers in your version (major, minor, interface, implementation)
and you want to manage the two first numbers (major and minor). Build Number will take care of the
<p> Build Number is a tool to track software artifacts such as files and automatically assign
proper version/build numbers to them. It ensures that two different artifacts will have different
version/build numbers, but identical artifacts/builds will be assigned the same number. It doesn't
take version management away from you and doesn't replace your build process, but rather plugs
into the process and introduces version/build number governance by defining who is in charge of
which part of version number. With Build Number you are still in charge of the head of the version
number. E.g. you may decide to have 4 numbers in your version (major, minor, interface, implementation)
and you want to manage the two first numbers (major and minor). Build Number will take care of the
tedium of managing the last two numbers (interface and implementation). </p>
<table class="externals" cellspacing="1" cellpadding="4">
<tr>
@@ -2035,7 +2035,7 @@
</th>
<td colspan="1" rowspan="1"
valign="top" align="left">
Tested with Ant 1.5 and 1.5.2
Tested with Ant 1.5.x and 1.6.5
</td>
</tr>
<tr>
@@ -2045,7 +2045,7 @@
</th>
<td colspan="1" rowspan="1"
valign="top" align="left">
<a href="http://www.hammurapi.biz">http://www.hammurapi.biz</a>
<a href="http://www.hammurapi.biz/products/hammurapi">http://www.hammurapi.biz/products/hammurapi</a>
</td>
</tr>
<tr>
@@ -4931,6 +4931,53 @@
valign="top" align="left">
Revised BSD
</td>
</tr>
</table>
<h4 class="subsection">
<a name="SQL Compiler (SQLC)"></a>
SQL Compiler (SQLC)
</h4>
<p>SQL Compiler (SQLC) compiles database metadata and SQL statements into data access and data transfer classes.</p>
<table class="externals" cellspacing="1" cellpadding="4">
<tr>
<th colspan="1" rowspan="1"
valign="top" align="left">
Compatibility:
</th>
<td colspan="1" rowspan="1"
valign="top" align="left">
Tested with Ant 1.5.4 and 1.6.5
</td>
</tr>
<tr>
<th colspan="1" rowspan="1"
valign="top" align="left">
URL:
</th>
<td colspan="1" rowspan="1"
valign="top" align="left">
<a href="http://www.hammurapi.biz/products/sqlc">http://www.hammurapi.biz/products/sqlc</a>
</td>
</tr>
<tr>
<th colspan="1" rowspan="1"
valign="top" align="left">
Contact:
</th>
<td colspan="1" rowspan="1"
valign="top" align="left">
<a href="http://www.hammurapi.biz/hammurapi-biz/ef/xmenu/contact.html">Project Contact Page</a>
</td>
</tr>
<tr>
<th colspan="1" rowspan="1"
valign="top" align="left">
License:
</th>
<td colspan="1" rowspan="1"
valign="top" align="left">
LGPL
</td>
</tr>
</table>
<h4 class="subsection">
@@ -5245,6 +5292,56 @@
valign="top" align="left">
BSD-like license
</td>
</tr>
</table>
<h4 class="subsection">
<a name="Transformica"></a>
Transformica
</h4>
<p>Transformica is a versatile and extensible code generator.
Supports multiple source models including database metadata, Java source files, grammar
files and custom models.
</p>
<table class="externals" cellspacing="1" cellpadding="4">
<tr>
<th colspan="1" rowspan="1"
valign="top" align="left">
Compatibility:
</th>
<td colspan="1" rowspan="1"
valign="top" align="left">
Tested with Ant 1.5.x and 1.6.5
</td>
</tr>
<tr>
<th colspan="1" rowspan="1"
valign="top" align="left">
URL:
</th>
<td colspan="1" rowspan="1"
valign="top" align="left">
<a href="http://www.hammurapi.biz/products/transformica">http://www.hammurapi.biz/products/transformica</a>
</td>
</tr>
<tr>
<th colspan="1" rowspan="1"
valign="top" align="left">
Contact:
</th>
<td colspan="1" rowspan="1"
valign="top" align="left">
<a href="http://www.hammurapi.biz/hammurapi-biz/ef/xmenu/contact.html">Project Contact Page</a>
</td>
</tr>
<tr>
<th colspan="1" rowspan="1"
valign="top" align="left">
License:
</th>
<td colspan="1" rowspan="1"
valign="top" align="left">
LGPL
</td>
</tr>
</table>
<h4 class="subsection">


+ 59
- 16
xdocs/external.xml View File

@@ -488,17 +488,17 @@
</tr>
</table>
</subsection>
<subsection name="Build Number">
<p> Build Number is a tool to track software artifacts such as files and automatically assign
proper version/build numbers to them. It ensures that two different artifacts will have different
version/build numbers, but identical artifacts/builds will be assigned the same number. It doesn't
take version management away from you and doesn't replace your build process, but rather plugs
into the process and introduces version/build number governance by defining who is in charge of
which part of version number. With Build Number you are still in charge of the head of the version
number. E.g. you may decide to have 4 numbers in your version (major, minor, interface, implementation)
and you want to manage the two first numbers (major and minor). Build Number will take care of the
<p> Build Number is a tool to track software artifacts such as files and automatically assign
proper version/build numbers to them. It ensures that two different artifacts will have different
version/build numbers, but identical artifacts/builds will be assigned the same number. It doesn't
take version management away from you and doesn't replace your build process, but rather plugs
into the process and introduces version/build number governance by defining who is in charge of
which part of version number. With Build Number you are still in charge of the head of the version
number. E.g. you may decide to have 4 numbers in your version (major, minor, interface, implementation)
and you want to manage the two first numbers (major and minor). Build Number will take care of the
tedium of managing the last two numbers (interface and implementation). </p>

<table class="externals">
@@ -519,7 +519,7 @@
<td>Commercial</td>
</tr>
</table>
</subsection>
</subsection>

<subsection name="Checkstyle">

@@ -1046,20 +1046,18 @@
</subsection>

<subsection name="Hammurapi">

<p>Java code review tool. Performs automated code
review. Contains 111 inspectors which check different aspects
of code quality including coding standards, EJB, threading,
...</p>

<table class="externals">
<tr>
<th>Compatibility:</th>
<td>Tested with Ant 1.5 and 1.5.2</td>
<td>Tested with Ant 1.5.x and 1.6.5</td>
</tr>
<tr>
<th>URL:</th>
<td><a href="http://www.hammurapi.biz">http://www.hammurapi.biz</a></td>
<td><a href="http://www.hammurapi.biz/products/hammurapi">http://www.hammurapi.biz/products/hammurapi</a></td>
</tr>
<tr>
<th>Contact:</th>
@@ -2682,6 +2680,27 @@
</table>
</subsection>

<subsection name="SQL Compiler (SQLC)">
<p>SQL Compiler (SQLC) compiles database metadata and SQL statements into data access and data transfer classes.</p>
<table class="externals">
<tr>
<th>Compatibility:</th>
<td>Tested with Ant 1.5.4 and 1.6.5</td>
</tr>
<tr>
<th>URL:</th>
<td><a href="http://www.hammurapi.biz/products/sqlc">http://www.hammurapi.biz/products/sqlc</a></td>
</tr>
<tr>
<th>Contact:</th>
<td><a href="http://www.hammurapi.biz/hammurapi-biz/ef/xmenu/contact.html">Project Contact Page</a></td>
</tr>
<tr>
<th>License:</th>
<td>LGPL</td>
</tr>
</table>
</subsection>

<subsection name="SQLUnit">
<p>SQLUnit is a regression and unit testing harness for testing
@@ -2856,6 +2875,30 @@
</table>
</subsection>

<subsection name="Transformica">
<p>Transformica is a versatile and extensible code generator.
Supports multiple source models including database metadata, Java source files, grammar
files and custom models.
</p>
<table class="externals">
<tr>
<th>Compatibility:</th>
<td>Tested with Ant 1.5.x and 1.6.5</td>
</tr>
<tr>
<th>URL:</th>
<td><a href="http://www.hammurapi.biz/products/transformica">http://www.hammurapi.biz/products/transformica</a></td>
</tr>
<tr>
<th>Contact:</th>
<td><a href="http://www.hammurapi.biz/hammurapi-biz/ef/xmenu/contact.html">Project Contact Page</a></td>
</tr>
<tr>
<th>License:</th>
<td>LGPL</td>
</tr>
</table>
</subsection>

<subsection name="Venus Application Publisher's (Vamp) Ant Task Suite">

@@ -3617,4 +3660,4 @@
</section>

</body>
</document>
</document>

Write Preview
Loading…
Cancel
Save
Please read the following content carefully:

Dear OpenI User

Thank you for your continuous support to the Openl Qizhi Community AI Collaboration Platform. In order to protect your usage rights and ensure network security, we updated the Openl Qizhi Community AI Collaboration Platform Usage Agreement in January 2024. The updated agreement specifies that users are prohibited from using intranet penetration tools. After you click "Agree and continue", you can continue to use our services. Thank you for your cooperation and understanding.

For more agreement content, please refer to the《Openl Qizhi Community AI Collaboration Platform Usage Agreement》

Agree and continue
Disagree, exit