• proposed filenames: tigase-pubsub.jar and tigase-pubsub.jar.old (to avoid conflicts);

• include both binaries in tarballs as well;

• automatically load pubsub schema in installer.

As per outlined requirements:

• configured jenkins to build and deploy both versions;

• both installer and tarbals contain two libraries, old suffixed with @-2.2.0-SNAPSHOT.jar.old@;

• included schema was changed to version 3.0.0 from pubsub;

• new PubSub schema is loaded in the installer if pubsub component is selected.

Example packages for testing purposes will be generated in in the next nightly cycle.

I've tested last item with Postgresql and MySQL (work as expected) as remaining schemas require fixes (see subtask) but they are already included so once the schemas are corrected installer will pick changes automatically.

We can build the RC2 with new PubSub even if it still has issues with SQL Server schema. To our knowledge only one customer uses SQL Server and they will not be updating their servers on their own. We can fix the SQL Server code in the meantime before releasing final and having new PubSub in RC2 would give us opportunity to have it tested in a field.

Both binaries included as expected in RC2, schamas fixed;