[MAGNOLIA-56] relative pathnames don't work when running as service Created: 13/Aug/04  Updated: 10/Mar/05  Resolved: 10/Mar/05

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 2.1 Final

Type: Improvement Priority: Major
Reporter: Pascal Mangold 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:

 Comments   
Comment by Fabrizio Giustina [ 10/Mar/05 ]

Fixed in svn for 2.1.
Now Magnolia calculates relative paths from the webapp root (note that this is different from the previous version), and doesn't depend anymore from the appserver/OS configuration.
Code and configuration have been updated (added a warning about the new base path in web.xml).

Now you can specify paths into magnolia war simply using:
<init-param>
<param-name>magnolia.cache.startdir</param-name>
<param-value>cache</param-value>
</init-param>

Generated at Mon Feb 12 03:13:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.