[JBoss JIRA] (JBIDE-24984) Server adapter: if created from "New application" wizard it wont autostart
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24984?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24984:
-------------------------------------
Fix Version/s: 4.5.x
> Server adapter: if created from "New application" wizard it wont autostart
> --------------------------------------------------------------------------
>
> Key: JBIDE-24984
> URL: https://issues.jboss.org/browse/JBIDE-24984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Andre Dietisheim
> Priority: Minor
> Fix For: 4.5.x
>
>
> # EXEC: create a new application (ex. eap based one, can be any type) in OpenShift
> # ASSERT: resources are created successfully
> # EXEC: when asked, have it imported to your workspace
> # ASSERT: app source code is imported to the Eclipse workspace
> # EXEC: when asked have it create a server adapter
> Result:
> The server adapter wont start automatically as it does when you create it manually for an existing application (ex. via context menu for a service in OpenShift explorer)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24984) Server adapter: if created from "New application" wizard it wont autostart
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-24984:
----------------------------------------
Summary: Server adapter: if created from "New application" wizard it wont autostart
Key: JBIDE-24984
URL: https://issues.jboss.org/browse/JBIDE-24984
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.5.1.AM1
Reporter: Andre Dietisheim
# EXEC: create a new application (ex. eap based one, can be any type) in OpenShift
# ASSERT: resources are created successfully
# EXEC: when asked, have it imported to your workspace
# ASSERT: app source code is imported to the Eclipse workspace
# EXEC: when asked have it create a server adapter
Result:
The server adapter wont start automatically as it does when you create it manually for an existing application (ex. via context menu for a service in OpenShift explorer)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24984) Server adapter: if created from "New application" wizard it wont autostart
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24984?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24984:
-------------------------------------
Priority: Minor (was: Major)
> Server adapter: if created from "New application" wizard it wont autostart
> --------------------------------------------------------------------------
>
> Key: JBIDE-24984
> URL: https://issues.jboss.org/browse/JBIDE-24984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Andre Dietisheim
> Priority: Minor
>
> # EXEC: create a new application (ex. eap based one, can be any type) in OpenShift
> # ASSERT: resources are created successfully
> # EXEC: when asked, have it imported to your workspace
> # ASSERT: app source code is imported to the Eclipse workspace
> # EXEC: when asked have it create a server adapter
> Result:
> The server adapter wont start automatically as it does when you create it manually for an existing application (ex. via context menu for a service in OpenShift explorer)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-3280) Screencasts: Java EE
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3280?page=com.atlassian.jira.plugin.... ]
Martin Malina resolved JBDS-3280.
---------------------------------
Resolution: Out of Date
> Screencasts: Java EE
> --------------------
>
> Key: JBDS-3280
> URL: https://issues.jboss.org/browse/JBDS-3280
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: documentation, requirements
> Reporter: Burr Sutter
> Assignee: Martin Malina
> Priority: Minor
> Fix For: 10.x
>
>
> As a new Eclipse+Java EE developer, I need educational screencasts, around 5 minutes each that educate me on a specific Java EE development capabilities of JBDS.
> Use cases include:
> - JPA - how to add one, content-assist, relationships
> - database reverse engineering via DTP vs Forge
> - JAX-RS: creation of new endpoints, content-assist, tester - including the GET/POST/PUT/DELETE with JSON payloads
> - JAX-WS: creation of new endpoints, content-assist, tester
> - CDI special features
> - Servlets
> - JSF
> - deployment to localhost EAP
> - deployment to remove EAP
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-3251) Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3251?page=com.atlassian.jira.plugin.... ]
Martin Malina resolved JBDS-3251.
---------------------------------
Resolution: Won't Fix
> Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3251
> URL: https://issues.jboss.org/browse/JBDS-3251
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: documentation, requirements
> Reporter: Max Rydahl Andersen
> Assignee: Martin Malina
> Fix For: 10.x
>
>
> suggestions from F2F:
> |Maven Top 10 Use Cases| Import, multi-module, run on server, package vs install, update, adjust profiles, dependencies adds/removes|
> |Java EE Top 10 Use Cases JPA, db reveng, JAX-RS (including testing), CDI, content assist, Servlets, JSF, etc
> HTML5/Hybrid Mobile|
> |OpenShift v3| start, stop, deploy apps
> |eGit Top Use Cases|
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-3281) Screencasts: Git
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3281?page=com.atlassian.jira.plugin.... ]
Martin Malina resolved JBDS-3281.
---------------------------------
Resolution: Out of Date
> Screencasts: Git
> ----------------
>
> Key: JBDS-3281
> URL: https://issues.jboss.org/browse/JBDS-3281
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: documentation, requirements
> Reporter: Burr Sutter
> Assignee: Martin Malina
> Priority: Minor
> Fix For: 10.x
>
>
> As a Java EE developer, new to Eclipse + Git, I need educational, 5 minute screencasts on the most common uses of Git inside of Eclipse.
> Use cases include:
> 1) as a new member of the team, just having only installed JBDS, I need to add an element to the project
> assume a clone, add (or modify), commit, push workflow
> a- Getting started as a new member of an existing git project (I need to clone a repo, import the project, insure my facets/Maven are set correctly)
> b- navigate/browse an existing repository
> c- git add - for a newly added class or file
> d- git commit -a
> e- git push
> as a new member of the team, just having only installed JBDS, I need to resolve a pull request.
> 2) other scenarios
> - git init a current project that I have in my workspace (and should I move it outside of my workspace first)
> - git checkout for a specific branch - getting Maven and Eclipse Facets to properly recognize my newly checked out branch
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24965) Server adapter: fails to "Restart in Debug"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24965?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24965:
-------------------------------------
Story Points: 8 (was: 4)
> Server adapter: fails to "Restart in Debug"
> -------------------------------------------
>
> Key: JBIDE-24965
> URL: https://issues.jboss.org/browse/JBIDE-24965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.AM3
>
> Attachments: image-2017-09-02-01-06-58-751.png
>
>
> steps:
> # EXEC: Create a nodejs-mongo-persistent application
> # EXEC/ASSERT: Create a server adapter for the service nodejs-mongo-persistent
> # EXEC: start the server adapter via "Debug"
> # ASSERT: debugging works
> # EXEC: restart the server adapter via "Restart in Debug"
> Result:
> Debugging fails, you get the following error:
> !image-2017-09-02-01-06-58-751.png!
> In the log you find the following entry:
> {code}
> org.eclipse.core.runtime.CoreException: Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.mapPortForwarding(OpenShiftLaunchController.java:357)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:83)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:221)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-09-02 00:32:34.031
> !MESSAGE Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24676) CDK3 server adapter's console view is using wrong coding on all platforms
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24676?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-24676 at 9/5/17 8:57 AM:
---------------------------------------------------------------
[~budhrg] Thanks a lot, that was fast! On Fedora 26 I am having almost no problem with cdk. :)
was (Author: odockal):
[~budhrg] Thanks a lot, that was fast! On Fedora 26 I am not having almost any problem with cdk. :)
> CDK3 server adapter's console view is using wrong coding on all platforms
> -------------------------------------------------------------------------
>
> Key: JBIDE-24676
> URL: https://issues.jboss.org/browse/JBIDE-24676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.5.0.AM2
> Environment: Windows, Linux, macOS
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
> Attachments: Console_output.png, cdk_console_coding.png, dot_spinner_error.png, no_progressbar.png, progress-win.PNG, progress.png
>
>
> Console view on all platforms show strange characters. See the pic.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24676) CDK3 server adapter's console view is using wrong coding on all platforms
by Budh Ram Gurung (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24676?page=com.atlassian.jira.plugi... ]
Budh Ram Gurung edited comment on JBIDE-24676 at 9/5/17 8:53 AM:
-----------------------------------------------------------------
[~odockal], Please download the binary from here https://drive.google.com/a/redhat.com/file/d/0B3HNnIbLSHKSWGwzQWc4X0cxaFk... .
I am also interested in setting up testing environment at my Fedora 26 machine too :)
was (Author: budhrg):
[~odockal], Please download the binary from here https://drive.google.com/a/redhat.com/file/d/0B3HNnIbLSHKSWGwzQWc4X0cxaFk... .
> CDK3 server adapter's console view is using wrong coding on all platforms
> -------------------------------------------------------------------------
>
> Key: JBIDE-24676
> URL: https://issues.jboss.org/browse/JBIDE-24676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.5.0.AM2
> Environment: Windows, Linux, macOS
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
> Attachments: Console_output.png, cdk_console_coding.png, dot_spinner_error.png, no_progressbar.png, progress-win.PNG, progress.png
>
>
> Console view on all platforms show strange characters. See the pic.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months