|
wojciech.kapcia@tigase.net opened 9 years ago
|
|
Good idea. |
|
|
I've added new annotation which allows to provide additional information. Given that in 7.2.x we are going to migrate to Tigase Kernel, which will handle plugins/components differently I've also created same issue #3954 |
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
3908
|
| Version |
tigase-server-7.1.0
|
| Spent time |
5h
|
Issue Votes (0)
Watchers (0)
Currently it's possible to enable deprecated plugin without knowing it was deprecated (except looking at the code) and run in in parallel with the new version.
For example recent split in
presenceplugin and explicit configuration of it (number of threads, for example) can lead to this situation, as new version is enabled by default.