[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: |
|
||||||||||||||||||||
| 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:
now core's pom has also exclusions set on jaxen:
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. |