From 4075bf26b65cf2be4c55f2e9cbdc1b854a41dbce Mon Sep 17 00:00:00 2001
From: pdanner Designed for use with Ant.
- This document is designed to be viewed using the frames feature. If you see this message, you are using a non-frame-capable web client.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Frame Alert
-
-
-
-
-
- CheckStyle Audit
-
- Designed for use with CheckStyle and Ant.
-
-
-
-
- Files
-
-
-
-
Name | -Errors | -
---|
Error Description | -Line | -
---|---|
Files | -Errors | -
---|---|
- This document is designed to be viewed using the frames feature. If you see this message, you are using a non-frame-capable web client. -
-
- |
-
-
- |
-
Reported Classes | -Methods Hit | -Lines Hit | -
---|---|---|
- To ensure accurate test runs on Java applications, developers need to know how much of - the code has been tested, and where to find any untested code. Coverage helps you - locate untested code, and measure precisely how much code has been exercised. - The result is a higher quality application in a shorter period of time. - - | -
- |
-
- |
-
- - - - | -Source Code Coverage |
-
Designed for use with Sitraka JProbe and Ant. | -
-
- Copyright © 1999-2001, Apache Software Foundation
-
- |
- This document is designed to be viewed using the frames feature. If you see this message, you are using a non-frame-capable web client. -
-- | - [summary] - [packages] - [cycles] - [explanations] - |
Package | -Total Classes | -Abstract Classes | -Concrete Classes | -Afferent Couplings | -Efferent Couplings | -Abstractness | -Instability | -Distance | - -
---|---|---|---|---|---|---|---|---|
-
- |
- ||||||||
- |
-
- | - [summary] - [packages] - [cycles] - [explanations] - |
Afferent Couplings: |
- Efferent Couplings: |
- Abstractness: |
- Instability: |
- Distance: |
-
Abstract Classes | -Concrete Classes | -Used by Packages | -Uses Packages | -
---|---|---|---|
- - |
-
- - |
-
- - |
-
- - |
-
- [summary] - [packages] - [cycles] - [explanations] - |
- | - [summary] - [packages] - [cycles] - [explanations] - |
There are no cyclic dependancies.
-
-
-
- [summary] - [packages] - [cycles] - [explanations] - |
- | - [summary] - [packages] - [cycles] - [explanations] - |
The following explanations are for quick reference and are lifted directly from the original JDepend documentation.
- -The number of concrete and abstract classes (and interfaces) in the package is an indicator of the extensibility of the package.
-The number of other packages that depend upon classes within the package is an indicator of the package's responsibility.
-The number of other packages that the classes in the package depend upon is an indicator of the package's independence.
-The ratio of the number of abstract classes (and interfaces) in the analyzed package to the total number of classes in the analyzed package.
-The range for this metric is 0 to 1, with A=0 indicating a completely concrete package and A=1 indicating a completely abstract package.
-The ratio of efferent coupling (Ce) to total coupling (Ce / (Ce + Ca)). This metric is an indicator of the package's resilience to change.
-The range for this metric is 0 to 1, with I=0 indicating a completely stable package and I=1 indicating a completely instable package.
-The perpendicular distance of a package from the idealized line A + I = 1. This metric is an indicator of the package's balance between abstractness and stability.
-A package squarely on the main sequence is optimally balanced with respect to its abstractness and stability. Ideal packages are either completely abstract and stable (x=0, y=1) or completely concrete and instable (x=1, y=0).
-The range for this metric is 0 to 1, with D=0 indicating a package that is coincident with the main sequence and D=1 indicating a package that is as far from the main sequence as possible.
- - - -- [summary] - [packages] - [cycles] - [explanations] - |
- [summary] - [packages] - [cycles] - [explanations] - |
- | Designed for use with JDepend and Ant. | -
Designed for use with JDepend and Ant.
-
- Summary- | - [summary] - [packages] - [cycles] - [explanations] - |
Package | -Total Classes | -Abstract Classes | -Concrete Classes | -Afferent Couplings | -Efferent Couplings | -Abstractness | -Instability | -Distance | - -
---|---|---|---|---|---|---|---|---|
-
- |
- ||||||||
- |
-
- Packages- | - [summary] - [packages] - [cycles] - [explanations] - |
Afferent Couplings: |
- Efferent Couplings: |
- Abstractness: |
- Instability: |
- Distance: |
-
Abstract Classes | -Concrete Classes | -Used by Packages | -Uses Packages | -
---|---|---|---|
- - |
-
- - |
-
- - |
-
- - |
-
- Cycles- | - [summary] - [packages] - [cycles] - [explanations] - |
There are no cyclic dependancies.
-
-
-
- Explanations- | - [summary] - [packages] - [cycles] - [explanations] - |
The following explanations are for quick reference and are lifted directly from the original JDepend documentation.
- -The number of concrete and abstract classes (and interfaces) in the package is an indicator of the extensibility of the package.
-The number of other packages that depend upon classes within the package is an indicator of the package's responsibility.
-The number of other packages that the classes in the package depend upon is an indicator of the package's independence.
-The ratio of the number of abstract classes (and interfaces) in the analyzed package to the total number of classes in the analyzed package.
-The range for this metric is 0 to 1, with A=0 indicating a completely concrete package and A=1 indicating a completely abstract package.
-The ratio of efferent coupling (Ce) to total coupling (Ce / (Ce + Ca)). This metric is an indicator of the package's resilience to change.
-The range for this metric is 0 to 1, with I=0 indicating a completely stable package and I=1 indicating a completely instable package.
-The perpendicular distance of a package from the idealized line A + I = 1. This metric is an indicator of the package's balance between abstractness and stability.
-A package squarely on the main sequence is optimally balanced with respect to its abstractness and stability. Ideal packages are either completely abstract and stable (x=0, y=1) or completely concrete and instable (x=1, y=0).
-The range for this metric is 0 to 1, with D=0 indicating a package that is coincident with the main sequence and D=1 indicating a package that is as far from the main sequence as possible.
- - - -- This document is designed to be viewed using the frames feature. If you see this message, you are using a non-frame-capable web client. -
-
- |
-
- |
-
Tests | -Failures | -Errors | -Success rate | -Time | -
---|---|---|---|---|
- |
-
- |
-
-
- Note: failures are anticipated and checked for with assertions while errors are unanticipated. - | -
- |
-
-
- | Designed for use with JUnit and Ant. | -
-
-
-
-
-
-
-
- |
-
Tests | -Failures | -Errors | -Success rate | -Time | -
---|---|---|---|---|
- |
-
- |
-
-
- Note: failures are anticipated and checked for with assertions while errors are unanticipated. - | -
- | Designed for use with JUnit and Ant. | -
-
-
-
-
-
-
-
-- - - - | -- Jakarta Ant - | -
-
- Copyright © 2000-2002, Apache Software Foundation
-
- |
Build Failed | -Build Complete | -Total Time: |
-
- - See the stacktrace. - |
-
ant.file | |
ant.version | |
java.version | |
os.name |
target | -task | -message | -
---|
- This document is designed to be viewed using the frames feature. If you see this message, you are using a non-frame-capable web client. -
-
- |
-
Audited classes | -Reported classes | -Violations | -
---|---|---|
- Note: Rules checked have originated from style guidelines suggested by the language designers, - experience from the Java development community and insite experience. Violations are generally - reported with a reference to the Java Language Specifications (JLS x.x.x) - and Metamata Audit rules (x.x). - Please consult these documents for additional information about violations. - - Rules checked also enforce adherence to Sun Java coding guidelines in use at Jakarta. - - One should note that these violations do not necessary underline errors but should be used - as an indication for possible errors. As always, use your best judgment and review - them carefully, it might save you hours of debugging. - | -
- - - - | -Source Code Audit |
-
Designed for use with Webgain QA/Metamata Audit and Ant. | -
-
- Copyright © 1999-2001, Apache Software Foundation
-
- |
- This document is designed to be viewed using the frames feature. If you see this message, you are using a non-frame-capable web client. -
-
- |
-
- |
-
V(G) | -LOC | -DIT | -NOA | -NRM | -NLM | -WMC | -RFC | -DAC | -FANOUT | -CBO | -LCOM | -NOCL | -
---|
- Note: Metrics evaluate the quality of software by analyzing the program source and quantifying - various kind of complexity. Complexity is a common source of problems and defects in software. - High complexity makes it more difficult to develop, understand, maintain, extend, test and debug - a program. - - The primary use of metrics is to focus your attention on those parts of code that potentially are - complexity hot spots. Once the complex areas your program have been uncovered, you can take remedial - actions. - For additional information about metrics and their meaning, please consult - Metamata Metrics manual. - | -
- Note: Metrics evaluate the quality of software by analyzing the program source and quantifying - various kind of complexity. Complexity is a common source of problems and defects in software. - High complexity makes it more difficult to develop, understand, maintain, extend, test and debug - a program. - - The primary use of metrics is to focus your attention on those parts of code that potentially are - complexity hot spots. Once the complex areas your program have been uncovered, you can take remedial - actions. - For additional information about metrics and their meaning, please consult - Metamata Metrics manual. - | -
- - - - | -Source Code Metrics |
-
Designed for use with Webgain QA/Metamata Metrics and Ant. | -
-
- Copyright © 1999-2001, Apache Software Foundation
-
- |
Designed for use with Ant.
-- New Files | - Modified Files | - Removed Files - | -