October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23296) NullPointerException in LocalJBoss7ServerRuntime.getBaseDirectory

by Automated Error Reporting Bot (JIRA)

Automated Error Reporting Bot created JBIDE-23296: ----------------------------------------------------- Summary: NullPointerException in LocalJBoss7ServerRuntime.getBaseDirectory Key: JBIDE-23296 URL: https://issues.jboss.org/browse/JBIDE-23296 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Reporter: Automated Error Reporting Bot The following problem was reported via the automated error reporting: Message: HIDDEN {noformat} java.lang.NullPointerException: null at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7ServerRuntime.getBaseDirectory(LocalJBoss7ServerRuntime.java:96) at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7ServerRuntime.getConfigLocation(LocalJBoss7ServerRuntime.java:121) at org.jboss.ide.eclipse.as.core.server.internal.LocalJBossServerRuntime.getConfigLocationFullPath(LocalJBossServerRuntime.java:130) at org.jboss.ide.eclipse.as.core.resolvers.ConfigNameResolver.handleConfigDir(ConfigNameResolver.java:157) at org.jboss.ide.eclipse.as.core.resolvers.ConfigNameResolver.resolveValue(ConfigNameResolver.java:127) at org.jboss.ide.eclipse.as.core.resolvers.ConfigNameResolver.resolveValue(ConfigNameResolver.java:116) at org.eclipse.core.internal.variables.DynamicVariable.getValue(DynamicVariable.java:56) at org.eclipse.core.internal.variables.StringSubstitutionEngine.resolve(StringSubstitutionEngine.java:269) at org.eclipse.core.internal.variables.StringSubstitutionEngine.substitute(StringSubstitutionEngine.java:192) at org.eclipse.core.internal.variables.StringSubstitutionEngine.performStringSubstitution(StringSubstitutionEngine.java:87) at org.jboss.ide.eclipse.as.core.resolvers.RuntimeVariableResolver.resolve(RuntimeVariableResolver.java:74) at org.jboss.tools.foundation.core.expressions.ExpressionResolver.resolveVariable(ExpressionResolver.java:304) at org.jboss.tools.foundation.core.expressions.ExpressionResolver.resolve(ExpressionResolver.java:229) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.getReplacedString(XPathQuery.java:105) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.setEffectiveBaseDir(XPathQuery.java:112) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.<init>(XPathQuery.java:97) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.addQueriesToCategoryFromDefaultFile(XPathModel.java:366) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.loadDefaultPortQueries(XPathModel.java:338) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.handleAddJBossXPaths(XPathModel.java:115) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.access$1(XPathModel.java:114) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel$1.run(XPathModel.java:101) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {noformat} Bundles: | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | | org.eclipse.core.variables | 3.2.800.v20130819-1716 | 3.3.0.v20160419-1720 | | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 | | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 | | org.eclipse.ui.navigator | 3.6.100.v20160518-1929 | 3.6.100.v20160518-1929 | | org.jboss.ide.eclipse.as.core | 3.1.1.Final-v20160409-0826-B118 | 3.2.0.Final-v20160614-2020-B9 | | org.jboss.ide.eclipse.as.ui | 3.2.0.Final-v20160614-2020-B9 | 3.2.0.Final-v20160614-2020-B9 | | org.jboss.tools.foundation.core | 1.2.1.Final-v20160408-2358-B112 | 1.3.0.Final-v20160610-1533-B7 | Operating Systems: | Windows | 10.0.0 | 10.0.0 | The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57cd9a2fe4b0fd7621...] for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-22965: ------------------------------------------ [~mmalina] thank you! [~jeffmaury] i'm not sure about traffic control on Windows. [People say|http://superuser.com/questions/29701/global-proxy-settings-for-windows], that there is no "global" proxy setting. And as it is offered there that we can establish VPN connection or just set proxy settings for applications (in our case in eclipse Preferences). So this is the topic for discussion. About DNS - i think it's more a question to [~lalatendum] about https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM2 > > Attachments: create_proxy-test_env.sh > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-22803: ------------------------------------------ [~jeffmaury], [~adietish] i talked to OS devs and they pointed me to https://github.com/openshift/origin/blob/master/pkg/cmd/cli/cmd/version.g... on how to retrieve the OS version. I tested it on https://console.engint.openshift.com, e.g. https://console.engint.openshift.com/version/openshift, but had an error: User "openshift-dev" cannot "get" on "/version/openshift" I talked to [~jcantrill] and [~deads2k]: {quote}deads2k: dbocharo: it's an upgrade step: https://docs.openshift.org/latest/architecture/additional_concepts/author... deads2k: dbocharo: the roles are based on the client being used. If you start a fresh server with a fresh etcd that has the /version/openshift endpoint, it's all set up already deads2k: dbocharo: I think that server is too old. Pretty sure we added it in 3.3{quote} So we wanted to use the OS version to detect whether watching projects feature enabled or not. And now it turned out that the feature of getting OS version is version-dependent itself =( > When OS projects are created and deleted, seems Openshift explorer restores non existing values > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23294) Console is badly rendering some characters when starting Container Development Environment

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23294?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23294: ---------------------------------------- This is devstudio 10.1.0.GA / JBoss Tools 4.4.1.Final > Console is badly rendering some characters when starting Container Development Environment > ------------------------------------------------------------------------------------------ > > Key: JBIDE-23294 > URL: https://issues.jboss.org/browse/JBIDE-23294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Priority: Minor > Attachments: screenshot-1.png > > > - there is a special character before the [KProgress > - what means K for KProgress? > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23294) Console is badly rendering some characters when starting Container Development Environment

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23294?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-23294: ----------------------------------------- I'm using the version installed with the "Development suite installer" in version 1.1.0 > Console is badly rendering some characters when starting Container Development Environment > ------------------------------------------------------------------------------------------ > > Key: JBIDE-23294 > URL: https://issues.jboss.org/browse/JBIDE-23294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Priority: Minor > Attachments: screenshot-1.png > > > - there is a special character before the [KProgress > - what means K for KProgress? > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-921) Add an IS presence in developers.redhat.com

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-921: -------------------------------- Summary: Add an IS presence in developers.redhat.com Key: JBTIS-921 URL: https://issues.jboss.org/browse/JBTIS-921 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution Affects Versions: 9.0.2.GA Reporter: Paul Leacu Assignee: Paul Leacu Modify the devstudio product in developers.redhat.com to point to an Integration Stack non-product. From there reference Fuse Tooling, DataVirt and BRMS tooling. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23291) If start of container fails on timeout, the status in server view is "Started, Synchronized"

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23291?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-23291: ----------------------------------------- What do you call the "server" in this case? The VirtualBox? The Docker daemon inside it? The Openshift Instance inside it? The vm has started but vagrant never finished in my case. The Openshift instance cannot be reached at this moment > If start of container fails on timeout, the status in server view is "Started, Synchronized" > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23291 > URL: https://issues.jboss.org/browse/JBIDE-23291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-860) Fuse runtime detection never makes a server

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-860?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-860. ------------------------------ Fix Version/s: 10.0.0.Alpha1 Resolution: Done Server created in the Karaf runtime detector. Fixed in Fuse tooling. > Fuse runtime detection never makes a server > ------------------------------------------- > > Key: JBTIS-860 > URL: https://issues.jboss.org/browse/JBTIS-860 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 10.0.0.Alpha1 > > > The runtime detectors never create the server, only the runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4089) Skip unit/ui tests not related to current platform/arch

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4089: ----------------------------------- Summary: Skip unit/ui tests not related to current platform/arch Key: JBDS-4089 URL: https://issues.jboss.org/browse/JBDS-4089 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: platform-installer Affects Versions: 10.1.0.AM2 Reporter: Denis Golovin Fix For: 10.2.0.AM2 Current UI tests are specific for windows. When installer supports Mac OS X there will be failures when UI tests are running on Mac. For example verification for Drive in selected path is valid only on Windows. this.skip() call does not work for protractor tests, because it still considered as a failure. Second option would be do not run tests that are not valid for current platform at all. That could be done ether by direct check in tests like {code} if(process.platform === 'win32') { it('test desctription', function(){ // test instructions }); } {code} or we can move platform specific tests in files with platform specific suffix and include them using process.platform and process.arch values at gulp execution time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4047) Uninstaller does not clean up Path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4047?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4047: -------------------------------- Fix Version/s: 10.2.0.AM2 (was: 10.2.0.AM1) > Uninstaller does not clean up Path > ---------------------------------- > > Key: JBDS-4047 > URL: https://issues.jboss.org/browse/JBDS-4047 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.2.0.AM2 > > > After running the uninstall script all the PATH entries pointing to the devsuite install folder remain untouched. My guess is the actual folder these entries are compared to is not the root install folder, but the uninstall one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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