[ARCH-18] POM should be default enable the filtering in order to replace placeholders on builds Created: 07/Feb/12  Updated: 14/Mar/14  Resolved: 08/Feb/12

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

Type: Improvement Priority: Neutral
Reporter: Will Scheidegger Assignee: Joerg Bellmann
Resolution: Fixed Votes: 0
Labels: filtering, placeholder, pom
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Date of First Response:

 Description   

When creating a module with the archetype (tested with the "theme" module) the module descriptor contains placeholders. These are not replaced when building the project because the filtering mechanism of the Maven Resources plugin is not enabled.

When using the magnolia parent poms it's fine since filtering is enabled there. But it would be better to enable filtering in the modules pom itself.

See http://forum.magnolia-cms.com/forum/thread.html?threadId=65c1a830-97e9-4ad6-82d6-1d08d907b03e



 Comments   
Comment by Magnolia International [ 08/Feb/12 ]

Thanks for the report. In fact, the "module" archetype already does this. The "forge-module" archetype also "does it", since it inherits from the forge parent pom. So I'll report that to the "theme" archetype.

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