[RIVER-161] Coalesce jars from multiple source dirs while retain current Manifest Classpath semantics

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: jtsk_2.1
• Fix Version/s: River_2.1.2
• Component/s: com_sun_jini_tool
• Bugtraq ID: 6227228
• Assignee: Mark Brouwer
• Reporter: Nigel Daley
• Created: 01/Aug/07 03:58
• Updated: 06/Jan/10 06:03
• Resolved: 15/Mar/08 12:23

Description

Bugtraq ID 6227228

"I would like to have an additional wrap method on com.sun.jini.tool.JarWrapper that takes java.io.File arguments instead of String arguments and that doesn't have the limitation that all JAR files to be wrapped are in the same directory. In the Class-Path entry of the Manifest files the referenced JAR files should be listed as being in the same directory (as required by specification).

This RFE is the result of the future ability of Seven to serve JAR files that seems (from the requestor perspective) to be in the same directory but are served from different locations on the filing system. I can work around this by moving all JAR files involved to a temp directory, apply JAR wrapping over there, move the wrapped JAR file to the final location and remove the temp directory, but I would prefer a better way of doing this."