AnsweredAssumed Answered

Mavenizing Smack

Question asked by rcollier Champion on Nov 22, 2010
Latest reply on Nov 22, 2010 by rcollier

I have been attempting to mavenize Smack, and I have come up with a few questions and suggestions related to how Smack is deployed.  Currently there are 4 jar files as artifacts from the build process, smack, smack-debug, smackx and smack-jingle.  My question is, why?  Can anyone enlighten me as to why there is this separation?


A part of converting to maven, I would like to create 1 or possibly 2 artifacts only.

  1. smack - which would be everything currently in the aforementioned 4 jars.
  2. smack-core - This is assuming that someone would need access to core xmpp functionality without any of the extensions.


The intent is to get these deployed to the central maven repos along with the upcoming release of a 3.2 Beta.


I am hoping for some feedback here first, and then possibly putting a similar type post in the open forums to hopefully get more user feedback.  I look forward to your suggestions/comments.