This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Build failed; Because run sql script
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 03, 2009
11:03 AM
Is there anyway to include an action based on build target?
I have a project where I am building installers both with and without a bundled Java VM. For the installer without the bundled JVM I would like to include a pre-install panel action to ask the user which JVM to use. For the installer with the bundled JVM, I don't want this panel to appear. Is there any way to achieve this?
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 03, 2009
05:31 PM
Use the following variable for evaluation:
$JAVA_HOME$: Installer without VM: Defaults to the value of the java property java.home. Its value can change at the Choose Java Virtual Machine step if the end-user selects a VM Installer with VM: Defaults to the value specified in the Project - Java Task. It can change when the $USER_INSTALL_DIR$ changes, or at the Choose Java Virtual Machine step if the end–user selects a VM already on their machine.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 04, 2009
01:43 AM
I have a project including mysql server, When I adding the sql script and build the project, It aways prompts me that running sql script failure. I instead ";" with "GO" or "\n"; But It did'nt work, I want to know why; Can you show a single example for sql script? If you do'nt mind!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 04, 2009
03:06 AM
Hello plazzy! As far as I can tell, your issue is different than the one cpaine initially reported, so please open a new thread for your issue! Thanks!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 04, 2009
12:38 PM
pv7721 wrote:
Use the following variable for evaluation:
Thanks for the info. I have successfully used the value of $JAVA_HOME$ to achieve what I wanted. What I did was set the folder for the bundled JVM in "Project->Java" to be "bundled_jre", so that I had a distinctive string to test for.
Only slight annoyance is I can't find a way of conditionally choosing the labels used in the list of installer steps displayed on the left of the installer panels. This means I either have to choose to have a label in the list saying "Choose Java Virtual Machine" which is never selected when the installer has a bundled JRE, or choose not to have it there at all, so that for the non-bundled JVM installer there is no specific label selected when the Choose Java Virtual Machine panel is displayed.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 04, 2009
04:16 PM
Good, this is what I had in mind, a special string to test against. For the step in the left pane, I would use "Configure Java", which is selected when the user chooses an external Java or skipped when you install the bundled JRE. Advice: while tempting as it is (give the user more freedom of choice to use an already installed JRE, in practice is more an annoyance for you: in case your application needs a minimum Java version you might need to check the selected JRE if it meets the minimum etc. We used to give this choice of external JRE, but at a certain moment we removed it altogether: relying on the bundled JRE give us the certainty that there won't be any compatibility issues.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 13, 2009
01:03 PM
pv7721 wrote:
For the step in the left pane, I would use "Configure Java", which is selected when the user chooses an external Java or skipped when you install the bundled JRE.
Thanks for the suggestion.
pv7721 wrote:
Advice: while tempting as it is (give the user more freedom of choice to use an already installed JRE, in practice is more an annoyance for you: in case your application needs a minimum Java version you might need to check the selected JRE if it meets the minimum etc. We used to give this choice of external JRE, but at a certain moment we removed it altogether: relying on the bundled JRE give us the certainty that there won't be any compatibility issues.
I take your point. For our product we supply two installers, one with a bundled JRE with no choice of external JRE for a simple straight forward install. The other installer has no bundled JRE and is for more Java-savvy users to avoid them having to clutter up their machines with another JRE.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 13, 2009
01:08 PM
pv7721 wrote:
For the step in the left pane, I would use "Configure Java", which is selected when the user chooses an external Java or skipped when you install the bundled JRE.
Thanks for the suggestion.
pv7721 wrote:
Advice: while tempting as it is (give the user more freedom of choice to use an already installed JRE, in practice is more an annoyance for you: in case your application needs a minimum Java version you might need to check the selected JRE if it meets the minimum etc. We used to give this choice of external JRE, but at a certain moment we removed it altogether: relying on the bundled JRE give us the certainty that there won't be any compatibility issues.
I take your point. For our product we provide two installers. One of them has a bundled JRE with no choice of external JRE for a simple staright forward install. The other installer has no bundled JRE and is intended for more Java-savvy users who don't want to clutter up their machines with another JRE.