Sorry for the discussion in the general blacktie section. This would have been better under the deploy article.
I went ahead and built my own using the instructions under building thirdparty and building blacktie.
My apologies for not responding to you yesterday, we are actually putting a small update to BlackTie (CR2 together) - generally tidy up the layout of the distribution on disk, e.g. a consolidated lib folder (lib/cxx lib/java etc).
Plus a further apology, I had not "promoted" our build artifacts to the main JBoss repository (release is a two-stage process for our new Nexus repo and I forgot the second stage - oops), this should now be remedied, although building from source as you did would have populated your .m2 folder correctly anyway.
Sorry for the confusion and hope you are enjoying your time with BlackTie. CR2 should drop either today or Monday but it is very similar to CR1, the main code differences are:
1. Allow environment variable substitution in btconfig.xml (intended so that you dont need to search and replace so many variables to get the examples running).
2. Allow the IP address of a server to be used in the btconfig.xml for "btadmin startup/shutdown"
Thanks for looking at our project,
Actually, I also realised that the example poms do not have the configuration in them to use the external Maven repository. For CR1 you can edit your ~/.m2/settings.xml as per: http://community.jboss.org/wiki/MavenGettingStarted-Developers
I will update the poms for CR2 so that this configuration is not required.