[MAGNOLIA-1277] Build failes on current trunk (revision 7834), test scoped dependencies have to be at the bottom of pom.xml Created: 17/Dec/06  Updated: 06/Dec/07  Resolved: 06/Dec/07

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.0 Final
Fix Version/s: None

Type: Bug Priority: Major
Reporter: David Smith Assignee: Magnolia International
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Maven 2.0.4, Sun JDK 6


Attachments: Text File pom-junit-dependency.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

 Description   

When attempting to build Magnolia trunk, compilation of tests fail in magnolia-gui and magnolia-module-mail. The exact error is "junit.framework does not exist". Moving the junit dependency to the bottom of the depencency list in each subproject fixed the build. I don't think order should matter – it could be a bug in Maven. Will attach patch.



 Comments   
Comment by David Smith [ 17/Dec/06 ]

This patch is a little funny – the first part patching magnolia-gui/pom.xml is a good patch that only replaces the relevant sections. The second part that patches magnolia-module-mail/pom.xml appears to be a whole file replacement. Generated by Tortoise SVN 1.4.

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