July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22679) Run integration-test against source (rather than package)

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22679?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-22679: ------------------------------------------ So I have devstudio.feature and cdi.feature defined {code} <requirement> <type>p2-installable-unit</type> <id>com.jboss.devstudio.core.feature.feature.group</id> <versionRange>0.0.0</versionRange> </requirement> <requirement> <type>p2-installable-unit</type> <id>org.jboss.tools.cdi.feature.feature.group</id> <versionRange>0.0.0</versionRange> </requirement> {code} It runs devstudio (which is OK) but somehow ignores my locally build CDI (log doesn't say anything) and uses the one from devstudio feature. My locally built cdi has higher timestamp than the one in devstudio. > Run integration-test against source (rather than package) > --------------------------------------------------------- > > Key: JBIDE-22679 > URL: https://issues.jboss.org/browse/JBIDE-22679 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Mickael Istria > Assignee: Rastislav Wagner > > Currently, integration-tests run against a prepared package (of Developer Studio). In order to more easily run those tests locally or as part of the development process, it would be nice to also have them running directly against source code of the component. > Tycho provide a mechanism to provision the application under test according to existing definition: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t... , or maybe even by simply making Developer Studio part of the test target-platform and define it as the application/produce under test: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-22603 at 7/1/16 6:46 AM: --------------------------------------------------------------- Well, this is something what should be fixed ASAP. I am not even able to publish project (I have to try do it several times, blocking jobs), nor start debugging (this I can't get working at all because of waiting for a pod). It makes CDK OpenShift unusable for me. But I am not sure why I am able to reproduce this at 100 % success rate. was (Author: mlabuda): Well, this is something what should be fixed ASAP. I am not even able to publish project, nor start debugging because of those WatchManager jobs. It makes CDK OpenShift unusable for me. But I am not sure why I am able to reproduce this at 100 % success rate. > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: explorer, openshift_v3 > Fix For: 4.4.x > > Attachments: watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-22603 at 7/1/16 6:43 AM: --------------------------------------------------------------- Well, this is something what should be fixed ASAP. I am not even able to publish project, nor start debugging because of those WatchManager jobs. It makes CDK OpenShift unusable for me. But I am not sure why I am able to reproduce this at 100 % success rate. was (Author: mlabuda): Well, this is something what should get be fixed ASAP. I am not even able to publish project, nor start debugging because of those WatchManager jobs. It makes CDK OpenShift unusable for me. But I am not sure why I am able to reproduce this at 100 % success rate. > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: explorer, openshift_v3 > Fix For: 4.4.x > > Attachments: watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22603: --------------------------------------- Well, this is something what should get be fixed ASAP. I am not even able to publish project, nor start debugging because of those WatchManager jobs. It makes CDK OpenShift unusable for me. But I am not sure why I am able to reproduce this at 100 % success rate. > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: explorer, openshift_v3 > Fix For: 4.4.x > > Attachments: watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ] David Hladky commented on JBIDE-21745: -------------------------------------- The 500 is fixed. > Unable to download EAP 7 Beta runtime using username without "@redhat.com" > -------------------------------------------------------------------------- > > Key: JBIDE-21745 > URL: https://issues.jboss.org/browse/JBIDE-21745 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Final, 4.3.1.CR1 > Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.x > > Attachments: rh-developer-credentials.png > > > Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page. > Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown: > {noformat} > You Entered All Necessary Information > Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip. > {noformat} > But even after that I'm unable to download that runtime with the same credentials. > Using login with "@redhat.com" I'm able to download the runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22679) Run integration-test against source (rather than package)

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22679?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-22679: ------------------------------------------ Log doesnt say anything. I will try adding com.jboss.devstudio.core.feature.feature.group as dependency > Run integration-test against source (rather than package) > --------------------------------------------------------- > > Key: JBIDE-22679 > URL: https://issues.jboss.org/browse/JBIDE-22679 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Mickael Istria > Assignee: Rastislav Wagner > > Currently, integration-tests run against a prepared package (of Developer Studio). In order to more easily run those tests locally or as part of the development process, it would be nice to also have them running directly against source code of the component. > Tycho provide a mechanism to provision the application under test according to existing definition: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t... , or maybe even by simply making Developer Studio part of the test target-platform and define it as the application/produce under test: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22679) Run integration-test against source (rather than package)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22679?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22679: ---------------------------------------- Does the log tell you something about not starting JBDS? Maybe the product should be added as a requirement? > Run integration-test against source (rather than package) > --------------------------------------------------------- > > Key: JBIDE-22679 > URL: https://issues.jboss.org/browse/JBIDE-22679 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Mickael Istria > Assignee: Rastislav Wagner > > Currently, integration-tests run against a prepared package (of Developer Studio). In order to more easily run those tests locally or as part of the development process, it would be nice to also have them running directly against source code of the component. > Tycho provide a mechanism to provision the application under test according to existing definition: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t... , or maybe even by simply making Developer Studio part of the test target-platform and define it as the application/produce under test: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22679) Run integration-test against source (rather than package)

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22679?page=com.atlassian.jira.plugi... ] Rastislav Wagner edited comment on JBIDE-22679 at 7/1/16 4:13 AM: ------------------------------------------------------------------ That doesn't work. I will only get eclipse with dependencies I specify in pom/manifest. So I think that we have a solution, i will create PR for integration-tests and as soon as it will be merged i will try to create POC job on central ci (JBIDE-22680). PR for integration-tests https://github.com/jbosstools/jbosstools-integration-tests/pull/1533 [~mickael_istria] do you agree ? Can I resolve this issue ? was (Author: rawagner): That doesn't work. I will only get eclipse with dependencies I specify in pom/manifest. So I think that we have a solution, i will create PR for integration-tests and as soon as it will be merged i will try to create POC job on central ci (JBIDE-22680). [~mickael_istria] do you agree ? Can I resolve this issue ? > Run integration-test against source (rather than package) > --------------------------------------------------------- > > Key: JBIDE-22679 > URL: https://issues.jboss.org/browse/JBIDE-22679 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Mickael Istria > Assignee: Rastislav Wagner > > Currently, integration-tests run against a prepared package (of Developer Studio). In order to more easily run those tests locally or as part of the development process, it would be nice to also have them running directly against source code of the component. > Tycho provide a mechanism to provision the application under test according to existing definition: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t... , or maybe even by simply making Developer Studio part of the test target-platform and define it as the application/produce under test: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22679) Run integration-test against source (rather than package)

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22679?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-22679: ------------------------------------------ That doesn't work. I will only get eclipse with dependencies I specify in pom/manifest. So I think that we have a solution, i will create PR for integration-tests and as soon as it will be merged i will try to create POC job on central ci (JBIDE-22680). [~mickael_istria] do you agree ? Can I resolve this issue ? > Run integration-test against source (rather than package) > --------------------------------------------------------- > > Key: JBIDE-22679 > URL: https://issues.jboss.org/browse/JBIDE-22679 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Mickael Istria > Assignee: Rastislav Wagner > > Currently, integration-tests run against a prepared package (of Developer Studio). In order to more easily run those tests locally or as part of the development process, it would be nice to also have them running directly against source code of the component. > Tycho provide a mechanism to provision the application under test according to existing definition: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t... , or maybe even by simply making Developer Studio part of the test target-platform and define it as the application/produce under test: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22639) Server Adapter Editor: Opening an Openshift3 server adapter when connection does not exists anymore causes NPE

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22639?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22639: ------------------------------------------ merged both PRs into master > Server Adapter Editor: Opening an Openshift3 server adapter when connection does not exists anymore causes NPE > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22639 > URL: https://issues.jboss.org/browse/JBIDE-22639 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: server_adapter_editor > Fix For: 4.4.1.AM2 > > Attachments: non-existent-workspace-reference.png, screenshot-1.png > > > ASSERT: create an Openshift3 connection > ASSERT: create a server adapter from that connection > ASSERT: delete the Openshift3 connection > EXEC: open the server adapter > ASSERT: NPE is thrown and dialog is displayed (see [^screenshot-1.png]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 July 2016