Mark deprecated methods for removal

[laeubi]

No description provided.

[github-actions]

Test Results

0 files   -   663  0 suites   - 663   0s ⏱️ - 1h 14m 43s
0 tests  - 2 211  0 ✅  - 2 164  0 💤  -  47  0 ❌ ±0 
0 runs   - 6 777  0 ✅  - 6 634  0 💤  - 143  0 ❌ ±0 

Results for commit 2e0e6e6. ± Comparison against base commit 91eebf3.

♻️ This comment has been updated with latest results.

[laeubi]

We can't use since / forRemoval here due to java 1.8 compatibility. @tjwatson since this is deprecated since ages (somewhere back to 2006 if I look at the git history) should we probably just remote them without further notice?

[tjwatson]

We can't use since / forRemoval here due to java 1.8 compatibility. @tjwatson since this is deprecated since ages (somewhere back to 2006 if I look at the git history) should we probably just remote them without further notice?

I'm not that motivated to remove individual methods from what I consider a completely deprecated package.

[laeubi]

I'm not that motivated to remove individual methods from what I consider a completely deprecated package.

Maybe we should then add the new deprecated directive to that package? I assumed until now that only the implementation (that already resides in a fragment) is deprecated but not the API itself (what is used in P2 and PDE...).