[JBoss JIRA] (TOOLSDOC-606) Docker: Document basic docker tooling
by Misha Ali (JIRA)
Misha Ali created TOOLSDOC-606:
----------------------------------
Summary: Docker: Document basic docker tooling
Key: TOOLSDOC-606
URL: https://issues.jboss.org/browse/TOOLSDOC-606
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Feature Request
Components: General documentation issues
Reporter: Misha Ali
Assignee: Misha Ali
Fix For: 4.3.0.Final
Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers.
Expected end-user flow 1:
0) Installation - assumes boot2docker pre-installed on the end-user's machine
1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag.
2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location.
3) I start (docker run) the image which auto-starts the embedded app server
4) I can then deploy my .war or .ear to the running app server
5) I can restart the running app server in debug mode and run the debugger
6) I can undeploy and redeploy my .war or .ear
7) I can stop/restart the running, embedded app server
8) I can then commit (docker commit)
9) then I can publish my changes (docker push)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-605) Git: Document the easy import feature
by Misha Ali (JIRA)
Misha Ali created TOOLSDOC-605:
----------------------------------
Summary: Git: Document the easy import feature
Key: TOOLSDOC-605
URL: https://issues.jboss.org/browse/TOOLSDOC-605
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Feature Request
Components: General documentation issues
Reporter: Misha Ali
Assignee: Misha Ali
Fix For: 4.3.0.Final
Document this use case: As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
The mission here is to make the Git experience much more user friendly.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-604) OpenShift: Document creating a deployment from a template
by Misha Ali (JIRA)
Misha Ali created TOOLSDOC-604:
----------------------------------
Summary: OpenShift: Document creating a deployment from a template
Key: TOOLSDOC-604
URL: https://issues.jboss.org/browse/TOOLSDOC-604
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Feature Request
Components: General documentation issues
Reporter: Misha Ali
Assignee: Misha Ali
Fix For: 4.3.0.Final
Document this use case: Use Case #3
Create Deployment from Template
a) Assume OpenShift is started remotely and provides an entrypoint URL
b) Assume end-user is logged in (ignore auth for now)
c) Eclipse user will open a dialog and enter the URL from step a
d) Eclipse user will then be presented with a list of templates from the template library
(initially a set of files on the local filesystem until openshift has a real template library api)
e) The template list should allow sorting so that higher priority items are at the top
We will likely need some form of categorization for templates also
f) The template list should be searchable by keyword
g) Eclipse user will select a particular template and
h) Create a new openshift deployment based on selected template
i) follow steps JBDS-3297 f through j (clone, import, project facets, etc)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-603) Openshift: Document how to push changes to an existing OS Project
by Misha Ali (JIRA)
Misha Ali created TOOLSDOC-603:
----------------------------------
Summary: Openshift: Document how to push changes to an existing OS Project
Key: TOOLSDOC-603
URL: https://issues.jboss.org/browse/TOOLSDOC-603
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Feature Request
Components: General documentation issues
Reporter: Misha Ali
Assignee: Misha Ali
Fix For: 4.3.0.Final
Document this use case:
Use Case #2 Push changes to Existing OpenShift Project
a) assumes the steps in Use Case #1 JBDS-3297
b) assumes the end-user has uploaded his SSH keys (to allow for git push)
c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc
d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP
e) Eclipse user will test (JUnit, Arquillian)
f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image)
g) Eclipse user will git add and git commit as appropriate
h) Eclipse user will git push to the original URL provided in Use Case #1
i) Eclipse user will await the automatic rebuild of a new image, deployment of the same
j) Eclipse user will then be provided a URL and the browser can be opened automatically
Note:
i) auto-build=true, auto-deploy=true
assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c.
A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear.
If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-602) OpenShift: Document Downloading/Importing existing OS Project
by Misha Ali (JIRA)
Misha Ali created TOOLSDOC-602:
----------------------------------
Summary: 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
Reporter: Misha Ali
Assignee: Misha Ali
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/appli...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-600) Websockets: Document using Annotations
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-600?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-600:
-------------------------------
Summary: Websockets: Document using Annotations (was: Weblogic: Document using Annotations)
> Websockets: Document using Annotations
> --------------------------------------
>
> Key: TOOLSDOC-600
> URL: https://issues.jboss.org/browse/TOOLSDOC-600
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues
> Reporter: Misha Ali
> Assignee: Misha Ali
> Fix For: 4.3.0.Final
>
>
> Document basic Websockets annotations we can use with JBDS: As a Java EE developer, I wish to take advantage of the new Websockets capability.
> Content-assist for annotations such as @ServerEndpoint, @OnMessage.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-600) Weblogic: Document using Annotations
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-600?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-600:
-------------------------------
Summary: Weblogic: Document using Annotations (was: Weblogic: Using Annotations)
> Weblogic: Document using Annotations
> ------------------------------------
>
> Key: TOOLSDOC-600
> URL: https://issues.jboss.org/browse/TOOLSDOC-600
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues
> Reporter: Misha Ali
> Assignee: Misha Ali
> Fix For: 4.3.0.Final
>
>
> Document basic Websockets annotations we can use with JBDS: As a Java EE developer, I wish to take advantage of the new Websockets capability.
> Content-assist for annotations such as @ServerEndpoint, @OnMessage.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-600) Weblogic: Using Annotations
by Misha Ali (JIRA)
Misha Ali created TOOLSDOC-600:
----------------------------------
Summary: Weblogic: Using Annotations
Key: TOOLSDOC-600
URL: https://issues.jboss.org/browse/TOOLSDOC-600
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Feature Request
Components: General documentation issues
Reporter: Misha Ali
Assignee: Misha Ali
Fix For: 4.3.0.Final
Document basic Websockets annotations we can use with JBDS: As a Java EE developer, I wish to take advantage of the new Websockets capability.
Content-assist for annotations such as @ServerEndpoint, @OnMessage.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-598) Document new JBDS+Fuse Installer
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-598?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-598:
-------------------------------
Affects Version/s: (was: 4.3.0.Final)
> Document new JBDS+Fuse Installer
> --------------------------------
>
> Key: TOOLSDOC-598
> URL: https://issues.jboss.org/browse/TOOLSDOC-598
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: Installation Guide
> Reporter: Misha Ali
> Assignee: Misha Ali
> Fix For: 4.3.0.Final
>
>
> Document a new installer (see linked JIRA for developer task) for the following use case: As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years