|
Lines 615-625
Link Here
|
| 615 |
|
615 |
|
| 616 |
|
616 |
|
| 617 |
<h3>3.2.2 <a name="I-Platform-Ant">Platform - Ant</a></h3> |
617 |
<h3>3.2.2 <a name="I-Platform-Ant">Platform - Ant</a></h3> |
| 618 |
<h4>UTF-8 encoded buildfiles with Byte Order Mark</h4> |
618 |
<h4> Custom Ant tasks and Ant types must be separate from plug-in library JARs</h4> |
| 619 |
<p>UTF-8 encoded buildfiles with byte order marks will fail to be parsed correctly depending on the XML parser being used for the build. Therefore a valid buildfile will fail to build with an error message similar to: "BUILD FAILED: C:\workspace\bom.xml:1: Document root element is missing.". To succeed in building with these files, ensure to include Xerces jars on the Ant runtime classpath so that the Xerces parser is used to parse the XML. As well the context menu for these files in the Navigator or Package Explorer will not have the run shortcuts for Ant builds. (bug |
|
|
| 620 |
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=67048">67048</a>)</p> |
| 621 |
<h4> Custom Ant tasks and Ant |
| 622 |
types must be separate from plug-in library JARs</h4> |
| 623 |
<p>Including the class files for custom Ant tasks or Ant types in the regular |
619 |
<p>Including the class files for custom Ant tasks or Ant types in the regular |
| 624 |
code JAR for your plug-in causes problems. These class files must be provided in |
620 |
code JAR for your plug-in causes problems. These class files must be provided in |
| 625 |
a separate JAR that is contributed to the <code>org.eclipse.ant.core.antTasks</code> |
621 |
a separate JAR that is contributed to the <code>org.eclipse.ant.core.antTasks</code> |
|
Lines 631-660
Link Here
|
| 631 |
<p>Eclipse can run Ant in the same JVM as the rest of Eclipse. Several aspects |
627 |
<p>Eclipse can run Ant in the same JVM as the rest of Eclipse. Several aspects |
| 632 |
of Ant and its use of global Java resources (such as System.out and System.err), |
628 |
of Ant and its use of global Java resources (such as System.out and System.err), |
| 633 |
make it unsafe to run more than one Ant build concurrently in the same JVM. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=24129">24129</a>).</p> |
629 |
make it unsafe to run more than one Ant build concurrently in the same JVM. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=24129">24129</a>).</p> |
| 634 |
<h4> Running certain Ant tasks |
|
|
| 635 |
cause memory leakage</h4> |
| 636 |
<p>Certain Ant tasks are known to leak memory. Please see the bug report for |
| 637 |
details, patches, and possible workarounds. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=24448">24448</a>)</p> |
| 638 |
<h4> Tasks that require input |
| 639 |
lock up workspace</h4> |
| 640 |
|
| 641 |
<p>As with using Ant from the command line, prompts for input from the |
| 642 |
console is not handled. This is not the same as making use of the <input> |
| 643 |
task, which works correctly within Eclipse. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=21748">21748</a>)</p> |
| 644 |
<h4>"version" property is always set when running Ant in the same VM as Eclipse</h4> |
| 645 |
<p>The Xalan libraries set system properties including a version property. These get set as properties within the Ant build and therefore the "version" property cannot be set within an Ant buildfile due to the immutable nature of Ant properties. This property will always be set to "2.4.1" for Ant builds in the same VM as Eclipse. (bug |
| 646 |
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=45717">45717</a>)</p> |
| 647 |
<h4>XDoclet support from within Eclipse</h4> |
| 648 |
|
630 |
|
|
|
631 |
<h4>XDoclet support from within Eclipse</h4> |
| 649 |
<p>Since there are differences when running Ant from the commandline and within Eclipse, some extra steps may be needed to have XDoclet support function correctly within Eclipse. Problems may occur creating XDoclet subtasks. The workarounds and full discussion can be found in bug report. (bug |
632 |
<p>Since there are differences when running Ant from the commandline and within Eclipse, some extra steps may be needed to have XDoclet support function correctly within Eclipse. Problems may occur creating XDoclet subtasks. The workarounds and full discussion can be found in bug report. (bug |
| 650 |
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37070">37070</a>)</p> |
633 |
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37070">37070</a>)</p> |
| 651 |
<h4>Ant Editor code completion based on Ant 1.6.1</h4> |
634 |
|
| 652 |
<p>Code completion provided by the Ant editor does not respect the user-specified version of org.eclipse.ant.core plug-in or ANT_HOME. Code completion proposals are mostly based on Ant 1.6.1 with some updates to Ant 1.6.5 (bug |
635 |
<h4>Ant Editor code completion based on Ant 1.6.x</h4> |
| 653 |
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=30886">30886</a>)</p> |
636 |
<p>Code completion provided by the Ant editor does not respect the user-specified version of org.eclipse.ant.core plug-in or ANT_HOME. |
| 654 |
<h4> Eclipse can hang due to implementation of the Ant <property> task (Windows 9X |
637 |
Code completion proposals are mostly based on Ant 1.6.x with some updates to Ant 1.6.5 (bug |
| 655 |
only)</h4> |
638 |
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=193046">bug 193046</a>)</p> |
| 656 |
<p>On Windows 9X, using:<property environment="env"/> will cause Eclipse to hang if the build occurs in the same VM as Eclipse. Running the build in a separate VM will hang the build but not Eclipse. |
|
|
| 657 |
(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=44196">44196</a>)</p> |
| 658 |
|
639 |
|
| 659 |
<h4> Setting build loggers not supported when debugging Ant builds</h4> |
640 |
<h4> Setting build loggers not supported when debugging Ant builds</h4> |
| 660 |
<p>When debugging Ant builds within Eclipse, setting -logger as a program argument will be ignored.</p> |
641 |
<p>When debugging Ant builds within Eclipse, setting -logger as a program argument will be ignored.</p> |
|
Lines 670-682
Link Here
|
| 670 |
|
651 |
|
| 671 |
<h4>Slow typing/saving of the Ant editor with imports that define numerous macrodefs</h4> |
652 |
<h4>Slow typing/saving of the Ant editor with imports that define numerous macrodefs</h4> |
| 672 |
<p>The Ant editor is slow on saving with buildfiles that have <import> declarations of buildfiles that have numerous <macrodef>s. |
653 |
<p>The Ant editor is slow on saving with buildfiles that have <import> declarations of buildfiles that have numerous <macrodef>s. |
| 673 |
See bugs <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92640">92640</a> and <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=125117">125117</a> for possible workarounds</p> |
654 |
See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=125117">125117</a> for a possible workaround</p> |
| 674 |
|
655 |
|
| 675 |
<h4>Failure to run Ant builds on non-Windows platforms if Eclipse installed in location with spaces in the path</h4> |
656 |
<h4>Failure to run Ant builds on non-Windows platforms if Eclipse installed in location with spaces in the path</h4> |
| 676 |
<p>Due to a bug in Ant 1.7.0, Ant builds will fail with an IllegalArgumentException if the Eclipse installation is in a location with spaces in the path. |
657 |
<p>Due to a bug in Ant 1.7.0, Ant builds will fail with an IllegalArgumentException if the Eclipse installation is in a location with spaces in the path. |
| 677 |
Embedded usage of Ant builds, such as plug-in export will also fail. |
658 |
Embedded usage of Ant builds, such as plug-in export will also fail. |
| 678 |
See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=187993">187993</a> for possible workarounds</p> |
659 |
See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=187993">187993</a> for possible workarounds</p> |
| 679 |
|
660 |
|
|
|
661 |
<h4>Ant 1.8.x reports missing libraries as build failures</h4> |
| 662 |
<p> |
| 663 |
In Ant 1.8.x, if you try to use a task that requires additional libraries and you do not have the libraries on the Ant classpath, the build will now properly report is failed. |
| 664 |
In previous versions of Ant, the build would still report that it had suceeded even though it actually failed to run any of the tasks from additional bundles. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=344518">bug 344518</a>. |
| 665 |
</p> |
| 666 |
<p> |
| 667 |
For more information on tasks that require additional bundles please refer to the <a href="http://www.apache.org/dist/ant/RELEASE-NOTES-apache-ant-1.8.2.html">Ant 1.8.2 release notes</a> |
| 668 |
and the <a href="http://ant.apache.org/manual/install.html#optionalTasks">Optional Tasks</a> section in the At manual. |
| 669 |
</p> |
| 670 |
|
| 671 |
<h4>Ant 1.8.x extension-point feature is not supported in the Ant editor</h4> |
| 672 |
<p> |
| 673 |
The extension-point feature added in Ant 1.8.x is not supported in the Ant editor, meaning there is no content assist or help support for it. |
| 674 |
See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=324625">bug 324625</a> for more details. |
| 675 |
</p> |
| 676 |
|
| 680 |
<h3>3.2.3 <a name="I-Platform-User-Assistance">Platform - User Assistance</a></h3> |
677 |
<h3>3.2.3 <a name="I-Platform-User-Assistance">Platform - User Assistance</a></h3> |
| 681 |
<h4>Welcome page not displayed properly (Linux/Unix)</h4> |
678 |
<h4>Welcome page not displayed properly (Linux/Unix)</h4> |
| 682 |
<p>The default Welcome implementation is HTML-based and requires a supported browser |
679 |
<p>The default Welcome implementation is HTML-based and requires a supported browser |
