[MGNLEE-187] Set environment variables in a SETENV file Created: 30/Aug/10  Updated: 13/Jan/11  Resolved: 18/Nov/10

Status: Closed
Project: Magnolia DX Core
Component/s: build / bundling
Affects Version/s: 4.3.6
Fix Version/s: 4.4

Type: Improvement Priority: Major
Reporter: Antti Hietala Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MAGNOLIA-3388 Set environment variables in a SETENV... Closed
dependency
is depended upon by MAGNOLIA-3387 Improvement of installation process Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

Simplify installation and startup by deploying a setenv file that sets JAVA_HOME and JRE_HOME environment variables for the target system. These variables are a common source of installation problems, especially on the Windows platform where it cannot be assumed that JRE/JDK is already installed (unlike OSX or Linux).

For example, if you have a fresh Windows 7 installation you don't have either JRE or JDK by default. In installation instructions we tell users that JRE is adequate. When the user sets JAVA_HOME to their JRE installation path the system warns "JAVA_HOME should point to a JDK not a JRE" and refuses to start.

If automated JRE/JDK selection is not possible then at least deploy a setenv.sh/setenv.bat file that contains commented-out commands for setting the variables. Users can uncomment the correct variable with minimal effort. Tomcat will read the configuration.


Generated at Mon Feb 12 05:27:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.