Re: [jclouds] Add top-level legacy directory (#489)
> It's always better to discuss and propose things +1. Thanks for spurring on the discussion, @jdaggett! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#issuecomment-53711497
Re: [jclouds] Add top-level legacy directory (#489)
It's always better to discuss and propose things than losing the opportunity of sharing something good :) Thanks for bringing this up @jdaggett! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#issuecomment-52881307
Re: [jclouds] Add top-level legacy directory (#489)
I wanted to throw it out there to see what people thought about it. I have worked on many projects where we moved code, rather than deleted it from the repo. Thx for the feedback! Closing. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#issuecomment-52808350
Re: [jclouds] Add top-level legacy directory (#489)
Closed #489. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#event-155116316
Re: [jclouds] Add top-level legacy directory (#489)
Just to short-circuit unneeded discussion, we should *not* remove the older swift provider yet. We have not yet moved openstack-swift into core, not written a HP provider, and do not know how compatible the new provider is with older Swift instances. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#issuecomment-52537928
Re: [jclouds] Add top-level legacy directory (#489)
Agree in general with @andrewgaul and @everett-toews. Could you describe why you think this is needed and better than e.g. pointing users to the branch or the commit history if they need to see the old code? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#issuecomment-52536679
Re: [jclouds] Add top-level legacy directory (#489)
Just a thought... an alternative could be to remove them from the default build and add a -Plegacy profile build, leaving them where they are. If the concern from Jeremy is that moving say, openstack-swift and rackspace-cloudfiles* to the main jclouds project will cause confusion on which one to use, then I agree that we should move up the discussion of just deleting the old ones. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#issuecomment-52534069
Re: [jclouds] Add top-level legacy directory (#489)
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
Re: [jclouds] Add top-level legacy directory (#489)
:-1: no reason to add a top-level directory for this, which only communicates intent to a small number of developers and just adds clutter. If we want to hit existing users with a stick, we should rename the *provider id* to legacy-swift. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#issuecomment-52457767
Re: [jclouds] Add top-level legacy directory (#489)
[jclouds-pull-requests #1103](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1103/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#issuecomment-52359868
Re: [jclouds] Add top-level legacy directory (#489)
[jclouds ยป jclouds #1530](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1530/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#issuecomment-52358475
Re: [jclouds] Add top-level legacy directory (#489)
[jclouds-pull-requests-java-6 #14](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-6/14/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489#issuecomment-52353317
[jclouds] Add top-level legacy directory (#489)
This PR introduces a new top level directory to the repository for legacy code. There is a need to move APIs like swift/cloudfiles/cloudserver somewhere, but not delete them from the repository. We should consider moving any legacy/unsupported code into this directory. You can merge this Pull Request by running: git pull https://github.com/rackspace/jclouds proto/legacy-dir Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/489 -- Commit Summary -- * Add legacy directories and README.md -- File Changes -- A legacy/README.md (11) -- Patch Links -- https://github.com/jclouds/jclouds/pull/489.patch https://github.com/jclouds/jclouds/pull/489.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/489
