[MGNLACTIVATION-101] Activation does not work if a workspace is not in the same repository as mgnlSystem and mgnlVersion Created: 19/Feb/15  Updated: 10/Jul/15  Resolved: 24/Feb/15

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

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-5975 Versioning does not work if a workspa... Closed
is depended upon by MGNLXAA-89 Transactional activation does not wor... Closed
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:

 Comments   
Comment by Jan Haderka [ 23/Feb/15 ]

ReceiveFilter

  • you should keep around old ctor and deprecate it to be backward compatible.

commons-io upgrade to 2.4 - can you double check that this library is not used anywhere else and if yes, that it is actually upgraded in all places that use it?

Comment by Hugo Ferreira [ 29/May/15 ]

Is this global activation or just activation with versioning? I'm facing this problem at the moment.

Comment by Jan Haderka [ 01/Jun/15 ]

Depends on which workspaces and on what instances you have in multiple repositories. If on author, than problem is just versioning. If you are using multiple repos on public, than it depends on what workspaces you have where. You might want to create support ticket to discuss details.

Comment by Milan Divilek [ 16/Jun/15 ]

CopyUtil is part of magnolia-core

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