[JBoss JIRA] (JBIDE-21608) "Show In -> Web Browser via Live Reload" on EJB module should be disabled
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21608?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-21608:
----------------------------------
Story Points: 2
> "Show In -> Web Browser via Live Reload" on EJB module should be disabled
> -------------------------------------------------------------------------
>
> Key: JBIDE-21608
> URL: https://issues.jboss.org/browse/JBIDE-21608
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Xavier Coulon
> Fix For: 4.4.x
>
>
> This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled.
> Rob did his part for Show in Server, but he says separate JIRAs are needed in other components.
> So for Livereload, there are these two items that should be disabled on an ejb module:
> Show in -> Web Browser via Livereload
> Show in -> Web Browser on External device
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22227?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22227:
-------------------------------------
I don't believe that this can be solved on the app-server at all, since it's a bug in how eclipse debugs java apps in general. When a marker is set, eclipse gains a reference to the class, thus preventing it from being garbage collected naturally.
I don't believe there are any associated bugs with JDK or with WildFly, because the bug is not caused by those projects. The bug is caused by eclipse.
> Hotcode replace fails on local wildfly if breakpoint is set
> -----------------------------------------------------------
>
> Key: JBIDE-22227
> URL: https://issues.jboss.org/browse/JBIDE-22227
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail.
> This will pop up a dialog asking to restart the module or the server, which is expected. However, after that, non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't.
> Workflow:
> 1) Create a dynamic web project with simple servlet
> 2) Start a wildfly 10 in debug mode and deploy the web project
> 3) Run-on-server the servlet object and verify it shows expected output
> 4) Set a breakpoint inside the doGet() method
> 5) refresh browser (breakpoint gets hit), press play
> 6) Make a non-breaking change (change text inside doGet())
> 7) refresh website, verify breakpoint is hit, website content is updated
> 8) make a breaking change by adding a new method
> 9) hotcode-replace dialog appears. Press 'restart module'
> 10) refresh web browser, verify breakpoint is hit, output has changed as expected
> 11) make a non-breaking change in output of doGet()
> 12) ASSERT: hotcode replace dialog does NOT show - THIS STEP FAILS
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-22268) Server adapter wizard: create unit tests
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22268?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22268:
--------------------------------
Sprint: (was: devex #113 April 2016)
> Server adapter wizard: create unit tests
> ----------------------------------------
>
> Key: JBIDE-22268
> URL: https://issues.jboss.org/browse/JBIDE-22268
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: server_adapter_wizard
> Fix For: 4.4.0.Alpha2
>
>
> The server adapter wizard should be unit tested. Given it's implemented using databinding and a presentation model (ServerSettingsWizardPageModel) the model can be unit tested (ex. #setService and then test all it's states: source path, deploy project etc.).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3282:
------------------------------
Sprint: devex #114 May 2017 (was: devex #113 April 2016)
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: documentation, openshift, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: screencast
> Fix For: 10.0.0.Alpha1
>
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set
by Thomas Mäder (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22227?page=com.atlassian.jira.plugi... ]
Thomas Mäder commented on JBIDE-22227:
--------------------------------------
I have opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=492265 against the eclipse JDT debugger.
> Hotcode replace fails on local wildfly if breakpoint is set
> -----------------------------------------------------------
>
> Key: JBIDE-22227
> URL: https://issues.jboss.org/browse/JBIDE-22227
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail.
> This will pop up a dialog asking to restart the module or the server, which is expected. However, after that, non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't.
> Workflow:
> 1) Create a dynamic web project with simple servlet
> 2) Start a wildfly 10 in debug mode and deploy the web project
> 3) Run-on-server the servlet object and verify it shows expected output
> 4) Set a breakpoint inside the doGet() method
> 5) refresh browser (breakpoint gets hit), press play
> 6) Make a non-breaking change (change text inside doGet())
> 7) refresh website, verify breakpoint is hit, website content is updated
> 8) make a breaking change by adding a new method
> 9) hotcode-replace dialog appears. Press 'restart module'
> 10) refresh web browser, verify breakpoint is hit, output has changed as expected
> 11) make a non-breaking change in output of doGet()
> 12) ASSERT: hotcode replace dialog does NOT show - THIS STEP FAILS
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-165) Refactor the Connection Wizard [EBZ#492420]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/ERT-165?page=com.atlassian.jira.plugin.sy... ]
Fred Bricon reassigned ERT-165:
-------------------------------
Story Points: 23
Assignee: Xavier Coulon
> Refactor the Connection Wizard [EBZ#492420]
> -------------------------------------------
>
> Key: ERT-165
> URL: https://issues.jboss.org/browse/ERT-165
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> Refactor the connection wizard to provide:
> - a table with all existing Docker instances (native, Docker for Mac/Windows and Docker Machine)
> - a simplified form to specify custom settings, more directly based on the env variables that are used by the Docker CLI client (DOCKER_HOST, DOCKER_TLS_VERIFY and DOCKER_CERT_PATH)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-165) Refactor the Connection Wizard [EBZ#492420]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/ERT-165?page=com.atlassian.jira.plugin.sy... ]
Fred Bricon updated ERT-165:
----------------------------
Sprint: devex #114 May 2017 (was: devex #113 April 2016)
> Refactor the Connection Wizard [EBZ#492420]
> -------------------------------------------
>
> Key: ERT-165
> URL: https://issues.jboss.org/browse/ERT-165
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> Refactor the connection wizard to provide:
> - a table with all existing Docker instances (native, Docker for Mac/Windows and Docker Machine)
> - a simplified form to specify custom settings, more directly based on the env variables that are used by the Docker CLI client (DOCKER_HOST, DOCKER_TLS_VERIFY and DOCKER_CERT_PATH)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-22279) Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22279?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22279:
------------------------------------
Dependency on mylyn.pde and mylyn.java comes from three connectors in Central:
* Mylyn support for Eclipse EGit and GitHub https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
* Mylyn support for the Subversion version control system, including SVNKit https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
* Mylyn support for reporting JBoss JIRAs and Red Hat Bugzillas https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
Since our Central includes v3.18.0 and Neon.M6 contains v3.19.0, this is a no-brainer: we need to simply include the latest version so that we don't attempt to install something older than what's already installed.
> Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22279
> URL: https://issues.jboss.org/browse/JBIDE-22279
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central-update, target-platform, upstream
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha2
>
> Attachments: jbide22279.png
>
>
> Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed:
> {code} Software being installed: Mylyn Context Connector: Plug-in Development 3.18.0.v20151013-1847 (org.eclipse.mylyn.pde_feature.feature.group 3.18.0.v20151013-1847)
> Software currently installed: Mylyn Context Connector: Java Development 3.19.0.v20160111-2059 (org.eclipse.mylyn.java_feature.feature.group 3.19.0.v20160111-2059)
> {code}
> Opening this issue just as a reminder to check that we're using the same version of Neon/Mylyn in Central & TP so we don't hit this problem again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22195:
--------------------------------
Story Points: 4
Sprint: devex #114 May 2017 (was: devex #113 April 2016)
> Docker-machine look-up does not work
> ------------------------------------
>
> Key: JBIDE-22195
> URL: https://issues.jboss.org/browse/JBIDE-22195
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.4.0.Alpha2
>
>
> The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying :
> {quote}
> The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin
> {quote}
> even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month