October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23265) Can't start CDK server if user or password env var is empty

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23265?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23265: ------------------------------------- https://github.com/jbosstools/jbosstools-openshift/pull/1352 > Can't start CDK server if user or password env var is empty > ----------------------------------------------------------- > > Key: JBIDE-23265 > URL: https://issues.jboss.org/browse/JBIDE-23265 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Labels: cdk, server > Fix For: 4.4.2.AM2 > > > If the user or password env var name is empty, then server refuses to start. The error is the following: > !ENTRY org.jboss.tools.openshift.cdk.server.core 4 0 2016-09-26 11:29:46.973 > !MESSAGE Exec_tty error:Cannot run program "C:\Apps\HashiCorp\Vagrant\bin\vagrant.exe": Unknown reason > !STACK 0 > java.io.IOException: Exec_tty error:Cannot run program "C:\Apps\HashiCorp\Vagrant\bin\vagrant.exe": Unknown reason > at org.eclipse.cdt.utils.spawner.Spawner.exec_pty(Spawner.java:387) > at org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:99) > at org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:98) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(VagrantLaunchUtility.java:198) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(VagrantLaunchUtility.java:185) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(VagrantLaunchUtility.java:178) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:201) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22225: ------------------------------------ When this is merged and built from master, please submit a PR against these two files to get the new feature added to jbosstools and devstudio update sites. https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/categ... If you've added a new test feature too, please be sure to add it here: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... And if you want this feature installed OOTB in devstudio installer, please add it here: https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... If it shouldn't be included in the rpm, then add it here instead: https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... See also: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Jeff MAURY > Labels: debugging, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23382) Server editor should allow 'edit...' option for selected username

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23382?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23382: -------------------------------- Summary: Server editor should allow 'edit...' option for selected username (was: Cannot start CDK adapter after deletion of secure storage) > Server editor should allow 'edit...' option for selected username > ----------------------------------------------------------------- > > Key: JBIDE-23382 > URL: https://issues.jboss.org/browse/JBIDE-23382 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > > If I have a CDK server adapter in Servers view and I clear secure storage, after next start of DevStudio I cannot start the CDK server adapter, because password is removed and there is no choice to edit an existing credentials (username, password pair) or removing an existing one. I get an error dialog with message: > {code} > The server Container Development Environment has no password associated with it. Please open the server editor and configure the credentials. > {code} > It would be nice, if I would be allowed to edit existing credentials or at least remove it/replace by another one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23382) Server editor should allow 'edit...' option for selected username

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23382?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23382: ------------------------------------- https://github.com/jbosstools/jbosstools-base/pull/540 > Server editor should allow 'edit...' option for selected username > ----------------------------------------------------------------- > > Key: JBIDE-23382 > URL: https://issues.jboss.org/browse/JBIDE-23382 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > > If I have a CDK server adapter in Servers view and I clear secure storage, after next start of DevStudio I cannot start the CDK server adapter, because password is removed and there is no choice to edit an existing credentials (username, password pair) or removing an existing one. I get an error dialog with message: > {code} > The server Container Development Environment has no password associated with it. Please open the server editor and configure the credentials. > {code} > It would be nice, if I would be allowed to edit existing credentials or at least remove it/replace by another one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4126) Include latest OpenJDK 8 build 111 to installer

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4126: ----------------------------------- Summary: Include latest OpenJDK 8 build 111 to installer Key: JBDS-4126 URL: https://issues.jboss.org/browse/JBDS-4126 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Enhancement Components: platform-installer Affects Versions: 10.2.0.AM3 Reporter: Denis Golovin Assignee: Denis Golovin Latest OpenJDK build is available from developers.redhat.com * https://developers.redhat.com/download-manager/file/java-1.8.0-openjdk-1.... * sha256: fc4c77412446d6bbf6bf91d76d4bb5cf5d1e94dc1e932f524796e3f8a9789ccc -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23093) use consistent variables across all jenkins jobs for streams, TP versions, etc.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23093?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23093: ------------------------------------ refactored vars in devstudio_master, 10.0.neon, install tests, and releng jobs too. Also updated vars in parent pom: https://github.com/jbosstools/jbosstools-build/commit/dfca11d0eb9bd3f2744... > use consistent variables across all jenkins jobs for streams, TP versions, etc. > ------------------------------------------------------------------------------- > > Key: JBIDE-23093 > URL: https://issues.jboss.org/browse/JBIDE-23093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > We have a number of inconsistencies between jobs / pom.xml: > * JBTCENTRALTARGET_VERSION -> TARGET_PLATFORM_CENTRAL_MAX > * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN > * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX > * jbosstools_site_stream -> stream_jbt > * JBT_buildversion -> version_jbt, versionWithRespin_jbt > * JBDS_buildversion -> version_ds, versionWithResin_ds > * JBDSVersion -> devstudioReleaseVersion > Should standardize these. > Can also (where applicable) script the relationship between version_* and versionWithRespin_*: > {code} > version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') > version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23365) bump version of egit and egit.mylyn in JBT TP to 4.4.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23365?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23365. ------------------------------ Assignee: Nick Boldt Resolution: Rejected Not required. Turns out the problem was we were using the Neon.0 TP to do installs instead of the Neon.1 TP. Reason this happened was that we were using an unclear variable name in the composite install jobs. So, as part of refactoring for JBIDE-23093 this problem should not reappear when we're moving to Neon.2, since the job now clearly asks for a TARGET_PLATFORM_VERSION_MAX, not just TARGET_PLATFORM_VERSION. Hooray for clear variable names! > bump version of egit and egit.mylyn in JBT TP to 4.4.1 > ------------------------------------------------------ > > Key: JBIDE-23365 > URL: https://issues.jboss.org/browse/JBIDE-23365 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Error when installing composite site: > {code} > -- > [p2.dir] !MESSAGE Cannot complete the install because one or more required items could not be found. > [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2016-10-16 04:58:14.113 > [p2.dir] !MESSAGE Software being installed: Eclipse Git Team Provider - Task focused interface 4.4.1.201607150455-r (org.eclipse.egit.mylyn.feature.group 4.4.1.201607150455-r) > [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2016-10-16 04:58:14.113 > [p2.dir] !MESSAGE Missing requirement: Eclipse Git Team Provider - Task focused interface 4.4.1.201607150455-r (org.eclipse.egit.mylyn.feature.group 4.4.1.201607150455-r) requires 'org.eclipse.egit.feature.group 4.4.1' but it could not be found > [p2.dir] Eclipse: > [p2.dir] GTK+ Version Check > --{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23380: ------------------------------- Story Points: 5 Sprint: devex #122 October 2016 > MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23380 > URL: https://issues.jboss.org/browse/JBIDE-23380 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > At a minimum, the mojo should: > foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all. > However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm. > So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23093) use consistent variables across all jenkins jobs for streams, TP versions, etc.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23093?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23093: ------------------------------- Description: We have a number of inconsistencies between jobs / pom.xml: * JBTCENTRALTARGET_VERSION -> TARGET_PLATFORM_CENTRAL_MAX * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX * jbosstools_site_stream -> stream_jbt * JBT_buildversion -> version_jbt, versionWithRespin_jbt * JBDS_buildversion -> version_ds, versionWithResin_ds * JBDSVersion -> devstudioReleaseVersion Should standardize these. Can also (where applicable) script the relationship between version_* and versionWithRespin_*: {code} version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') {code} was: We have a number of inconsistencies between jobs / pom.xml: * JBTCENTRALTARGET_VERSION -> TARGET_PLATFORM_CENTRAL_MAX * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX * jbosstools_site_stream -> stream_jbt * JBT_buildversion -> version_jbt, versionWithRespin_jbt * JBDS_buildversion -> version_ds, versionWithResin_ds * JBDSVersion -> devstudioReleaseVersion Should standardize these. Can script relationship between version_* and versionWithRespin_*: {code} version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') {code} > use consistent variables across all jenkins jobs for streams, TP versions, etc. > ------------------------------------------------------------------------------- > > Key: JBIDE-23093 > URL: https://issues.jboss.org/browse/JBIDE-23093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > We have a number of inconsistencies between jobs / pom.xml: > * JBTCENTRALTARGET_VERSION -> TARGET_PLATFORM_CENTRAL_MAX > * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN > * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX > * jbosstools_site_stream -> stream_jbt > * JBT_buildversion -> version_jbt, versionWithRespin_jbt > * JBDS_buildversion -> version_ds, versionWithResin_ds > * JBDSVersion -> devstudioReleaseVersion > Should standardize these. > Can also (where applicable) script the relationship between version_* and versionWithRespin_*: > {code} > version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') > version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/$^.*$$.$$/\1/') > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23263) CDK docker registry is filled for an existing OpenShift 3 connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23263?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23263: -------------------------------- Fix Version/s: 4.2.3.Final > CDK docker registry is filled for an existing OpenShift 3 connection > -------------------------------------------------------------------- > > Key: JBIDE-23263 > URL: https://issues.jboss.org/browse/JBIDE-23263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.2.3.Final > > > If I already have an existing OpenShift 3 connection, which would have been otherwise created by starting CDK server adapter, an the connection does not have filled CDK docker registry URL, then the field for registry is still empty even after successful start of CDK server adapter. I would like to have the registry URL filled for an existing connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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