Browse Prior Art Database

A method to automatically update a Jar or a Zip file with a few files via drag&drop Disclosure Number: IPCOM000199049D
Publication Date: 2010-Aug-24
Document File: 2 page(s) / 63K

Publishing Venue

The Prior Art Database


This article has proposed a method on updating files within a Jar or a Zip file via drag 'n' drop several files into a Jar or a Zip file. The drag and drop process is faster and simpler than the existing command jar which you have to provide the full path structure for the files to be updated. To provide a full path structure for each file is time-consuming and it can be complicated if the updated files have different paths. This method will increase software engineers' productivity and bring more business values to the software industry.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 2

A method to automatically update a Jar or a Zip file with a few files via drag &drop

Software developers and testers have found that a process to update a jar file with couple of changes are very time consuming and less productive. There are three well-known solutions to this problem :

Using jar tool from a command line to update the jar with couple of changed



Using WinZip to update the changes.


Using Ant to build a new jar.


The first one is using this command : jar uf jar-file input-file(s)

    The jar-file is a jar file which contains the input-files and the input-files must provide with their path structure. You have to manually find out these paths, otherwise the files will be added to the root directory of the jar file.

    The second method also involves some manual steps which you have to unzip the file, copy the updated files manually to the right destinations, and zip them again.

    Both solutions are very slow especially on navigating to the specific directory for a given class file to be updated in the Jar or Zip file. If you don't provide an explicit directory, the input file will be added into the root path of the jar which are unexpected.

    The last one is beyond this topic here as it is under an assumption of that there is always a build script or a tool available in your Integrated development environment (IDE) ready to use. If there no such a build script or a tool available, then you have to use the command jar which falls into the solution 1.

    The idea of this disclosure is to use a drag 'n' drop mechanism to...