River
  1. River
  2. RIVER-161

Coalesce jars from multiple source dirs while retain current Manifest Classpath semantics

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: jtsk_2.1
    • Fix Version/s: River_2.1.2
    • Component/s: com_sun_jini_tool
    • Labels:
      None
    • Bugtraq ID:
      6227228

      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."

        Activity

        Peter Firmstone made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Mark Brouwer made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Mark Brouwer made changes -
        Description 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."
        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."
        Affects Version/s jtsk_2.1 [ 12312606 ]
        Mark Brouwer made changes -
        Fix Version/s AR2 [ 12312604 ]
        Mark Brouwer made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Mark Brouwer made changes -
        Assignee Mark Brouwer [ marbro ]
        Nigel Daley made changes -
        Field Original Value New Value
        Description 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."
        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."
        Nigel Daley created issue -

          People

          • Assignee:
            Mark Brouwer
            Reporter:
            Nigel Daley
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development