[ARCH-33] Take advantage of Maven Archetype Plugin support for empty directories Created: 14/Feb/14 Updated: 14/Mar/14 Resolved: 14/Feb/14 |
|
| Status: | Closed |
| Project: | Archetypes |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.2 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| 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 DoR: |
Empty
|
||||||||
| Description |
|
... to a certain extent. Following ARCHETYPE-289, the archetype plugin "supports" generating empty directories. It still doesn't work perfectly (see ARCHETYPE-458), but with some resources-plugin configuration, still provides for an easier maintenance of our archetypes: we can have the complete overview of files and directories created by an archetype just by looking at src/main/resources/archetype-resources, rather than the combination of that AND the META-INF/maven/archetype-metadata.xml file. Since we're using Git, part of the "new workaround" involves adding (and further ignoring}} .emptydir-placeholder files. |