> My take: deprecate early, rather than late, even if replacement functionality > is not already there. I realize not > everybody would agree with me.
Or, as a halfway house, add a Javadoc warning that this code will soon be deprecated and then removed? Won't create a compiler deprecation warning (which seems a little harsh, since users can't avoid that without replacement functionality), but at least gives them a heads-up? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/237#issuecomment-30720607
