Bug ID: JDK-4368021 Html converter -backup option does not change anything

Type: Bug
Component: deploy
Sub-Component: plugin
Affected Version: 1.3.0

Priority: P5
Status: Closed
Resolution: Duplicate
OS: solaris_2.6
CPU: generic

Submitted: 2000-09-01
Updated: 2000-10-06
Resolved: 2000-10-06

For both the manual and GUI parts of the HTMLConverter, if the backup is specified by the user to be something other than the default, it will still use the default.  The user should be able to save the backup wherever they choose, otherwise there should be no backup option available.

EVALUATION The -backup option works if you give a directory in the workspace that you are converting the files. But if you were to give it even a non-write-protected directory /home/billyh or /net/tirpitz/bill it won't write to the directory. This is because the File method rename() is not able to do this. william.harnois@East 2000-09-13 The HTML Converter uses the method in the class File called renameTo() to rename the original file to the desired backup directory. If you look at bug 4073756, it says that the renameTo() method basically does the exact same thing as the mv unix command, but is unable to mv files to different NFS mounted directories. It will only rename a file within a single filesystem. william.harnois@East 2000-10-04 This is now being saved as a duplicate of bug 4073756 The java io group does not plan on fixing this bug because they feel that renameTo() is using the unix command rename(2) and not the unix command mv. This html converter bug should be fixed so I'm reopening this bug. william.harnois@East 2001-02-13

13-02-2001

SUGGESTED FIX Instead of using the renameTo() method, create a new file of the same name in the desired backup location. Copy the contents of the previous file into the backup file. Then delete the original file. william.harnois@East 2001-02-13

13-02-2001