April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3866?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3866: ------------------------------ Fix Version/s: 10.x > vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server > ---------------------------------------------------------------------------------------- > > Key: JBDS-3866 > URL: https://issues.jboss.org/browse/JBDS-3866 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit. > (previous installs of CDK and dependencies) > Reporter: Robert Terzi > Fix For: 10.x > > > vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse. > The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist. > The CDK server was shown as 'Started, Sychronized'. > The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either. > Synchronized seems misleading here, since no files had been sync'd yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22261) Server Adapter: "Show in > Server Log" should open the current running pod log

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22261?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22261: -------------------------------- Original Estimate: 3 minutes Remaining Estimate: 3 minutes > Server Adapter: "Show in > Server Log" should open the current running pod log > ------------------------------------------------------------------------------ > > Key: JBIDE-22261 > URL: https://issues.jboss.org/browse/JBIDE-22261 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Fix For: 4.4.x > > Original Estimate: 3 minutes > Remaining Estimate: 3 minutes > > It's currently not practical to open the log for the running server adapter. Users need to open the pod log from the OpenShift Explorer. > Instead, "Show in > Server Log" should open the current running pod log, from the OpenShift 3 Server adapter, in the Servers view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22261) Server Adapter: "Show in > Server Log" should open the current running pod log

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22261?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22261: -------------------------------- Original Estimate: (was: 3 minutes) Remaining Estimate: (was: 3 minutes) Story Points: 3 > Server Adapter: "Show in > Server Log" should open the current running pod log > ------------------------------------------------------------------------------ > > Key: JBIDE-22261 > URL: https://issues.jboss.org/browse/JBIDE-22261 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Fix For: 4.4.x > > > It's currently not practical to open the log for the running server adapter. Users need to open the pod log from the OpenShift Explorer. > Instead, "Show in > Server Log" should open the current running pod log, from the OpenShift 3 Server adapter, in the Servers view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22261) Server Adapter: "Show in > Server Log" should open the current running pod log

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22261?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22261: -------------------------------- Fix Version/s: 4.4.x > Server Adapter: "Show in > Server Log" should open the current running pod log > ------------------------------------------------------------------------------ > > Key: JBIDE-22261 > URL: https://issues.jboss.org/browse/JBIDE-22261 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Fix For: 4.4.x > > > It's currently not practical to open the log for the running server adapter. Users need to open the pod log from the OpenShift Explorer. > Instead, "Show in > Server Log" should open the current running pod log, from the OpenShift 3 Server adapter, in the Servers view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22261) Server Adapter: "Show in > Server Log" should open the current running pod log

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22261: ----------------------------------- Summary: Server Adapter: "Show in > Server Log" should open the current running pod log Key: JBIDE-22261 URL: https://issues.jboss.org/browse/JBIDE-22261 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.1.Final Reporter: Fred Bricon It's currently not practical to open the log for the running server adapter. Users need to open the pod log from the OpenShift Explorer. Instead, "Show in > Server Log" should open the current running pod log, from the OpenShift 3 Server adapter, in the Servers view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-174) JSON empty Array not properly recognized in the outline view [EBZ#491944]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-174: --------------------------------------- Summary: JSON empty Array not properly recognized in the outline view [EBZ#491944] Key: ERT-174 URL: https://issues.jboss.org/browse/ERT-174 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot Created attachment 261054 Looks like the comma is not recognized as a comma after an empty array Apparently is a lexical issue -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3869) platform installer should check/warn if Hyper-V is already enabled.

by Robert Terzi (JIRA)

Robert Terzi created JBDS-3869: ---------------------------------- Summary: platform installer should check/warn if Hyper-V is already enabled. Key: JBDS-3869 URL: https://issues.jboss.org/browse/JBDS-3869 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: platform-installer Affects Versions: 9.1.0.Beta1 Environment: Windows 10 Pro, 64 bit. Reporter: Robert Terzi The platform installer should check and warn if Hyper-V is already enabled on Windows systems. Hyper-V takes over the virtualization assist hardware, which will keep VirtualBox from being able to start the CDK box which depends on VT-x/AMD-V. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-649) Update org.jboss.tools.foundation.security.linux.feature to 1.2.1.Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-649?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-649: ---------------------------------- Hey [~blafond] - could you please update your <td.tpc.version> to 4.3.1.Final in teiid designer (mars)? We're pulling in an older org.jboss.tools.foundation.security.linux Thkx! > Update org.jboss.tools.foundation.security.linux.feature to 1.2.1.Final > ----------------------------------------------------------------------- > > Key: JBTIS-649 > URL: https://issues.jboss.org/browse/JBTIS-649 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Attachments: found1.png, jbdsis_security_bundle.png > > > Currently, JBDS-IS 9.0.0.CR1 (and also the snapshot of CR1a) contains > org.jboss.tools.foundation.security.linux 1.2.1.Beta2-v20160127-2129-B77 > but the JBDS 9.1.0.CR1a contains > org.jboss.tools.foundation.security.linux 1.2.1.Final-v20160401-0436-B108 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install

by Robert Terzi (JIRA)

Robert Terzi created JBDS-3868: ---------------------------------- Summary: Document (and check) required disk space before beginning install Key: JBDS-3868 URL: https://issues.jboss.org/browse/JBDS-3868 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: platform-installer Affects Versions: 9.1.0.Beta1 Environment: Windows 7/64 bit Reporter: Robert Terzi Priority: Minor The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process. Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3867) CDK file name should include version, match file name on RHCP

by Robert Terzi (JIRA)

Robert Terzi created JBDS-3867: ---------------------------------- Summary: CDK file name should include version, match file name on RHCP Key: JBDS-3867 URL: https://issues.jboss.org/browse/JBDS-3867 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: platform-installer Affects Versions: 9.1.0.Beta1 Environment: Windows 7/64 bit Reporter: Robert Terzi Priority: Minor The platform installer uses a file name for the CDK box with no version information making it difficult to tell if you have the latest CDK box or not. The downloaded box file is saved in \cdk\boxes\rhel-vagrant-virtualbox.box. It should use the same file name as the Red Hat Customer Portal to make it easy to identify that it is the same file: rhel-cdk-kubernetes-7.2-23.x86_64.vagrant-virtualbox.box -- 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