[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23238#action_23238
]
Hudson CI server commented on MAGNOLIA-2788:
--------------------------------------------
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-trunk
#890|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/890/]
ModuleManager now provides the correct "current module" when
instanciating a version handler
> InstallContext should provide the correct "current module" to
> ModuleVersionHandlers at instantiation time
> ----------------------------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2788
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2788
> Project: Magnolia
> Issue Type: Bug
> Components: core
> Affects Versions: 4.1
> Reporter: Grégory Joseph
> Assignee: Grégory Joseph
> Fix For: 4.1.1
>
>
> Considering the following code:
> {code}
> public class MyModuleVersionHandler extends DefaultModuleVersionHandler {
> public MyModuleVersionHandler() {
> super();
> final ModuleDefinition currentModule =
> ModuleManager.Factory.getInstance().getInstallContext().getCurrentModuleDefinition();
> System.out.println(currentModule);
> }
> }
> {code}
> With 4.1, this print the ModuleDefinition of the module preceding the one
> corresponding to this version handler instead of "MyModule"
--
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]>
----------------------------------------------------------------
