[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26563#action_26563
 ] 

Hudson CI server commented on MAGNOLIA-2762:
--------------------------------------------

Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#1356|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1356/]
     MAGNOLIA-2762 ModuleRegistry.get*() methods now throw exceptions for 
unknown modules - added isModuleRegistered() to cover cases where the previous 
behaviour was needed


> ModuleRegistry : throw an exception for unknown modules
> -------------------------------------------------------
>
>                 Key: MAGNOLIA-2762
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2762
>             Project: Magnolia
>          Issue Type: Improvement
>          Components: core, updatemechanism
>            Reporter: Grégory Joseph
>            Assignee: Grégory Joseph
>             Fix For: 4.3
>
>
> An exception should be thrown when attempted to get unknown modules.
> Care needs to be taken - some code checks if a module is present (see 
> {{InstallContext}} for instance) - but ideally the methods of ModuleRegistry 
> should be consistent in how they treat absent module. Maybe we'll need to 
> expose a new method to check for modules' existence.
> For 4.1 we'll simply issue a warning to avoid breaking the api.

-- 
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]>
----------------------------------------------------------------

Reply via email to