New contrib project request for XWiki Release Maven Plugin

Development
1

Hi everyone,

I’d like to request a new contrib repository for a XWiki Release Maven Plugin to help having something standard for releasing both XS and contrib extensions with automated checks without having to rely on a bash script.

Proposed repository name: maven-xwiki-release-plugin

2

Anything required by XS must be in the xwiki GH org. Contrib project can reuse that.

Some questions:

  • Could it go in the xwiki-dev-tools existing repo? (seems more logical to me)
  • Could you also explain how you’re planning to use it?
  • Is the goal to modify the XWiki release scripts to use that plugin?
  • Is it supposed to replace the maven release plugin (e.g. it would add more checks)?

Thx

3

The long term idea is to then put indeed that in xwiki/xwiki-commons. But I want to experiment and be able to quickly release before it’s stable, hence the request for an xwiki-contrib repository in the meantime.

It’s an option, but I’m not a big fan of it clearly: it’s big and will probably be noisy in that repo. The only advantage I can see is that it might have a limited lifespan. I’m just not sure yet how long it will exist in a repo…

The idea is to be able to use that plugin when performing a release of a contrib project: configure the plugin in the pom or call directly the proper plugin goal: you’d do a mvn xwiki-release:release (names to be fixed) and it would automatically perform checks and post operation on top of the normal release plugin (e.g. put the right profiles, check JDK version, fix up revapi ignores, etc)

On the long run yes

yes

4

It does not really make any sense in xwiki-dev-tools because it’s currently designed to contain things which are not released and have very different lifecycles anyway, while this plugin needs to be released to be used.

5

Yes, I had not understood initially that Simon wanted to replace the default maven release plugin with this plugin. I thought it was a maven plugin to be used in our release scripts, when doing a release of xwiki. Hence why I thought it was logical to be put in xwiki-dev-tools.

I now understand that the goal is to do the opposite: to bring a lot of release actions from xwiki-dev-tools inside that custom xwiki maven release plugin (and thus lighten the release script) so that we could run it anywhere (on a release machine, inside jenkins, etc).

Thx