[MGNLMIGRATION-274] Split migration module and migration integration tests into different projects Created: 04/Nov/13  Updated: 25/Apr/14  Resolved: 14/Mar/14

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: Integration tests
Affects Version/s: None
Fix Version/s: 1.2.9

Type: Task Priority: Major
Reporter: Milan Divilek Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLMIGRATION-319 Migration project could depend on low... Closed
causality
is causing MGNLMIGRATION-315 Remove redundant branches Closed
dependency
relation
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Right now migration module and migration integration tests are in one project and it makes hard to managing versions in poms. And because integration test have to run against the last dev(SNAPSHOT) version then we also force to build migration module with the last version.

  • split migration module and migration integration tests into two different projects for better managing version. This will also allow to better set version for integration test. So it will be easy to run integration tests against whatever version of magnolia (4.5.4, 4.5.10...)

-* rename branches to reflect their purpose- obsolete



 Comments   
Comment by Robert Šiška [ 14/Mar/14 ]

Integration tests moved from/to:

modules/4-5-migration.git internal/migration-tests.git
magnolia-4-5-migration-1.2.x 4.4-to-4.5.x
magnolia-4-5-migration-2.0.x 4.5-to-5.2.x
master 5.0-to-5.2.x
Generated at Mon Feb 12 10:18:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.