[UIMA-1273] Pear runtime pulls in all jar files in pear lib directory, no matter if they're on the classpath or not

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.2
• Fix Version/s: 2.3
• Component/s: Core Java Framework
• Assignee: Unassigned
• Reporter: Thilo Goetz
• Created: 23/Jan/09 13:15
• Updated: 14/Oct/09 09:58
• Resolved: 14/Oct/09 09:58

Description

The pear runtime will not only use the classpath as defined in metadata/install.xml, it will also pick up any jar in the lib directory. It even recurses down into subdirectories. This is undocumented, and most unexpected.

I chatted with Michael about this. He thinks it may be because the same code that creates the classpath in the pear packager is used in the runtime. The packager does collect all jar files it can find and puts them in the classpath, and the pear file. That's fine for the packager, but not the runtime. We should either have an explicit classpath, or use all jar files in the lib dir, but not both.