April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22068) [openshift server] Wire up module-restart / republish for hot-code replace

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22068: ------------------------------------- Summary: [openshift server] Wire up module-restart / republish for hot-code replace Key: JBIDE-22068 URL: https://issues.jboss.org/browse/JBIDE-22068 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift, server Affects Versions: 4.3.1.CR1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.3.1.CR1 I've made this a subtask because it is related to but not a core piece of enabling module-restart. This jira is for allowing more options on hotcode-replace failure. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22069) Allow stop / start / restart to work on module selections in server view

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22069: ------------------------------------- Summary: Allow stop / start / restart to work on module selections in server view Key: JBIDE-22069 URL: https://issues.jboss.org/browse/JBIDE-22069 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift, server Affects Versions: 4.3.1.CR1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.3.1.CR1 Allow simple module-state verification based on rsync and checking deployment markers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21711) Server Adapter: Need a way to restart modules

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21711?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21711: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Server Adapter: Need a way to restart modules > --------------------------------------------- > > Key: JBIDE-21711 > URL: https://issues.jboss.org/browse/JBIDE-21711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.1.CR1 > > > When doing hot code reload in an OpenShift deployed EAP server, changing a method signature will make the debugger complain with > !http://content.screencast.com/users/fbricon/folders/Jing/media/623c96cc-ae62-441b-b498-a39d9cf9b563/00000322.png|width=650! > Triggering a full publish on the module is not sufficient. > We need to at least have a way to trigger a module restart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21993) Show in Browser: route chooser should allow to user to choose route permanently

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21993?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21993. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B260. > Show in Browser: route chooser should allow to user to choose route permanently > ------------------------------------------------------------------------------- > > Key: JBIDE-21993 > URL: https://issues.jboss.org/browse/JBIDE-21993 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > Attachments: route-chooser.png > > > steps to reproduce: > # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace > # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project) > # EXEC: launch New OpenShift 3 Server Adapter wizard > # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected) > # EXEC: create the adapter by picking service, local project etc. > # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser > # ASSERT: Route chooser shows up (since there are several routes available) > Result: > There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project) > !route-chooser.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21351) Error during "Update Maven projects configuration"

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21351?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-21351. ------------------------------------ Resolution: Done Merged PR. > Error during "Update Maven projects configuration" > -------------------------------------------------- > > Key: JBIDE-21351 > URL: https://issues.jboss.org/browse/JBIDE-21351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.1.Beta1 > Reporter: Radim Hopp > Assignee: Mickael Istria > Fix For: 4.3.1.CR1 > > > Sometimes I get > {noformat} > An internal error occurred during: "Update Maven projects configuration". > Cannot add projects when processing is started{noformat} > when I'm importing maven project using easymport. > Full stacktrace: > {noformat} > java.lang.IllegalStateException: Cannot add projects when processing is started > at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$CumulativeMappingDiscoveryJob.addProjects(MavenProjectConfigurator.java:97) > at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$UpdateMavenConfigurationJob.run(MavenProjectConfigurator.java:161) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21646) Ensure Quickstarts for EAP7 will be supported in JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21646?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21646: ------------------------------------- Currently, we rely on the search results defined in http://download.jboss.org/jbosstools/configuration/ide-config.properties, that is: quickstarts.search.query=http://dcp.jboss.org/v1/rest/search?content_prov... If you provide some fake search results by starting eclipse with -Dquickstarts.search.query=mock.results.url, you should be able to test it. You can try -Dquickstarts.search.query=https://raw.githubusercontent.com/jbosstools/jbosstools-central/fd22e14f4303720254d6adbbc1d112cd113c9d97/examples/tests/org.jboss.tools.project.examples.test/resources/search.json and search for cdi-veto. See https://github.com/jbosstools/jbosstools-central/commit/fd22e14f430372025... > Ensure Quickstarts for EAP7 will be supported in JBoss Central > -------------------------------------------------------------- > > Key: JBIDE-21646 > URL: https://issues.jboss.org/browse/JBIDE-21646 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > Ensure Quickstarts for EAP7 will be supported in JBoss Central. Need to be smart about https://github.com/jbosstools/jbosstools-central/blob/master/examples/plu... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22003) Order of project in New OS3 Server Adapter wizard could be better

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22003?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22003. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B260. > Order of project in New OS3 Server Adapter wizard could be better > ----------------------------------------------------------------- > > Key: JBIDE-22003 > URL: https://issues.jboss.org/browse/JBIDE-22003 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.CR1 > > > With latest changes to New OS3 Server Adapter wizard the current order of projects, listed on wizard page where service selection is done, is a bit strange. At first there are alphanumeric ordered projects with no services and therefore they are not useful for creation of a new OS3 Server Adapter and then there are projects with any service ordered in alphanumberic order. It results in following. > Assume project aproject with no services, bproject with a service, c project with no services, d project with a service. Order on the wizard page is following: > a > c > b > d > I think we are safe not to list projects with no services there or otherwise we should keep alphanumeric order regardless existence of a service under a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21699) Enable debug mode on deployment config

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21699?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21699: --------------------------------------- Follow-up JIRA has been created for getting back from debug state to normal state. > Enable debug mode on deployment config > -------------------------------------- > > Key: JBIDE-21699 > URL: https://issues.jboss.org/browse/JBIDE-21699 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.CR1 > > Attachments: Screenshot 2016-03-25 12.07.45.png > > > When clicking on the Debug button of the server adapter, the Debug variables should be set, if necessary. > The remote debug port could be read from server adapter preferences, default to 8787 > {code} > { > "name" : "debug", > "containerPort" : 8787, > "protocol" : "TCP" > } > {code} > * and to spec.containers.env: > {code} > { > "name" : "DEBUG", > "value" : "true" > }, > { > "name" : "DEBUG_PORT", > "value" : "8787" > } > {code} > If the remote debug port was already set (possibly to another value), then it should be returned -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22066) Stopping debugging of OpenShift application should get application back to normal state.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22066: ---------------------------------- Description: When user stop or delete Server Adapter where debugging has been enabled, application should be able to get back to normal state - remove environment variable for debugging and remove ports for debugging from deployment config. (was: This is follow up on JBIDE-21699. When user stop or delete Server Adapter where debugging has been enabled, application should be able to get back to normal state - remove environment variable for debugging and remove ports for debugging from deployment config.) > Stopping debugging of OpenShift application should get application back to normal state. > ---------------------------------------------------------------------------------------- > > Key: JBIDE-22066 > URL: https://issues.jboss.org/browse/JBIDE-22066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > > When user stop or delete Server Adapter where debugging has been enabled, application should be able to get back to normal state - remove environment variable for debugging and remove ports for debugging from deployment config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22066) Stopping debugging of OpenShift application should get application back to normal state.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22066: ---------------------------------- Labels: openshift_v3 (was: ) > Stopping debugging of OpenShift application should get application back to normal state. > ---------------------------------------------------------------------------------------- > > Key: JBIDE-22066 > URL: https://issues.jboss.org/browse/JBIDE-22066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > > When user stop or delete Server Adapter where debugging has been enabled, application should be able to get back to normal state - remove environment variable for debugging and remove ports for debugging from deployment config. -- 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 April 2016