wojciech.kapcia@tigase.net opened 7 years ago
|
|
yes |
|
%kobit If I'm correct this would require changing package names. As a result, it will break API, so maybe it should be done in 8.0? |
|
Andrzej Wójcik wrote:
Definitely yes |
|
From my perspective, all works as expected. |
|
Issue with @PriorityQueueStrict@:
|
|
While working on #5379 I noticed that all tests started to fail when the change was made. It was due to using old path to the PriorityQueueStrict class. I've adjusted the converted to handle the change. Let's see next tests results. |
|
Some repositories were not adjusted, and jenkins didn't catch the change as old dependencies were used (for example 3.6.0-SNAPSHOT) which still contained old packages paths. I have:
|
Type |
Task
|
Priority |
Normal
|
Assignee | |
RedmineID |
6206
|
Version |
tigase-server-8.0.0
|
Spent time |
81h 15m
|
Currently tigase-utils and tigase-xmltools are inlined to tigase-server (reason was that OSGi prohibits packages across various jar) and it would be good to tackle "split packages" problem as new java9/jigsaw modules also forbid 'split packages' in modules.
%kobit yesno?