gmane.comp.cms.magnolia.devel

JIRA (on behalf of Fabrizio Giustina | 16 Jul 21:33

[magnolia-dev] [JIRA] Created: (MAGNOLIA-2271) Magnolia 3.6 update can crash due to unexpected repository location

Magnolia 3.6 update can crash due to unexpected repository location
-------------------------------------------------------------------

                 Key: MAGNOLIA-2271
                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2271
             Project: Magnolia
          Issue Type: Bug
    Affects Versions: 3.6 RC1
            Reporter: Fabrizio Giustina
            Assignee: Fabrizio Giustina
             Fix For: 3.6

the update task setup/for3_6/CheckNodeTypesDefinition.java is looking for a custom-nodetypes.xml
file based on the repo home configuration property.
If the repositories.xml file has been customized and changed without using that property as the base path
magnolia will never startup due to a FileNotFound exception. We should at least ignore it, making startup
work as usual.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

(Continue reading)

headers

JIRA (on behalf of Fabrizio Giustina | 16 Jul 21:37

[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-2271) Magnolia 3.6 update can crash due to unexpected repository location


     [
http://jira.magnolia.info/browse/MAGNOLIA-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fabrizio Giustina resolved MAGNOLIA-2271.
-----------------------------------------

    Resolution: Fixed

fixed with r16843, will merge on branch

> Magnolia 3.6 update can crash due to unexpected repository location
> -------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2271
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2271
>             Project: Magnolia
>          Issue Type: Bug
>    Affects Versions: 3.6 RC1
>            Reporter: Fabrizio Giustina
>            Assignee: Fabrizio Giustina
>             Fix For: 3.6
>
>
> the update task setup/for3_6/CheckNodeTypesDefinition.java is looking for a custom-nodetypes.xml
file based on the repo home configuration property.
> If the repositories.xml file has been customized and changed without using that property as the base path
magnolia will never startup due to a FileNotFound exception. We should at least ignore it, making startup
work as usual.

(Continue reading)

headers

JIRA (on behalf of Fabrizio Giustina | 16 Jul 21:41

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2270) Better logs and avoid NPEs when magnolia is started from an unexpanded war


    [
http://jira.magnolia.info/browse/MAGNOLIA-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159#action_17159
] 

Fabrizio Giustina commented on MAGNOLIA-2270:
---------------------------------------------

you can see the diff from the branch, I committed it using the jira number. Please don't be too picky with this
kind of changes, it could become really annoying...

> Better logs and avoid NPEs when magnolia is started from an unexpanded war
> --------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2270
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2270
>             Project: Magnolia
>          Issue Type: Improvement
>    Affects Versions: 3.6 RC1
>            Reporter: Fabrizio Giustina
>            Assignee: Fabrizio Giustina
>             Fix For: 3.6
>
>
> Magnolia doesn't work with if started from an unexpanded war, as we know, but we also should give a better output.
> 3.6-rc1 dies with an unhelpful NPE in MgnlServletContextListener

--

-- 
This message is automatically generated by JIRA.
-

(Continue reading)

headers

JIRA (on behalf of Jan Haderka | 16 Jul 21:41

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2270) Better logs and avoid NPEs when magnolia is started from an unexpanded war


    [
http://jira.magnolia.info/browse/MAGNOLIA-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160#action_17160
] 

Jan Haderka commented on MAGNOLIA-2270:
---------------------------------------

Fabrizio,
what makes you think Magnolia doesn't run on unexpanded war file? We have quite few clients running on war
files without any problems. It is all just a matter of configuration. Could you please describe
environment in which you had problems with current code? I would prefer not to make changes to this kind of
very central classes while being in RC.
Thanks,
Jan

> Better logs and avoid NPEs when magnolia is started from an unexpanded war
> --------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2270
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2270
>             Project: Magnolia
>          Issue Type: Improvement
>    Affects Versions: 3.6 RC1
>            Reporter: Fabrizio Giustina
>            Assignee: Fabrizio Giustina
>             Fix For: 3.6
>
>
> Magnolia doesn't work with if started from an unexpanded war, as we know, but we also should give a better output.

(Continue reading)