We'll move the TI parser to a subpackage just to keep the codebase clean.
The first step is creating a copy of the parser in the subpackage, deprecating the old one and replacing the old one with the new one when the user updates the plugin.
The second step is removing the old parser in a later release.
There is an old issue https://issues.jenkins-ci.org/browse/JENKINS-30001 about a second step refactor. as far as I remember is was to be backwards compatible so we we're doing over two steps.
Probably still needs to be finished.
We wrote:
We'll move the TI parser to a subpackage just to keep the codebase clean.
The first step is creating a copy of the parser in the subpackage, deprecating the old one and replacing the old one with the new one when the user updates the plugin.
The second step is removing the old parser in a later release.
This is the issue for the second step.
Step 1: https://issues.jenkins-ci.org/browse/JENKINS-30000 Step 2: https://issues.jenkins-ci.org/browse/JENKINS-30001