[JBoss JIRA] (JBIDE-19849) As a user I want to easily show my (v3) application in a browser
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19849?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19849:
------------------------------------------
This was implemented as item in the context menu of a project or route (children of a v3 connection) in the OpenShift explorer:
!show-in-browser-1.png!
If there are several routes for a given project, we'll list them and ask you to pick the one that you want to open in a browser:
!show-in-browser-2.png!
> As a user I want to easily show my (v3) application in a browser
> ----------------------------------------------------------------
>
> Key: JBIDE-19849
> URL: https://issues.jboss.org/browse/JBIDE-19849
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: v3
> Fix For: 4.3.0.Beta1
>
>
> The tooling should allow the user to easily open up the application in a browser without having to look the url up in some property of the resources.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19787) As a user I want to import existing OpenShift projects into my Eclipse workspace
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19787?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19787:
-------------------------------------
Labels: import_wizard new_and_noteworthy (was: import_wizard)
> As a user I want to import existing OpenShift projects into my Eclipse workspace
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19787
> URL: https://issues.jboss.org/browse/JBIDE-19787
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: import_wizard, new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
> Attachments: import-application-2.png, import-application-3.png, import-application.png
>
>
> This is the case where a user has added resources via the CLI or console and wants to create an Eclipse project in order to start developing.
> The Eclipse project nature will be of the appropriate type as inferred from the source.
> Main focus is to correctly import java/maven projects or “General” project otherwise.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3297) Download/Import Existing OpenShift Project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3297?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim commented on JBDS-3297:
----------------------------------------
This was partially implemented. This was only implemented as explicit operation. This was not implemented as part of the new-application wizard, we went out of time for this to happen. See JBIDE-19787 for further details.
> 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
> Labels: new_and_noteworthy
> Fix For: 9.0.0.Beta1
>
>
> 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/appli...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3297) Download/Import Existing OpenShift Project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3297?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim resolved JBDS-3297.
------------------------------------
Labels: new_and_noteworthy (was: )
Resolution: Partially Completed
> 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
> Labels: new_and_noteworthy
> Fix For: 9.0.0.Beta1
>
>
> 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/appli...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19787) As a user I want to import existing OpenShift projects into my Eclipse workspace
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19787?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-19787.
--------------------------------------
Resolution: Partially Completed
> As a user I want to import existing OpenShift projects into my Eclipse workspace
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19787
> URL: https://issues.jboss.org/browse/JBIDE-19787
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: import_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: import-application-2.png, import-application-3.png, import-application.png
>
>
> This is the case where a user has added resources via the CLI or console and wants to create an Eclipse project in order to start developing.
> The Eclipse project nature will be of the appropriate type as inferred from the source.
> Main focus is to correctly import java/maven projects or “General” project otherwise.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19787) As a user I want to import existing OpenShift projects into my Eclipse workspace
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19787?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19787:
------------------------------------------
This was partially implemented. This was only implemented as explicit operation. This was not implemented as part of the new-application wizard, we went out of time for this to happen.
You can now select a connection or a project and pick "Import Application" from the context menu. You'd get to the same wizard via menu File->Import->OpenShift->Existing OpenShift Application if you select a v3 connection in the connection dialog.
!import-application.png!
You get all projects and their build configs listed:
!import-application-2.png!
As soon as you pick a build-config you can get to page2 where you specify the clone destination:
!import-application-3.png!
> As a user I want to import existing OpenShift projects into my Eclipse workspace
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19787
> URL: https://issues.jboss.org/browse/JBIDE-19787
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: import_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: import-application-2.png, import-application-3.png, import-application.png
>
>
> This is the case where a user has added resources via the CLI or console and wants to create an Eclipse project in order to start developing.
> The Eclipse project nature will be of the appropriate type as inferred from the source.
> Main focus is to correctly import java/maven projects or “General” project otherwise.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19787) As a user I want to import existing OpenShift projects into my Eclipse workspace
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19787?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19787:
-------------------------------------
Attachment: import-application.png
import-application-2.png
import-application-3.png
> As a user I want to import existing OpenShift projects into my Eclipse workspace
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19787
> URL: https://issues.jboss.org/browse/JBIDE-19787
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: import_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: import-application-2.png, import-application-3.png, import-application.png
>
>
> This is the case where a user has added resources via the CLI or console and wants to create an Eclipse project in order to start developing.
> The Eclipse project nature will be of the appropriate type as inferred from the source.
> Main focus is to correctly import java/maven projects or “General” project otherwise.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months