[ARCH-60] Project archetype: war dependency must be defined before the pom dependency for the overlay set in the proper order Created: 05/Apr/18  Updated: 23/Apr/18  Resolved: 13/Apr/18

Status: Closed
Project: Archetypes
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.3

Type: Bug Priority: Neutral
Reporter: Zdenek Skodik Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
duplicate
is duplicated by MAGNOLIA-7216 Missing Dependencies When Creating Ma... 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:
Sprint: Kromeriz 142
Story Points: 0

 Description   

So that e.g. you won't end up with standard widgetset configured implicitly, although using pro webapp. 



 Comments   
Comment by Tobias Hochgürtel [ 17/Apr/18 ]

I know this is closed, but I just jumpt into this issue today... and it cost me time to find the information what was wrong. And yes I had changed the order manually . I just checked if there isn't an way to test the pom for an specific arrangement and found the following maven-plugin: https://github.com/ferstl/pedantic-pom-enforcers -> 

PedanticDependencyManagementOrderEnforcer DEPENDENCY_MANAGEMENT_ORDER This enforcer makes sure that all artifacts in your dependency management are ordered.

May be this is a way to ensure that such problems don't appear in the future or by and mistake. Never know that it's important to have an exact arrangement between to dependencies.

Generated at Sun Feb 11 23:23:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.