I'm not crazy about this. If the code is deprecated, it will eventually be deleted. No need to shuffle it around before deleting it.
If the code isn't deprecated, we support it. Putting it into a "legacy" dir just confuses the issue, especially if you were to change the Maven groupId too. No need to shuffle it around. If there is code that is legacy and unsupported, I would rather discuss deleting it than moving it. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#issuecomment-52471712
