Party of the first part
Over the past few days, we've worked to make the bits of TorqueBox that are packaged up and exposed as RubyGems a little less crazytown.
If you recall, you've been in the habit of doing stuff like:
Or more recently…
org.torquebox prefix has been leaking in from the fact we
build all of TorqueBox, including RubyGems, using Maven.
We've found some options, though, to remove that cruft. And with these changes, we have some significantly saner gem names.
We have included some hooks for backwards-compatibility, which should
issue a deprecation warning if you continue to use the
So, begin doing this:
Party of the second part
The messaging and naming clients are probably the most-used gems in
applications. To make requiring them even easier, we now have a top-level
torquebox gem that depends on both of these client gems.
So, it's even easier:
Fight for your right to party
Lastly, we have been hosting a RubyGems repository, which is useful when working with our CI-built development builds. The repository is located here:
Instructions for its use are at that location, along with a list of the current gems.