Issue Type: Improvement Improvement
Assignee: Unassigned
Components: build
Created: 27/Feb/13 8:33 AM
Description:

STK parent pom's dependency mgmt section defines version as usual. Unfortunately it doesn't define all version there. Hence we have a mix of how version are defined.

e.g. dependency mgmt section defines versions for

  • magnolia-module-activation, magnolia-module-data & junit
    but not for
  • magnolia-core, magnolia-templating, magnolia-rendering, magnolia-ui-admincentral or commons-proxy & cglib-full

As most of these non-managed dependencies are used in several modules, updating any version e.g. when preparing a release is unnecessarily "complex"

Fix Versions: 2.5
Project: Magnolia Standard Templating Kit
Priority: Major Major
Reporter: Daniel Lipp
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to