Ah ... ok ... now I know what was going on ... If I put in the renaming in the parent, the build of the parent will fail because the file is obviously not there. So I put it in a self-activating profile, to activate the renaming, only if the file exists. Unfortunately activation of profiles happens before the pom is "alive" so there is no wildcards and no properties that we can use. So I fixed things to the "index" name ... but it doesn't work for any other name and then you need to add the renaming yourself.
Think we better come up with a different/better solution ... Chris Am 25.01.20, 09:33 schrieb "Christofer Dutz" <[email protected]>: But the idea with the main.content.file is not bad ... Could adjust the archetype and the parent pom accordingly. Chris Am 25.01.20, 08:44 schrieb "Justin Mclean" <[email protected]>: Hi, > I used the template to create several presentations and didn't have that issue. Is it assuming that it is called index rather than what is specified? For example: <properties> <project.main.contentfile>index_en</project.main.contentfile> </properties> Thanks. Justin
