[MGNLTOOLS-44] xmlParserAPIs-2.6.2 collides with removenode script Created: 31/May/11  Updated: 27/Mar/12  Resolved: 02/Jun/11

Status: Closed
Project: Repository Tools
Component/s: None
Affects Version/s: 1.1.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Zdenek Skodik Assignee: Ondrej Chytil
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace.txt    
Issue Links:
causality
caused by MGNLEE-226 CLONE -Exclude xom from bundle Closed
caused by MAGNOLIA-3723 Exclude xom from bundle Closed
caused by MGNLEE-205 CLONE -Exclude xom from bundle Closed
relation
is related to MGNLBACKUP-54 Restore fails on startup due to prese... 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:

 Description   

Since Magnolia CMS 4.4.3 we bundle xmlParserAPIs-2.6.2 to the webapp. This unfortunately breaks execution of the removenode script as it throws IncompatibleClassChangeError (find the attachment).

For the workaround just temporarily remove the jar from your libs.



 Comments   
Comment by Zdenek Skodik [ 01/Jun/11 ]

This applies to whatever script which makes the module a bit useless so we should target it to next release, which is apparently 1.2.

Comment by Ondrej Chytil [ 02/Jun/11 ]

Solved with MAGNOLIA-3723 and MGNLEE-205.

Comment by Federico Grilli [ 23/Jun/11 ]

nitpicking fix

Generated at Mon Feb 12 10:40:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.