Thanks for the report lfiorino.
The warning can be resolved by using the EnvInject plugin instead of this plugin. If you must use this plugin and cannot switch your use to the better maintained EnvInject plugin, then you can resolve the warning by following the "update parent pom" and "update Jenkins version" steps in the "Improve a plugin" tutorial. Are you interested in adopting the plugin so that the warning can be resolved?
The plugin was last released 11 years ago. Unless someone adopts it, the warning is not likely to ever be fixed.
Thanks for the report lfiorino.
The warning can be resolved by using the EnvInject plugin instead of this plugin. If you must use this plugin and cannot switch your use to the better maintained EnvInject plugin, then you can resolve the warning by following the "update parent pom" and "update Jenkins version" steps in the "Improve a plugin" tutorial. Are you interested in adopting the plugin so that the warning can be resolved?
The plugin was last released 11 years ago. Unless someone adopts it, the warning is not likely to ever be fixed.