| Summary: | Checks needed on Excalibur Logkit Version: 1.0.1 | ||
|---|---|---|---|
| Product: | [Technology] Hudson | Reporter: | Duncan Mills <duncan.r.mills> |
| Component: | Core | Assignee: | Winston Prakash <winston.prakash> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Duncan Mills
I searched through core sources. The classes from Logkit does not seem to be used any where in the core. Seems to be brought in by velocity as a compile time dependency. BTW the version seems to be Logkit 2.0 (not 1.0.1). I see this comment in the core pom.xml
<!--
| these are now optional in commons-logging:1.1.1,
| keeping them around in case any plugins use them
-->
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>${log4j.version}</version>
</dependency>
<dependency>
<groupId>logkit</groupId>
<artifactId>logkit</artifactId>
<version>${logkit.version}</version>
</dependency>
<dependency>
<groupId>avalon-framework</groupId>
<artifactId>avalon-framework</artifactId>
<version>${avalon-framework.version}</version>
</dependency>
<!--
| ^ end of optional commons-logging dependencies
-->
Relevant comments added. |