Differences between revisions 6 and 7
Revision 6 as of 2007-12-17 14:51:00
Size: 4485
Editor: TimEllison
Comment:
Revision 7 as of 2009-09-20 21:54:44
Size: 4515
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Besides the [http://en.wikipedia.org/wiki/Internet_slang usual Internet slang], [http://java.sun.com/docs/glossary.html words in common Java usage] and [http://www.apache.org/foundation/glossary.html Apache Software Foundation terminology], here's a dictionary of terms that you may come across in the Apache Harmony project which may need some explanation: Besides the [[http://en.wikipedia.org/wiki/Internet_slang|usual Internet slang]], [[http://java.sun.com/docs/glossary.html|words in common Java usage]] and [[http://www.apache.org/foundation/glossary.html|Apache Software Foundation terminology]], here's a dictionary of terms that you may come across in the Apache Harmony project which may need some explanation:
Line 9: Line 9:
'''ACQ''' : Authorized Contributor Questionnaire. A [http://harmony.apache.org/auth_cont_quest.html document] that Harmony contributors are asked to sign. '''ACQ''' : Authorized Contributor Questionnaire. A [[http://harmony.apache.org/auth_cont_quest.html|document]] that Harmony contributors are asked to sign.
Line 11: Line 11:
'''BCC''' : Bulk Contribution Checklist. A [http://harmony.apache.org/bulk_contribution_checklist.html document] that we use to check incoming re-purposed code contributions to Harmony. '''BCC''' : Bulk Contribution Checklist. A [[http://harmony.apache.org/bulk_contribution_checklist.html|document]] that we use to check incoming re-purposed code contributions to Harmony.
Line 21: Line 21:
'''EUT''' : [http://wiki.eclipse.org/Automated_Testing Eclipse unit tests] '''EUT''' : [[http://wiki.eclipse.org/Automated_Testing|Eclipse unit tests]]
Line 33: Line 33:
'''JDI''': [http://java.sun.com/j2se/1.5.0/docs/guide/jpda/jdi/index.html Java Debug Interface]. A high-level API in JPDA stack which is used by Java debuggers like [http://www.eclipse.org/ Eclipse] or [http://www.netbeans.org/ NetBeans] to connect to other JVM and control debugged application. Harmony uses JDI implementation from [http://www.eclipse.org/eclipse/debug/index.php Eclipse JDT Debug Project]. '''JDI''': [[http://java.sun.com/j2se/1.5.0/docs/guide/jpda/jdi/index.html|Java Debug Interface]]. A high-level API in JPDA stack which is used by Java debuggers like [[http://www.eclipse.org/|Eclipse]] or [[http://www.netbeans.org/|NetBeans]] to connect to other JVM and control debugged application. Harmony uses JDI implementation from [[http://www.eclipse.org/eclipse/debug/index.php|Eclipse JDT Debug Project]].
Line 35: Line 35:
'''JDWP''': [http://java.sun.com/j2se/1.5.0/docs/guide/jpda/jdwp-spec.html Java Debug Wire Protocol]. A communication protocol in JPDA stack which is used to control a JVMTI agent by a Java debugger over network or other communication means. '''JDWP''': [[http://java.sun.com/j2se/1.5.0/docs/guide/jpda/jdwp-spec.html|Java Debug Wire Protocol]]. A communication protocol in JPDA stack which is used to control a JVMTI agent by a Java debugger over network or other communication means.
Line 37: Line 37:
'''Jitrino''', '''Jitrino.JET''', '''Jitrino.OPT''' : Jitrino is the family name of JIT compilers that work with the DRLVM. The Jitrino.JET and Jitrino.OPT are JIT compilers with different architectures, [http://harmony.apache.org/subcomponents/drlvm/JIT.html as described here]. '''Jitrino''', '''Jitrino.JET''', '''Jitrino.OPT''' : Jitrino is the family name of JIT compilers that work with the DRLVM. The Jitrino.JET and Jitrino.OPT are JIT compilers with different architectures, [[http://harmony.apache.org/subcomponents/drlvm/JIT.html|as described here]].
Line 39: Line 39:
'''JPDA''': [http://java.sun.com/j2se/1.5.0/docs/guide/jpda/ Java Platform Debugger Architecture]. A stack of standard APIs and protocols which are used for debugging and profiling of Java application. Includes JDI, JDWP and JVMTI specifications. '''JPDA''': [[http://java.sun.com/j2se/1.5.0/docs/guide/jpda/|Java Platform Debugger Architecture]]. A stack of standard APIs and protocols which are used for debugging and profiling of Java application. Includes JDI, JDWP and JVMTI specifications.
Line 41: Line 41:
'''JVMTI''' : [http://java.sun.com/j2se/1.5.0/docs/guide/jvmti/jvmti.html Java Virtual Machine Tool Interface]. A low-level native API in JPDA stack created by Sun in Java 1.5 and later to replace deprecated JVMDI and JVMPI interfaces. This API is used both for debugging and profiling of Java applications. '''JVMTI''' : [[http://java.sun.com/j2se/1.5.0/docs/guide/jvmti/jvmti.html|Java Virtual Machine Tool Interface]]. A low-level native API in JPDA stack created by Sun in Java 1.5 and later to replace deprecated JVMDI and JVMPI interfaces. This API is used both for debugging and profiling of Java applications.
Line 49: Line 49:
'''TPTP''' : [http://www.eclipse.org/tptp/ Eclipse Test & Performance Tools Platform Project]. Very useful and powerful Eclipse plug-in which includes Java profiler that can be used with Harmony for performance optimization of both Java applications and internal classlib implementation. This profiler uses JVMTI and Byte Code Instrumentation (BCI) technique for gathering performance data. '''TPTP''' : [[http://www.eclipse.org/tptp/|Eclipse Test & Performance Tools Platform Project]]. Very useful and powerful Eclipse plug-in which includes Java profiler that can be used with Harmony for performance optimization of both Java applications and internal classlib implementation. This profiler uses JVMTI and Byte Code Instrumentation (BCI) technique for gathering performance data.

WTF? - A dictionary of Apache Harmony abbreviations and acronyms

Every technical community seems to grow a set of vocabulary around the terms that are in common usage, and it can often be the case that abbreviations, idioms and acronyms are impenetrable to the newcomer.

Besides the usual Internet slang, words in common Java usage and Apache Software Foundation terminology, here's a dictionary of terms that you may come across in the Apache Harmony project which may need some explanation:


ACQ : Authorized Contributor Questionnaire. A document that Harmony contributors are asked to sign.

BCC : Bulk Contribution Checklist. A document that we use to check incoming re-purposed code contributions to Harmony.

BTI : Build-Test Infrastructure

CC : Cruise Control, which Harmony uses for regression test.

DRLVM : Dynamic Runtime Layer Virtual Machine - the advanced VM developed within the Apache Harmony project.

EGA : Eclipse Geronimo Application - the name of a particular scenario test in the Apache Harmony test suite.

EUT : Eclipse unit tests

H-xxxx or HY-xxxx : (discouraged) A reference to the JIRA issue. See the encouraged form HARMONY-xxxx.

HARMONY-xxxx : Name of an Apache JIRA issue http://issues.apache.org/jira/browse/HARMONY-xxxx. See also H-xxxx.

HDK : Harmony Developer's Kit. The set of files required to incrementally develop Harmony itself, c.f. the JDK which is designed for Java developers.

HUT : Harmony Unit Tests, you may also see EUT = Eclipse Unit Test, GUT = Geronimo Unit Tests, ...

hy : Abbreviation for Harmony, commonly used in naming Apache Harmony modules and files. See also H-xxxx.

JDI: Java Debug Interface. A high-level API in JPDA stack which is used by Java debuggers like Eclipse or NetBeans to connect to other JVM and control debugged application. Harmony uses JDI implementation from Eclipse JDT Debug Project.

JDWP: Java Debug Wire Protocol. A communication protocol in JPDA stack which is used to control a JVMTI agent by a Java debugger over network or other communication means.

Jitrino, Jitrino.JET, Jitrino.OPT : Jitrino is the family name of JIT compilers that work with the DRLVM. The Jitrino.JET and Jitrino.OPT are JIT compilers with different architectures, as described here.

JPDA: Java Platform Debugger Architecture. A stack of standard APIs and protocols which are used for debugging and profiling of Java application. Includes JDI, JDWP and JVMTI specifications.

JVMTI : Java Virtual Machine Tool Interface. A low-level native API in JPDA stack created by Sun in Java 1.5 and later to replace deprecated JVMDI and JVMPI interfaces. This API is used both for debugging and profiling of Java applications.

LUNI : Java packages in lang, util, net, and io space

Mx : Series of Apache Harmony stable milestone builds, not a formal Harmony release. Also used in way of M1 build or M1 release.

SAMSA : A module in Harmony jdktools component, which provides unified native wrapper for JDK tools written in Java. This name was borrowed from Kafka's character.

TPTP : Eclipse Test & Performance Tools Platform Project. Very useful and powerful Eclipse plug-in which includes Java profiler that can be used with Harmony for performance optimization of both Java applications and internal classlib implementation. This profiler uses JVMTI and Byte Code Instrumentation (BCI) technique for gathering performance data.

VMI : VM interface, the contract between the Class libraries and the Virtual Machine

WTF (last edited 2009-09-20 21:54:44 by localhost)