[MGNLACTIVATION-6] Rename exchange-simple module to activation - update tasks Created: 20/Nov/12  Updated: 21/Mar/13  Resolved: 19/Mar/13

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Task Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MAGNOLIA-4688 Rename exchange-simple module to acti... Closed
relation
is related to MAGNOLIA-4660 Move cache, exchange-simple and store... Closed
is related to MGNLXAA-53 Update module to work with activation... Closed
is related to MGNLXAA-55 Fix failing tests Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Sprint: Iteration 2013-12

 Description   

Leftover job from last sprint: create the update task. Here's a summary of things to do/take into account:

  • /config/modules/exchange-simple node can be safely deleted during upgrade from 4.5.x to 5.0, its default content being re-bootstrapped by the activation module
  • /server/filters/activation/bypasses remains untouched by the new module installation - no action required
  • /server/activation/subscribers/class value must be changed from info.magnolia.module.exchangesimple.DefaultActivationManager to info.magnolia.module.activation.DefaultActivationManager
  • for each subscriber under /server/activation/subscribers change the class value from info.magnolia.module.exchangesimple.DefaultSubscriber to info.magnolia.module.activation.DefaultSubscriber
  • publicKey remains untouched


 Comments   
Comment by Jan Haderka [ 25/Nov/12 ]

VersionHandler needs to be adapted to detect old name config and skip installation and move config to new place, otherwise new installation would break activation due to generation of new keys.

There needs to be related ticket where exchange-transactional dependencies are modified.

Comment by Federico Grilli [ 19/Mar/13 ]

tests are failing on hudson even though they work fine locally

Generated at Sun Feb 11 22:58:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.