[jira] Closed: (RIVER-161) Coalesce jars from multiple source dirs while retain current Manifest Classpath semantics

["Peter Firmstone (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RIVER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Firmstone closed RIVER-161.
---------------------------------


> Coalesce jars from multiple source dirs while retain current Manifest Classpath semantics
> -----------------------------------------------------------------------------------------
>
>                 Key: RIVER-161
>                 URL: https://issues.apache.org/jira/browse/RIVER-161
>             Project: River
>          Issue Type: New Feature
>          Components: com_sun_jini_tool
>    Affects Versions: jtsk_2.1
>            Reporter: Nigel Daley
>            Assignee: Mark Brouwer
>            Priority: Minor
>             Fix For: AR2
>
>
> Bugtraq ID [6227228|http://bugs.sun.com/bugdatabase/view_bug.do?bug_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."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.