Requirement #814 (assigned)
Opened 17 years ago
Last modified 14 years ago
Improve install/deploy experience — at Version 5
Reported by: | jamoore | Owned by: | jmoore |
---|---|---|---|
Priority: | major | Milestone: | OMERO-Beta4.2 |
Component: | Deployment | Keywords: | n.a. |
Cc: | Business Value: | n.a. | |
Total Story Points: | n.a. | Roif: | n.a. |
Mandatory Story Points: | n.a. |
Description (last modified by jmoore)
Currently there are several situations and warnings which are only printed during or after JBoss start up. These could be performed during "ant deploy" or some future "ant install" target:
- #444 check for postgres.jar in JBOSS_HOME/server/lib (or copy it)
- check for omero.data.dir (/OMERO)
- check dbpatch level
- check Java version (and possible existence of _jboss-remoting.jar if needed)
- on failure, run "bin/omero server stop"
- on failure, print common things to look into
This might should be just large warnings or possibly errors to prevent startup. If we ever replace JBOSS_HOME/bin/run.sh with a call to "ant jboss", then
With #1037 I've removed ant from the final dist, meaning that each of these becomes a python script. The only task to add from that ticket is:
- bin/omero db install
Change History (5)
comment:1 Changed 16 years ago by jmoore
- Milestone changed from 3.0-Beta3 to 3.0-Beta4
- Status changed from new to assigned
comment:2 Changed 15 years ago by jmoore
- Description modified (diff)
- Priority changed from minor to major
comment:3 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4 to OMERO-Beta4.1
Much of this is done, though we don't perform checks yet on startup. This will have to come in the next milestone.
comment:4 Changed 14 years ago by jmoore
- Type changed from Task to Requirement
comment:5 Changed 14 years ago by jmoore
- Description modified (diff)
- Milestone changed from Unscheduled to OMERO-Beta4.2
Still very true, but pushing to next milestone.