April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22043) Server adapter wizard: create unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22043?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22043: ------------------------------------- Priority: Critical (was: Major) > Server adapter wizard: create unit tests > ---------------------------------------- > > Key: JBIDE-22043 > URL: https://issues.jboss.org/browse/JBIDE-22043 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Priority: Critical > Labels: server_adapter_wizard > Fix For: 4.4.0.Alpha1 > > > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22035) Server adapter: Stopping of J2EE module does not work

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22035?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22035: ------------------------------------- Summary: Server adapter: Stopping of J2EE module does not work (was: Stopping of J2EE module does not work) > Server adapter: Stopping of J2EE module does not work > ----------------------------------------------------- > > Key: JBIDE-22035 > URL: https://issues.jboss.org/browse/JBIDE-22035 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Stopping of J2EE Web module lying under an OpenShift 3 Server Adapter does nothing. After discussion with Rob in JBIDE-21989, stop of J2EE module should create an .undeploy marker and rsync it, but that's not happening. Only output from rsync when stopping J2EE module is following > {code}sent 46 bytes received 1,333 bytes 2,758.00 bytes/sec > total size is 8,523,390 speedup is 6,180.85 > sending incremental file list > ROOT.war.isdeploying > sent 1,428 bytes received 149 bytes 3,154.00 bytes/sec > total size is 8,523,390 speedup is 5,404.81{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3858) doTry blocks disappearing in Camel Blueprint.xml

by Michael Thirion (JIRA)

Michael Thirion created JBDS-3858: ------------------------------------- Summary: doTry blocks disappearing in Camel Blueprint.xml Key: JBDS-3858 URL: https://issues.jboss.org/browse/JBDS-3858 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: integration Affects Versions: 9.0.0.GA, 8.1.0.GA Environment: Using JBDS with the integration pack. Developing camel routes with Blueprint XML. Reporter: Michael Thirion During the edition of the Camel's blueprint.xml file, when switching from "design" view to "source" view, the doTry blocks with their content totally disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22005) Log console: Unexpected EOF in pod log

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22005: ------------------------------------- Summary: Log console: Unexpected EOF in pod log (was: Unexpected EOF in pod log) > Log console: Unexpected EOF in pod log > -------------------------------------- > > Key: JBIDE-22005 > URL: https://issues.jboss.org/browse/JBIDE-22005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log. > Last lines from console (output of application pod log) > {code} > ... > [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe... > error: unexpected EOF > {code} > I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21755) Properties: "Eager-er" loading of the project properties

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21755: ------------------------------------- Summary: Properties: "Eager-er" loading of the project properties (was: "Eager-er" loading of the project properties) > Properties: "Eager-er" loading of the project properties > -------------------------------------------------------- > > Key: JBIDE-21755 > URL: https://issues.jboss.org/browse/JBIDE-21755 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Minor > Labels: openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > > Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21755) Properties: "Eager-er" loading of the project properties

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21755: ------------------------------------- Labels: openshift_v3 properties (was: ) > Properties: "Eager-er" loading of the project properties > -------------------------------------------------------- > > Key: JBIDE-21755 > URL: https://issues.jboss.org/browse/JBIDE-21755 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Minor > Labels: openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > > Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21968) Automatically stop server adapters when connection is severed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21968?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21968: ------------------------------------- Component/s: cdk > Automatically stop server adapters when connection is severed > ------------------------------------------------------------- > > Key: JBIDE-21968 > URL: https://issues.jboss.org/browse/JBIDE-21968 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Assignee: Rob Stryker > Labels: server_adapter > Fix For: 4.4.0.Alpha1 > > > It would be nice to automatically stop the server adapter when no longer connected to openshift (i.e. after shutting down CDK) - that way it would reflect the actual state of things. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21121: ------------------------------------- Issue Type: Bug (was: Enhancement) Priority: Major (was: Minor) > Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21121 > URL: https://issues.jboss.org/browse/JBIDE-21121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.0.Alpha1 > > > OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21121: ------------------------------------- Steps to Reproduce: ASSERT: Have a OpenShift 3 connection with project in OpenShift Explorer View. EXEC: Set incorrect path to OpenShift oc binary in preferences (type some invalid string or path non-leading to oc binary) and press Esc or close dialog. EXEC: Create a new OpenShift 3 application (I created eap-basic s2i from server template) ASSERT: Application is running (there is a succeeded pod for build called eap-app-1-build and there is a running pod with name eap-app-1-* where * is some string/hash) EXEC: Select running pod and open its context menu. EXEC: Select Port Forwarding... context menu. RESULT: Dialog Application Port Forwarding is opened. EXPECTED RESULT: Warning/Error dialog about oc should be shown. > Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21121 > URL: https://issues.jboss.org/browse/JBIDE-21121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.0.Alpha1 > > > OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22079) Import wizard: Error when import a project already existing in workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22079: ------------------------------------- Summary: Import wizard: Error when import a project already existing in workspace (was: Error when import a project already existing in workspace) > Import wizard: Error when import a project already existing in workspace > ------------------------------------------------------------------------ > > Key: JBIDE-22079 > URL: https://issues.jboss.org/browse/JBIDE-22079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: import_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: import-error.png > > > When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear). > Error: > {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts. > One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again. > An exception stack trace is not available. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

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