Unfortunately, the fact that it does not have any special support for multi-module project is not great: if you want the plugin to be executed only once (and you do want, otherwise it will fail because "the release already exist" and it's not great for performances anyway) you need to use the standard Maven <inherited>false</inherited>, but then it means that: 1. it's executed at the beginning, while it would be much better to execute it at the end (when the release perform is a success) 2. it means that you need to declare the plugin in each contrib project (with <inherited>false</inherited> if the contrib project has several modules)
For now, I'm going to configure it without any goal and execute the goal in the XWiki Standard release script, after the maven build.
Thomas Mortagne on 09/Jan/25 12:11
I experimented with [ https://github.com/RagedUnicorn/github-release-maven-plugin] and it's working well.
Unfortunately, the fact that it does not have any special support for multi-module project is not great: if you want the plugin to be executed only once (and you do want, otherwise it will fail because "the release already exist" and it's not great for performances anyway) you need to use the standard Maven <inherited>false</inherited>, but then it means that: 1. # it's executed at the beginning, while it would be much better to execute it at the end (when the release perform is a success) 2. # it means that you need to declare the plugin in each contrib project (with <inherited>false</inherited> if the contrib project has several modules)
For now, I'm going to configure it without any goal and execute the goal in the XWiki Standard release script, after the maven build.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
