Actions
Bug #2842
closedJetty can't be started with a JAVA_HOME which is /usr/java
Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Packaging
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
We need a more flexible test to set the JAVA and JAVA_HOME envars.
With java installed in /usr/java, jetty can't be started and display theses messages:
/etc/init.d/jetty restart # /etc/init.d/jetty restart Stopping Jetty: OK Setting umask to 0027 Starting Jetty: /etc/init.d/jetty: line 491: /usr/bin/java: No such file or directory
Updated by Jonathan CLARKE over 12 years ago
- Status changed from New to 2
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
- Target version changed from 2.4.0~beta4 to 2.4.0~beta5
Updated by Jonathan CLARKE over 12 years ago
- Status changed from 2 to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:57794790aa980a251d7df27e55bf26fe7b686011.
Updated by Jonathan CLARKE over 12 years ago
- Status changed from Pending technical review to Released
Updated by Nicolas PERRON almost 12 years ago
- Project changed from Rudder to 34
- Category deleted (
11)
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 34 to Rudder
- Category set to Packaging
Actions