Our product requires a SIGNIFICANT number of variable substitutions to be applied during installation, such that it would be more practical to have a single "substitute all variables" action rather than the current <substitute> action which requires each mapping to be explicitly named.

Are there any plans for such a feature? If not, is there any means currently available for us to develop it ourselves and "graft" (load?) it into the installer as a Java class such that it's executed at install time?


asked 18 Apr, 10:55

drivera's gravatar image

accept rate: 0%

Additionally, specifying an "interpolation pattern" would help in files where variable interpolation is already in play (i.e. ${} is already in use). For instance, patterns like %{VARIABLE} would be interpolated by resolving VARIABLE in the installer's existing variables/parameters.

I've seen other installers use @@VARIABLE@@. The idea is to not have to enumerate every single possible variable in the substitution since this can be quite time consuming and error-prone.



answered 18 Apr, 11:05

drivera's gravatar image

accept rate: 0%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 18 Apr, 10:55

Seen: 445 times

Last updated: 18 Apr, 11:05