[MAGNOLIA-4351] exclusions for jaxen in core's pom override settings inherited from parent pom Created: 28/Mar/12  Updated: 29/Mar/12  Resolved: 28/Mar/12

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.5.1
Fix Version/s: 4.5.2

Type: Bug Priority: Major
Reporter: Daniel Lipp Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLBACKUP-54 Restore fails on startup due to prese... Closed
is causing MGNLEE-226 CLONE -Exclude xom from bundle Closed
relation
is related to MAGNOLIA-4352 exclusions for betwixt in core's pom ... 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

 Description   

magnolia-project's pom defines the following exclusions on jaxen:

  • xom
  • dom4j
  • xml-apis
  • xerces

now core's pom has also exclusions set on jaxen:

  • jdom
  • xml-apis

Defining exclusions in child poms will not lead to a exclusion of both - the ones from the parent and the child pom but will only exclude the child ones.
This is the reason why all other modules depending on core currently have to exclude e.g. xom again!


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