[MAGNOLIA-1238] Current module dms doesn't point to the 3.0.1-SNAPSHOT version of Magnolia Created: 30/Nov/06  Updated: 04/Feb/07  Resolved: 07/Dec/06

Status: Closed
Project: Magnolia
Component/s: build
Affects Version/s: 3.0.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Anthony Ogier Assignee: Magnolia International
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: 1m
Time Spent: Not Specified
Original Estimate: 1m

Attachments: Text File pom.xml.patch    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

The current module-dms has its pom.xml which don't point to the current Magnolia sources.
Look at the patch I'll provide.



 Comments   
Comment by Anthony Ogier [ 30/Nov/06 ]

The poms' patch

Comment by Magnolia International [ 30/Nov/06 ]

Why is that a concern ?
Actually, this might not have been made clear, but the dms module (and samples, too) are bound to be moved to modules/community rather than the main trunk, and have a separate lifecycle. As long as the APIs don't change, the dependency from dms to magnolia won't need to be changed. (of course, the bundle will embed the latest-and-greatest dms)

Comment by Anthony Ogier [ 30/Nov/06 ]

All right, so if I understand, all the correction in the dms modules will not be integrated to the trunk of Magnolia when compiling, but the moment there is a release, the pom.xml of Magnolia will be upgraded to take the latest release of the dms module ?

Comment by Magnolia International [ 07/Dec/06 ]

Yes, you understood correctly. This is also valid in the other direction, i.e if there are api changes in magnolia-core, for instance, dms will be updated and most likely released when magnolia-core gets released.

Generated at Mon Feb 12 03:24:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.