Separate the configuration for smack extension related classes from the smack jar.

Description

Currently the config files (smack-config.xml and smack.providers) both have references to classes in the smackx.jar, even though they are located in the smack.jar. This creates an unwanted runtime dependency.

Environment

None

Activity

Show:

Robin Collier January 20, 2014 at 2:40 AM

While not completely separated, all the providers for smackx and other jars is now moved into the jars containing the actual providers. The smack jar no longer has any direct references to external classes. This was done while resolving SMACK-286.

The only soft link that now exists is that the default config in the smack jar does have an extension initializer that will load the providers file in the smackx.jar if it is on the classpath. If it doesn't find the file, it does nothing.

Closing this task due to these changes.

Fixed

Details

Assignee

Reporter

Fix versions

Priority

Created May 3, 2012 at 2:14 PM
Updated October 28, 2020 at 1:28 PM
Resolved January 20, 2014 at 2:40 AM