Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6414746

sponsor ws should only use partial tables, to simplify future development

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 6
    • 6
    • install
    • None
    • b90
    • generic
    • generic, windows
    • Not verified

      When we build the sponsor transforms, we currently use the following tables to override the tables of the normal JRE MSI installer.

      AppSearch.idt CustomAction.idt Property.idt
      Binary.idt Dialog.idt RegLocator.idt
      CheckBox.idt DrLocator.idt Registry.idt
      Control.idt ISLocalControl.idt SCCS
      ControlCondition.idt ISString.idt Signature.idt
      ControlEvent.idt InstallUISequence.idt
       
      Now that we have this sponsor ws, every time we make a change to any of these tables in the install ws, we will also have to make it in the sponsors workspace. Otherwise, the transform will undo the change that we made in the install ws. This can get tricky, and mistakes will likely be made. Most of the sponsor specific stuff is just an addition to the regular install ws tables, not an actual change. We should really only add the sponsor specific stuff to these tables and concatenate them over the regular install ws tables. That way fixes made in the install workspace will not need to be duplicated in the sponsor ws.

      However, there are some tables where this will not be entirely possible. For tables like ControlEvent.idt, actual changes are made to the database tuples, so we'll probably have to keep the entire table in the sponsor workspace.

            billyh William Harnois
            billyh William Harnois
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: