[jbosstools-issues] [JBoss JIRA] (JBDS-3297) Download/Import Existing OpenShift Project

[Burr Sutter (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040960#comment-13040960 ] 

Burr Sutter commented on JBDS-3297:
-----------------------------------

[~rruss] it depends on the maturity of our Docker tooling.   At the time this jira was crafted it was assumed that the Docker tooling would NOT be ready in time, therefore the "docker build/docker run" would happen outside of Eclipse - via the command line.   The key thing about step "j" is that it is the same .war/.ear file that is deployable to:
a) OpenShift Enterprise v3 and v2 running EAP (via Eclipse-based OpenShift Tools)
b) localhost EAP (via Run As Run on Server)
c) local Docker container running EAP  (via command-line or Eclipse-based Docker Tools)
For Docker containers, the community will be focused on Centos+Wildfly (at Docker Hub) and there will also be a RHEL/Atomic+EAP (though not available at Docker Hub).

> Download/Import Existing OpenShift Project
> ------------------------------------------
>
>                 Key: JBDS-3297
>                 URL: https://issues.jboss.org/browse/JBDS-3297
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: openshift, requirements
>            Reporter: Burr Sutter
>            Assignee: Max Rydahl Andersen
>            Priority: Blocker
>
> Use Case #1 - Download/Import Existing OpenShift Project
> a) Assume OpenShift is started remotely and provides an entrypoint URL (e.g. http://localhost:8080/osapi/v1beta1/projects)
> b) Assume end-user is logged in (ignore auth for now)
> c) Assume OpenShift already has some deployed "projects", this "project" definition includes the buildconfig, deployconfig, docker image, source git URL, routes and services.
> d) Eclipse user will open a dialog and enter the URL from step a
> e) Eclipse user will see a list of "things" associated with "projects" from step 1c
> "things" 
> f) Embedded in one of those things is a Git URL - that will be displayed to the user who will agree to git clone it [1f]
> g) If the downloaded items include a Maven project, the Eclipse user will see a newly configured Eclipse project based on Maven with the appropriately configured facets
> h) If there is no pom.xml, the Eclipse user will see a newly configured generic Eclipse project containing the downloaded files
> i) It is expected that a Maven-based Java project will build locally (leveraging Maven Central and/or maven.repository.redhat.com)
> j) It is expected that a Maven-based Java project will deploy to a localhost EAP/Wildfly or a locally running Docker container:
> docker run -it -p 8080:8080 openshift/wildfly-8-centos 
> [1f] https://github.com/openshift/origin/blob/master/examples/sample-app/application-template-dockerbuild.json#L76



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)