[MAGNOLIA-1440] redeployment util allows module to clobber other modules installed files. Created: 28/Mar/07 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Chris Miner | Assignee: | Unassigned |
| Resolution: | Won't Do | 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
When a module is updated, part of the module registration process involves installing files. Only files under mgnl-files containing the module name as part of the path are installed. This is a good thing since it means each module has its own file 'name space'. However if you trigger redeployment via the deployment utils page, no such check is used. Any file anywhere in the classpath under mgnl-files is unpacked and written to the file system. You might notice this if your jsps never deploy by themselves and you find yourself having to deploy them manually every time you update your modules version number. |
| Comments |
| Comment by Philipp Bracher [ 03/Apr/07 ] |
|
I would like to change this as such:
|
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |