| Home >> All >> org >> eclipse >> ant |
| | org.eclipse.ant.core.* (11) | | org.eclipse.ant.internal.* (255) |
Package Samples:
org.eclipse.ant.internal.core.ant
org.eclipse.ant.internal.core
org.eclipse.ant.core
org.eclipse.ant.internal.ui.antsupport.logger
org.eclipse.ant.internal.ui.antsupport
org.eclipse.ant.internal.ui.antsupport.inputhandler
org.eclipse.ant.internal.ui.editor.utils
org.eclipse.ant.internal.ui.editor.text
org.eclipse.ant.internal.ui.editor.templates
org.eclipse.ant.internal.ui.editor.outline
org.eclipse.ant.internal.ui.editor.model
org.eclipse.ant.internal.ui.editor.formatter
org.eclipse.ant.internal.ui.editor.derived
org.eclipse.ant.internal.ui.editor
org.eclipse.ant.internal.ui.dtd.util
org.eclipse.ant.internal.ui.dtd.schema
org.eclipse.ant.internal.ui.dtd
org.eclipse.ant.internal.ui.preferences
org.eclipse.ant.internal.ui.model
org.eclipse.ant.internal.ui.launchConfigurations
Classes:
NfmParser: NfmParser parses an NFA and returns an equivalent DFA if it can do so in linear time and space (in terms of the original NFA). As used here, NfmParser is called lazily when someone actually asks for a Dfm. This is for performance reasons. Why go to the work of calculating all those Dfms if nobody ever uses them? Well-formed errors in content models have already been detected. The only error that can arise in NfmParser is an ambiguity error. Bruggemann-Klein showed that if an NFA is 1-unambiguous, an epsilon-free NFA constructed from it in linear time is actually a DFA. This is obvious in NfmParser. ...
NfmNode: Non-deterministic finite state machine node. Following Aho & Ullman, nfm nodes contain two transition links. The graph is constructed so that no node requires more than two links. There are exactly these kinds of nodes: Symbol Next1 Next2 Meaning "a" fwd null Regexp "a" null null null Accepting node null fwd1 fwd2 Start node of ? and * regexp fwd2 points to stop node null fwd bkw Internal node of + and * regexp fwd points to stop node bkw points, e.g., in "a*" to start node of "a" null fwd1 fwd2 Start node of | regexp, e.g., "a|b", fwd nodes point to start nodes of "a" and "b". null fwd null Internal ...
Parser: Simple parser for DTDs. Returns ISchema representing the DTD. To parse a DTD, you must parse an XML document. The parseDTD() method builds a temporary XML document in memory that refers to or includes the DTD. There is no dependency in this package on any code outside the package except XMLReader. To hide the underlying parser, XML parser exceptions are wrapped by a ParseError. Unless debugging, the two string constants are sufficient to determine the cause of the error.
InternalProject: A subclass of Project to facilitate "faster" parsing with less garbage generated. This class is not used on Ant 1.6 and newer due to the improvements in lazy loading of these Ant versions. Only three tasks are loaded (property, taskdef and typedef: three tasks that can be defined outside of a target on Ant 1.5.1 or older). Datatypes are loaded if requested. Derived from the original Ant Project class
TaskDescriptionProvider: The TaskDescriptionProvider provides the additional descriptions for tasks and attributes for the code assist. Descriptions for task are originally provided with the XML file TASKS_DESCRIPTION_XML_FILE_NAME . This file is parsed by the provider and requested descriptions are returned. Check out the documentation for the public methods of this class.
SchemaFactory: SchemaFactory is a SAX DeclHandler that converts DTD ELEMENT and ATTLIST declarations to schema form on the fly. The only two methods available to external users of SchemaFactory are its constructor and getSchema() . The latter returns the schema built by this process and should not be called until the XML parser to which this handler is attached has finished parsing.
MessageIds: Copyright (c) 2003 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/cpl-v10.html Contributors: IBM Corporation - initial API and implementation
Dfm: Deterministic finite state machine. Once constructed DFM is immutable and can be used by multiple threads. A Dfm node is essentially an accepting flag and a hashtable mapping atoms to Dfm nodes. (Almost of org.eclipse.ant.internal.ui.dtd.util is aimed at reducing the storage overhead of hundreds of little hashtables.)
AntModelProject: Derived from the original Ant Project class This class allows property values to be written multiple times. This facilitates incremental parsing of the Ant build file It also attempts to ensure that we clean up after ourselves and allows more manipulation of properties resulting from incremental parsing
AntSecurityManager: A security manager that always throws an AntSecurityException if the calling thread attempts to cause the Java Virtual Machine to exit/halt. Otherwise this manager just delegates to the pre-existing manager passed in the constructor or mimics the default security manager behavior
AntSecurityManager: A security manager that always throws an AntSecurityException if the calling thread attempts to cause the Java Virtual Machine to exit/halt. Otherwise this manager just delegates to the pre-existing manager passed in the constructor or mimics the default security manager behavior
AntPropertyValueProvider: Dynamic provider for Ant properties. Provides the dynamic values for the following Ant properties: eclipse.home - set to the Eclipse installation directory * eclipse.running - set (to "true") when Eclipse is running
AntInputHandler: The default input handler when using Ant within Eclipse. This is the class that will respond to requests from within an Ant build file. If the build is occurring in Ant 1.6.0 and the -noinput option has been specified this input handler will fail.
Schema: This is a very simple schema suitable for DTDs. Once constructed, a schema is immutable and could be used by multiple threads. However, since in general the schema will reflect the internal DTD subset, re-use for multiple documents is problematic.
AntEnvironmentTab: An environment tab for Ant launch configurations. Environment variables are only supported when Ant is run in a separate VM, so this tab adds a warning message at the top and disables the widgets if the config isn't set to run in a separate VM.
StatusDialog: An abstract base class for dialogs with a status bar and ok/cancel buttons. The status message must be passed over as StatusInfo object and can be an error, warning or ok. The OK button is enabled or disabled depending on the status.
Factory: Factory maintains a free list and, with FactoryObject, serves as a basis for factories of all types. Factory should only be subclassed in singleton classes; for static factories, it may be instantiated as a static object.
ProjectHelper: Derived from the original Ant ProjectHelper2 with help from the JAXPUtils class. This class provides parsing for using a String as a source and provides handlers that will continue parsing to completion upon hitting errors.
AntBuildTab: A launch configuration tab which allows the user to specify which resources should be built before the Ant build (a build scope) This class may be instantiated; this class is not intended to be subclassed.
SearchForBuildFilesDialog: This dialog allows the user to search for Ant build files whose names match a given pattern. The search may be performed on the entire workspace or it can be limited to a particular working set.
SubstitutionTextReader: Reads the text contents from a reader and computes for each character a potential substitution. The substitution may eat more characters than only the one passed into the computation routine.
NullInputHandler: A input handler that does nothing with input requests Used to ensure we do not block while retrieving targets from an Ant buildfile that has an input task in the top level implicit target
RemoteAntBuildLogger: Parts adapted from org.eclipse.jdt.internal.junit.runner.RemoteTestRunner A build logger that reports via a socket connection. See MessageIds for more information about the protocol.
SortedSet: SortedSet is a flyweight set implementation that uses an external array provided by a KeyHolder. SortedSet provides both equality/comparison operations and identity operations.
| Home | Contact Us | Privacy Policy | Terms of Service |