[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22754#action_22754
]
Philipp Bärfuss commented on MAGNOLIA-2743:
-------------------------------------------
MAGNOLIA-2445 is related to installation/update when having the
magnolia.update.auto set to true.
The problem I run into is that the system was miss configured (well by some
install tasks but the install did not fail at all). That went as far as that a
single miss configured command stopped the system to start up.
> startup: don't fail to start the system just because a single
> module/component fails to start
> ---------------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2743
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2743
> Project: Magnolia
> Issue Type: Improvement
> Components: updatemechanism
> Affects Versions: 4.0.1
> Reporter: Philipp Bärfuss
> Assignee: Philipp Bärfuss
> Fix For: 4.1
>
>
> Since FactoryUtil.newInstance() is re-throwing exceptions (MAGNOLIA-2552) a
> module or component startup can fail.
> ModuleManager and Content2Bean itself should be aware of this and treat
> exceptions accordingly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
