[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-602) OpenShift: Document Downloading/Importing existing OS Project

[Misha Ali (JIRA)]

     [ https://issues.jboss.org/browse/TOOLSDOC-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Misha Ali updated TOOLSDOC-602:
-------------------------------
    Description: 
Document the following use case:

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

  was:
Document the following use case:

se 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



> OpenShift: Document Downloading/Importing existing OS Project
> -------------------------------------------------------------
>
>                 Key: TOOLSDOC-602
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-602
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Feature Request
>    Affects Versions: 4.3.0.Final
>            Reporter: Misha Ali
>            Assignee: Misha Ali
>              Labels: openshift
>             Fix For: 4.3.0.Final
>
>
> Document the following use case:
> 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)