[MAGNOLIA-4352] exclusions for betwixt 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: None
Affects Version/s: 4.5.1
Fix Version/s: 4.5.2

Type: Improvement Priority: Neutral
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:
relation
is related to MAGNOLIA-4351 exclusions for jaxen in core's pom ov... 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)

 Description   

We could simplify the setting by adding xml-apis to the exclusion of the parent pom and completely remove the betwixt exclusions in core's pom.



 Comments   
Comment by Daniel Lipp [ 28/Mar/12 ]

This is related in the sense that for both cases exclusions defined in parent pom got obsolete due to exclusions in child's pom. For MAGNOLIA-4351 this was bad as the exclusions of the child was a subset of the parent's exclusions. Here it's just ugly as it's actually the parent's exclusions that are a subset of the child ones.

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