[JBIDE-19555] Refactor to use openshift-restclient-java

[jcantrill]

@adietish Please merge ASAP along with the client auth changes. This change utilizes the new repo

[adietish]

why are you removing the Eclipse project file? Without it I can hardly see Eclipse properly working? I bet this was by mistake.

[adietish]

why would you want to ignore those Eclipse configuration files (all of them, the ones below, too)?

[adietish]

see above

[adietish]

@jcantrill

dependencies are specified in the manifest file and are pulled in when you import.
Given thats the case, what is the point of placing these file under source control

manifest is runtime, java build path/pom are build-time. So m2e bridges manifest to build-time by setting the java build path from what I sees in manifest.
So the point is that you force people to use m2e. You can only use Eclipse to develop plugin projects, Whats the point of forcing people to install m2e? It only causes initial lifecycle errors upon import which you have to solve upon import, Furthermore m2e frequently gets out-of-sync with the settings in .project and needs to be to told update (Maven->Update project). M2e slows the build cycle and has no additional benefit. Compiling and launching is all done with Eclipse, maven just sits there and idles. I really dont see any benefit in having m2e involved here.
Furthermore we are in a manifest-first approach here, not pom first: look at our poms, they're basically empty, maven gets it's settings from what's in manifest, not the other way round. Why would you want to inverse the approach and state that what maven detects (from Manifest) should be set to Eclipse settings?

[adietish]

rebased, removed empty plugin.xml, added .classpath back in, removed m2e natures:
#595