[MAGNOLIA-319] Use non relative repository paths in repository configuration files Created: 17/Mar/05 Updated: 17/Mar/05 Resolved: 17/Mar/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | build |
| Affects Version/s: | 2.1 Final |
| Fix Version/s: | 2.1 Final |
| Type: | Improvement | Priority: | Major |
| Reporter: | Markus Zingg | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Date of First Response: |
| Description |
|
Within the current version the repository configuration files (WEB-INF/config/repositories/xxx.xml) contain relative paths (../xxxx). Starting the tomcat application server in another directory than $TOMCAT_HOME/bin (eg. in directory $TOMCAT_HOME -> bin/catalina.sh run) will result in an error in the magnolia startup process, because Jackrabbit does not find the repository. As far as I know Jackrabbit supports variables in the configuration files (here ${rep.home} ) : The default repository should be either configured to use that variables or handle the paths relativly to the web application directory. |
| Comments |
| Comment by Fabrizio Giustina [ 17/Mar/05 ] |
|
fixed in svn, now variables are used in repository config |