Module dependencies should be able to handle version numbers in a more flexible
way
-----------------------------------------------------------------------------------
Key: MAGNOLIA-1209
URL: http://jira.magnolia.info/browse/MAGNOLIA-1209
Project: magnolia
Issue Type: Improvement
Components: core
Affects Versions: 3.0 Final
Reporter: Grégory Joseph
Assigned To: Sameer Charles
For instance, the dms module depends on adminInterface 3.0
At the moment, if we use it with adminInterface 3.0.1, it will just not deploy.
We should be able to
- declare dependencies without version requirement (i.e "I need
adminInterface, no matter what version")
- declare dependencies with a minimal version requirement (i.e "I need
adminInterface, at least version 3.0, ignoring minor versions // I need
adminInterface at least 3.0.2")
- declare dependencies with minimal and maximal version requirements (i.e "I
need adminInterface, at least version 3.0, but I won't run with 3.1 or further
versions")
--
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://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
