-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
Component/s: None
-
None
Summary
Jira could ship with Java application that would replace all of shell starting/configuration scripts. Running the application would create a configured Tomcat instance with Jira webapp.
This would have following adventages:
- Jira wouldn't rely on shell startup scripts, making it more OS agnostic - fixing e.g.
JRASERVER-68811 - Jira could manage default vs custom configuration (JRASERVER-68882) for:
- Tomcat
- JVM/GC
- Logging
- Mentioned above configurations could be stored in jirahome/database making upgrade process less complicated, as the configuration wouldn't need to be reapplied.
- Atlassian SDK could run Jira directly from Java without need of it's own Tomcat
- relates to
-
JRASERVER-68811 Jira fails to start on Solaris when executing the startup manually.
-
- Closed
-
-
JRASERVER-68882 Separate user defined Tomcat/JVM/GC/Logging configuration from default ones specified in Jira
- Gathering Interest