[ http://jira.magnolia.info/browse/MGNLIMG-27?page=comments#action_15008 ] David Smith commented on MGNLIMG-27: ------------------------------------
On the surface, that seems to have done it. My dev build bootstrapped normally with only a change to the version in the admininterface dependency. I'll have to do some deeper testing to see if there are any other issues. Is there a way to define a minimum version dependency or a version range dependency? Seems rather limited to hard code specific versions into module dependencies. > module is dependent on magnolia 3.0 -- can't use with 3.1 > --------------------------------------------------------- > > Key: MGNLIMG-27 > URL: http://jira.magnolia.info/browse/MGNLIMG-27 > Project: Magnolia Image Filtering Module > Issue Type: Bug > Affects Versions: 1.0 > Environment: tomcat 5.5, magnolia 3.1 trunk (svn revision 12303) > Reporter: David Smith > Assigned To: Grégory Joseph > > On attempting to add magnolia-module-imagefiltering to 3.1 trunk, the > following exception occurs: > info.magnolia.module.model.reader.ModuleDependencyException: Module > magnolia-module-imagefiltering (version 1.0.0-SNAPSHOT) is dependent on > admininterface version 3.0, but Magnolia Admin Interface Module (version > 3.1.0-SNAPSHOT) is currently installed. > It'd be nice when time allows to at least branch this module and create a > version usable with 3.1. -- 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/docs/en/editor/stayupdated.html ----------------------------------------------------------------
