March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21907) Server adapter: service details text is selectable (each line on its own)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21907?page=com.atlassian.jira.plugi... ] Jan Richter updated JBIDE-21907: -------------------------------- Attachment: selection.png > Server adapter: service details text is selectable (each line on its own) > ------------------------------------------------------------------------- > > Key: JBIDE-21907 > URL: https://issues.jboss.org/browse/JBIDE-21907 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Priority: Minor > Labels: openshift_v3, server_adapter_wizard > Attachments: selection.png > > > One can select the values in the Service detail part of the wizard. The fun part is they are all independent and can be selected on their own. > So once some line is selected, the only way to deselect it is to click inside it again - which places the annoying caret into the text. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-3552: ------------------------------------- [~mmalina] could you please verify this one? OpenShift has its own issue for this. This one is related only to docker incremental deployments. > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker, openshift > Reporter: Max Rydahl Andersen > Assignee: Martin Malina > Priority: Critical > Fix For: 9.1.0.CR1 > > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ] Marián Labuda reassigned JBDS-3552: ----------------------------------- Assignee: Martin Malina (was: Marián Labuda) > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker, openshift > Reporter: Max Rydahl Andersen > Assignee: Martin Malina > Priority: Critical > Fix For: 9.1.0.CR1 > > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21835) Server adapter: incremental deployment is broken

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21835?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-21835 at 3/18/16 7:25 AM: ---------------------------------------------------------------- Reopening, because Issue 1 still persists. After changing index.xhtml, ROOT.war is redeployed (stopped, started, replaced). This happens when local change is performed before starting OS3 Server Adapter. was (Author: mlabuda): Reopening, because Issue 1 still persists. After changing index.xhtml, ROOT.war is redeployed (stopped, started, replaced). > Server adapter: incremental deployment is broken > ------------------------------------------------ > > Key: JBIDE-21835 > URL: https://issues.jboss.org/browse/JBIDE-21835 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.CR1 > > > Running OS 3.1.1 from https://github.com/redhat-developer-tooling/openshift-vagrant/tree/master... > Deploy an eap basic app on openshift, > import the kitchensink code in the workspace > wait for the application to deploy and run on openshift > Issue #1 > - when creating a server adapter from the OpenShift Explorer menu "Server Adapter...", on the eap service, the server has no module. The project is treated as a magic project. > - After making a change to the index page and saving, the page is incrementally pushed to the openshift server, and then the ROOT.war restart. It's not supposed to > Issue #2 > - create a new server adapter from the Servers view. Add the kitchensink project as a module to the last page of the wizard > - jbosstools-kitchensink.war is deployed to the remote server. Both ROOT.war and jbosstools-kitchensink.war start, access to the / context root fails. It's been superseded by jbosstools-kitchensink > - local change is not pushed immediately to the server. module restart happens before the change is effective. > (Fred indicates this issue was not replicatable on most recent test) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21906) Choosing Eclipse project in server adapter wizard acts weird

by Jan Richter (JIRA)

Jan Richter created JBIDE-21906: ----------------------------------- Summary: Choosing Eclipse project in server adapter wizard acts weird Key: JBIDE-21906 URL: https://issues.jboss.org/browse/JBIDE-21906 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Jan Richter Open a clean workspace. Have an OS3 application set up and imported. Open a new server adapter wizard for the connection where your application is -> fill in the first page, click next -> in the Eclipse project part, click Browse... Observe - projects imported from the connection are listed -> check Show all projects - RemoteSystemsTempFiles appears -> select RemoteSystemsTempFiles and confirm -> click Brose... again -> observe - 'Show all projects' is checked but RemoteSystemsTempFiles is not visible -> uncheck 'Show all projects' -> observe - OK button is disabled -> double click a listed project to select it with OK button disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21906) Choosing Eclipse project in server adapter wizard acts weird

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21906?page=com.atlassian.jira.plugi... ] Jan Richter updated JBIDE-21906: -------------------------------- Labels: openshift_v3 server_adapter_wizard (was: ) > Choosing Eclipse project in server adapter wizard acts weird > ------------------------------------------------------------ > > Key: JBIDE-21906 > URL: https://issues.jboss.org/browse/JBIDE-21906 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Labels: openshift_v3, server_adapter_wizard > > Open a clean workspace. Have an OS3 application set up and imported. > Open a new server adapter wizard for the connection where your application is > -> fill in the first page, click next > -> in the Eclipse project part, click Browse... > Observe - projects imported from the connection are listed > -> check Show all projects - RemoteSystemsTempFiles appears > -> select RemoteSystemsTempFiles and confirm > -> click Brose... again > -> observe - 'Show all projects' is checked but RemoteSystemsTempFiles is not visible > -> uncheck 'Show all projects' > -> observe - OK button is disabled > -> double click a listed project to select it with OK button disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21905) Server adapter states don't reflect any real state

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21905?page=com.atlassian.jira.plugi... ] Jan Richter updated JBIDE-21905: -------------------------------- Description: Having OS server adapters showing started/stopped states is quite perplexing, because they are completely arbitrary. For example, I can click start on a stopped server with no connection, then just cancel the connection dialog - it throws an error, but it proceeds to started state anyway. It is meaningless to have different states, when their only function is to predend the server is in some state. Plus it introduces steps like the 'stop server before deleting' dialog. was: Having OS server adapters showing started/stopped states is quite perplexing, because they are completely arbitrary. For example, I can click start on a stopped server with no connection, then just cancel the connection dialog - it throws an error, but it proceeds to started state anyway. It is meaningless to have different states, when their only function is to predend the server is in some state. > Server adapter states don't reflect any real state > -------------------------------------------------- > > Key: JBIDE-21905 > URL: https://issues.jboss.org/browse/JBIDE-21905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Labels: openshift_v3, server_adapter > > Having OS server adapters showing started/stopped states is quite perplexing, because they are completely arbitrary. > For example, I can click start on a stopped server with no connection, then just cancel the connection dialog - it throws an error, but it proceeds to started state anyway. > It is meaningless to have different states, when their only function is to predend the server is in some state. Plus it introduces steps like the 'stop server before deleting' dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Thomas Mäder edited comment on JBIDE-21857 at 3/18/16 6:26 AM: --------------------------------------------------------------- I looked at the wildfly VM in a profiler and was able to see that there are at least two class loaders where MemberRegistration is loaded. When looking at the JNI global references, there seems to be one instance retained per attempted class reload or restart modules (not sure which). There really should not be a JNIGlobal referencing this class. I suspect that the failed HCR leaks this reference somehow. Difficult to tell whether this is a JDI/JDT problem or VM. was (Author: tmader): I looked at the wildfly VM in a profiler and was able to see that there are at least two class loaders where MemberRegistration is loaded. > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Thomas Mäder > Priority: Blocker > Fix For: 4.3.1.CR1 > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21905) Server adapter states don't reflect any real state

by Jan Richter (JIRA)

Jan Richter created JBIDE-21905: ----------------------------------- Summary: Server adapter states don't reflect any real state Key: JBIDE-21905 URL: https://issues.jboss.org/browse/JBIDE-21905 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Jan Richter Having OS server adapters showing started/stopped states is quite perplexing, because they are completely arbitrary. For example, I can click start on a stopped server with no connection, then just cancel the connection dialog - it throws an error, but it proceeds to started state anyway. It is meaningless to have different states, when their only function is to predend the server is in some state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21904) Pod deployment path is not reflecting selected service

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21904: ------------------------------------- Summary: Pod deployment path is not reflecting selected service Key: JBIDE-21904 URL: https://issues.jboss.org/browse/JBIDE-21904 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Having more services under an OpenShift 3 connection and trying to create a new OS 3 server adapter does not use correct pod deployment path in following scenario: I am having a project with eap application (created from eap 64 basic s2i) and nodejs application. When I select nodejs application /opt/apt-root/src is used as a Pod Deployment Path. After selecting an EAP service, Pod Deployment Path is changed to /opt/eap/standalone/deployments. When I select nodejs in this point, Pod Deployment Path is not updated again and value is still /opt/eap/standalone/deployments, what is wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2016