Re: maven-rules for plugin version

[Ludovic Claude <ludovic.claude54@googlemail.com>]

The third field needs to be maven-plugin, as this is the type of the
artifact which is going to be affected by this rule. You can use * also,
it will work but it's less clear.
About the version, you are forced to specify the actual version of the
plugin, generic versions such as 'debian' or 1.x are not allowed because
of the way Maven resolves its plugin dependencies. That means that
unfortunately if one of the plugin used is upgraded in the Debian
repository, then we need to update all packages built with that plugin.

Ludovic

Gabriele Giacone a écrit :
> Ludovic Claude wrote:
>> Hello Gabriele,
>>
>> In the maven.rules file for your package, you can add the following line
>>
>> org.codehaus.mojo exec-maven-plugin maven-plugin s/.*/1.1.1/
>>
>> It should force the version of the plugin to 1.1.1 without needing any
>> patch.
> Thanks Ludovic. It works. I didn't try to change 3rd field in something
> else than "jar".
> But it seems we can't play with .x versions ie. s/.*/1.x/, isn't it?
> The ideal would be to satisfy dependency even if plugin version became
> 1.1.2 or 1.2 or at least to have a choice between strict (1.1.1) and
> permissive (1.x).
> 
> Cheers,
> Gabriele
> 
>