[MAGNOLIA-1602] Update mechanism Created: 20/Jun/07 Updated: 06/Dec/13 Resolved: 07/Aug/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | updatemechanism |
| Affects Version/s: | None |
| Fix Version/s: | 3.1 M3 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
We had some brainstorming sessions today about the update mechanism that will be part of Magnolia 3.1. We put our ideas down in mindmaps. While that format might not be ideal to read for someone who did not participate in the meetings, we also see it as a good compromise between ease of creation, maintenance and usefulness, as opposed to long-ish spec-ish text documents. We'll be happy to provide info or clarify points that are not clear by themselves, and/or discuss any of them. The first one is an attempt to list all the problems to solve and features we'd like to see in there: The seconds focuses more on technical or practical aspects, with some decisions being taken or viewpoints being adopted: |
| Comments |
| Comment by Tom Jensen [ 12/Jul/07 ] |
|
This doesn't break the build but makes magnolia unusable. The exception that happens on startup is: INFO info.magnolia.cms.beans.config.ModuleRegistration ModuleRegistration.java(readModuleDefinitions:150) 12.07.2007 11:59:49 Reading module definition I poked around in the code and determined that the i.m.cms.beans.config.ModuleRegistration was pointing to the module.dtd in the old place it used to be (/info/magnolia/cms/module/module.dtd). So I repointed to the correct place (/info/magnolia/module/model/module.dtd), rebuilt and fired it up again. The exception I got on startup this time was: INFO info.magnolia.cms.beans.config.ModuleRegistration ModuleRegistration.java(readModuleDefinitions:150) 12.07.2007 12:14:20 Reading module definition Rather than trying to track down how to fix this I thought I'd just make this comment and defer it to whomever worked on this and might know more quickly than I how to fix. |
| Comment by Magnolia International [ 12/Jul/07 ] |
|
Tom : thanks for the report, I'd overlooked that - had a bunch of local changes I cant commit yet. Just commit a fix for this - pls let me know if you encounter any more issue. |
| Comment by Magnolia International [ 16/Jul/07 ] |
|
Commited a bunch of changes in a new branch: |
| Comment by Fabrizio Giustina [ 06/Aug/07 ] |
|
added a property "magnolia.update.auto" (false by default) that can be set in order to enable automatic update, just like it worked in previous versions. magnolia.bootstrap.ifEmpty and magnolia.bootstrap.force have a different meaning and we should probably try to make them work as before ("magnolia.update.auto" simply means "don't wait for me to click ok on the update UI") |
| Comment by Magnolia International [ 07/Aug/07 ] |
|
a preliminary version will be available in 3.1 M3. Will create more jira reports for further improvements. |
| Comment by Magnolia International [ 06/Dec/13 ] |
|
Attaching screenshots of mindmaps mentioned here, in case they ever go missing. |