Bugzilla – Full Text Bug Listing
| Summary: | orion.conf is always moved to archive | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Gorkem Ercan <gorkem.ercan> |
| Component: | Server | Assignee: | Anthony Hunter <ahunter.eclipse> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse, eclipse |
| Version: | unspecified | ||
| Target Milestone: | 8.0 | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Gorkem Ercan
Trying Orion 7.0, this always happens for me. Even a fully commented out orion.conf causes it to be deemed as invalid and taken out of the way. This is what gets logged: 2014-12-08 10:08:52.993 [Worker-0] ERROR org.eclipse.orion.server.config - Meta File Error, root contains invalid metadata: file /home/rafael/cloudfier/repository/orion.conf archived to /home/rafael/cloudfier/repository/.archive/orion.conf No details on what would be wrong. Note this is running against an existing (4.0) workspace. Ok, there is a workaround. This does not occur if the orion.conf file lives in the current directory, only if it lives in the workspace (even if a brand-new one). Is that option no longer supported? Our expected usage is that orion.conf lives in the application root directory alongside the executable. I didn't even remember that it could be read from the workspace, but I see now this is mentioned in the server admin guide. With our changes to support multiple concurrent instances of Orion, we have been moving away from using the platform instance location for anything important other than OSGi bundle state. I think we should just stop supporting orion.conf in workspace location, and support only pwd and a location specific by system property. Paul if you agree, can you change the server code to stop checking workspace location, and update the server admin guide doc. I was using this scenario to mostly feed configuration to a dockerized orion to test different settings. It is probably not a production scenario though The Orion install should be disposable, but not the configuration, so it'd be better if it did not have to live alongside the executable. Luckily, at list on Linux, I can have a symbolic link outside of the orion install pointing to the executable inside the install, and the configuration file can be alongside this file, so I'm good. ...alongside this *link*, I meant. It's server side code that moves the orion.conf to .archive. Anthony, would another option be to ignore orion.conf in the workspace root, just like we ignore .metadata? PW "and support only pwd and a location specific by system property" Either of those two approaches are good from my viewpoint. (In reply to Paul Webster from comment #7) > It's server side code that moves the orion.conf to .archive. Anthony, would > another option be to ignore orion.conf in the workspace root, just like we > ignore .metadata? > > PW Yes, I have delivered this update with commit: http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=137a6805b95cf95de1c791693cbabfe4bf7244ad |