[DERBY-1046] JVMInfo is duplicated in derbyclient.jar

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.8.2.2, 10.9.1.0
• Component/s: Build tools
• Issue & fix info: Patch Available
• Assignee: Katherine Marsden
• Reporter: Knut Anders Hatlen
• Created: 24/Feb/06 17:53
• Updated: 24/Jul/12 17:26
• Resolved: 30/Sep/11 19:17

Description

The JVMInfo class is included twice in derbyclient.jar, as
org.apache.derby.iapi.services.info.JVMInfo and
org.apache.derby.shared.common.info.JVMInfo. The only one of them
actually used by the client code is the one found in
org.apache.derby.shared.common.info.

org.apache.derby.iapi.services.info.JVMInfo is also included in
derby.jar, so one could run into problems if the classpath contains
derbyclient.jar and derby.jar with different versions.

Issue Links

• relates to: DERBY-5431 If 10.7 or greater derbyclient.jar is in the classpath before an older release's server jars, derby fails to boot with NoSuchFieldError for JVMInfo.JAVA_SQL_TYPES_BOOLEAN
• relates to: DERBY-5410 sysinfo needs to be adjusted to indicate support for Java 7 jdbc 4.1 level