August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-834) JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-834?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-834: ---------------------------------- Hey [~apodhrad] - this came by request of [~bfitzpat]. > JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY > ---------------------------------------------------------------------------- > > Key: JBTIS-834 > URL: https://issues.jboss.org/browse/JBTIS-834 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.2.Final-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > *Reason:* IS dependency for Fuse/SY > *Project page/sources:* > *Version:* 4.3.3 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.3.0/ > *Include Sources:* Yes > *Affected JBoss Tools components:* Integration Stack > *Include in JBDS:* Yes JBDSIS > *Type of dependency:* testing|central-only|distribution > *List of bundles added/removed:* > {code} > > org.eclipse.swtbot.eclipse.spy [2.3.0.201506081302] > > org.eclipse.swtbot.generator.jdt [2.3.0.201506081302] > > org.eclipse.swtbot.ide.feature.group [2.3.0.201506081302] > > org.eclipse.swtbot.ide.feature.jar [2.3.0.201506081302] > > org.eclipse.swtbot.generator.rules.workbench [2.3.0.201506081302] > > org.eclipse.swtbot.generator [2.3.0.201506081302] > > org.eclipse.swtbot.generator.feature.feature.jar [2.3.0.201506081302] > > org.eclipse.swtbot.generator.ui [2.3.0.201506081302] > > org.eclipse.swtbot.eclipse.ui [2.3.0.201506081302] > > org.eclipse.swtbot.generator.feature.feature.group [2.3.0.201506081302] > === Summary === > file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 10 unique IUs > {code} > The JBT core TP dependencies are: > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4008) Installer may use different credentials than those used to log in

by Jan Richter (JIRA)

Jan Richter created JBDS-4008: --------------------------------- Summary: Installer may use different credentials than those used to log in Key: JBDS-4008 URL: https://issues.jboss.org/browse/JBDS-4008 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.1.0.AM3 Reporter: Jan Richter Assignee: Denis Golovin The basic idea is that the user may still edit the login form after login button has been clicked. Authentication will use the values from the moment the button was clicked. But if the user for some reason changes the fields during authentication, the installer will use the most recent values. Hence one can successfully log in and then get a failure when i.e. an authenticated download is needed or later when launching CDK during box registration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22773: ------------------------------------------ +1, warning seem fair. > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: server > Fix For: 4.4.1.Final > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22867) JBT could not get projects created by openshift cli tool

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22867?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-22867. -------------------------------------- Assignee: Andre Dietisheim Resolution: Cannot Reproduce Bug > JBT could not get projects created by openshift cli tool > -------------------------------------------------------- > > Key: JBIDE-22867 > URL: https://issues.jboss.org/browse/JBIDE-22867 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.x > Environment: JBoss OpenShift 3 Tools 3.3.0.v20160721-2201 > openshift v3.3.0.12 > kubernetes v1.3.0+57fb9ac > etcd 2.3.0+git > Reporter: Peng Li > Assignee: Andre Dietisheim > Fix For: 4.4.1.Final > > > User could not get projects created by oc command -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22867) JBT could not get projects created by openshift cli tool

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22867?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22867: ------------------------------------------ I cannot reproduce this in several tries. The new instance is newer than the one that made you experience this: 3.3.0.13 vs 3.3.0.21. I'll resolve this issue as CANT_REPRODUCE and ask you to please reopen it if you face it again. > JBT could not get projects created by openshift cli tool > -------------------------------------------------------- > > Key: JBIDE-22867 > URL: https://issues.jboss.org/browse/JBIDE-22867 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.x > Environment: JBoss OpenShift 3 Tools 3.3.0.v20160721-2201 > openshift v3.3.0.12 > kubernetes v1.3.0+57fb9ac > etcd 2.3.0+git > Reporter: Peng Li > Fix For: 4.4.1.Final > > > User could not get projects created by oc command -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23010) landrush plugin prevents CDK server adapter from starting

by Brian Exelbierd (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23010?page=com.atlassian.jira.plugi... ] Brian Exelbierd commented on JBIDE-23010: ----------------------------------------- Tracked upstream here: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/513 > landrush plugin prevents CDK server adapter from starting > --------------------------------------------------------- > > Key: JBIDE-23010 > URL: https://issues.jboss.org/browse/JBIDE-23010 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > > Today I downloaded cdk 2.2.rc1 [1], installed all the vagrant plugins from scratch. And then I first started this from CLI - it wanted password for sudo to set up landrush. (That's another concern I have: How will this work in devstudio? Probably it won't.) > Then I stopped it, set up in devstudio and start there. Everything looks fine, but the server adapter is stuck at "Starting...". > This is the console output: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: [landrush] virtualbox requires an additional private network; adding it > ==> default: [landrush] starting dns server > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Remote connection disconnect. Retrying... > default: Warning: Remote connection disconnect. Retrying... > default: Warning: Remote connection disconnect. Retrying... > ==> default: Machine booted and ready! > ==> default: Registering box with vagrant-registration... > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Setting hostname... > ==> default: Configuring and enabling network interfaces... > [landrush] Using eth1 (172.28.128.3) > ==> default: [landrush] adding machine entry: cdk.vm => 172.28.128.3 > ==> default: [landrush] adding static DNS entry: cdk => cdk.vm > [landrush] Using eth1 (172.28.128.3) > [landrush] Host DNS resolver config looks good. > ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Mounting SSHFS shared folder... > ==> default: Mounting folder via SSHFS: /Users/rasp => /Users/rasp > ==> default: Checking Mount.. > ==> default: Checking Mount.. > ==> default: Folder Successfully Mounted! > ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always will still run. > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: > ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory. > ==> default: To modify the number of cores and/or available memory set the environment variables > ==> default: VM_CPU respectively VM_MEMORY. > ==> default: > ==> default: You can now access the OpenShift console on: https://openshift.cdk:8443/console > ==> default: > ==> default: To use OpenShift CLI, run: > ==> default: $ vagrant ssh > ==> default: $ oc login > ==> default: > ==> default: Configured users are (<username>/<password>): > ==> default: openshift-dev/devel > ==> default: admin/admin > ==> default: > ==> default: If you have the oc client library on your host, you can also login from your host. > {code} > These are my plugins: > {code} > $ vagrant plugin list > landrush (1.1.1) > - Version Constraint: 1.1.1 > vagrant-registration (1.2.3) > - Version Constraint: 1.2.3 > vagrant-service-manager (1.3.0) > - Version Constraint: 1.3.0 > vagrant-share (1.1.5, system) > vagrant-sshfs (1.2.0) > - Version Constraint: 1.2.0 > {code} > [1] http://cdk-builds.usersys.redhat.com/builds/weekly/12-Aug-2016.rc1/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22773: ------------------------------------ I would like to continue my investigations so that we can add a warning or try to manage those permissions issues so keep it open > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: server > Fix For: 4.4.1.Final > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22773 at 8/18/16 6:02 AM: ------------------------------------------------------------------- [~jeffmaury] Sounds like this is an issue that's inherent to rsync and cant be fix. If you confirm this then we'd close this as WONT_FIX? was (Author: adietish): Sounds like this is an issue that's inherent to rsync and cant be fix. If you confirm this then we'd close this as WONT_FIX? > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: server > Fix For: 4.4.1.Final > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22773: ------------------------------------------ Sounds like this is an issue that's inherent to rsync and cant be fix. If you confirm this then we'd close this as WONT_FIX? > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: server > Fix For: 4.4.1.Final > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23010) landrush plugin prevents CDK server adapter from starting

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23010?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23010: --------------------------------------- I would like to add some clarification: This issue (landrush preventing cdk from starting properly in Eclipse) affects Mac and Linux, but not Windows (I just checked). Brian provided me with a patched landrush gem and that fixed it for me on Mac and for him on Linux. > landrush plugin prevents CDK server adapter from starting > --------------------------------------------------------- > > Key: JBIDE-23010 > URL: https://issues.jboss.org/browse/JBIDE-23010 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > > Today I downloaded cdk 2.2.rc1 [1], installed all the vagrant plugins from scratch. And then I first started this from CLI - it wanted password for sudo to set up landrush. (That's another concern I have: How will this work in devstudio? Probably it won't.) > Then I stopped it, set up in devstudio and start there. Everything looks fine, but the server adapter is stuck at "Starting...". > This is the console output: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: [landrush] virtualbox requires an additional private network; adding it > ==> default: [landrush] starting dns server > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Remote connection disconnect. Retrying... > default: Warning: Remote connection disconnect. Retrying... > default: Warning: Remote connection disconnect. Retrying... > ==> default: Machine booted and ready! > ==> default: Registering box with vagrant-registration... > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Setting hostname... > ==> default: Configuring and enabling network interfaces... > [landrush] Using eth1 (172.28.128.3) > ==> default: [landrush] adding machine entry: cdk.vm => 172.28.128.3 > ==> default: [landrush] adding static DNS entry: cdk => cdk.vm > [landrush] Using eth1 (172.28.128.3) > [landrush] Host DNS resolver config looks good. > ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Mounting SSHFS shared folder... > ==> default: Mounting folder via SSHFS: /Users/rasp => /Users/rasp > ==> default: Checking Mount.. > ==> default: Checking Mount.. > ==> default: Folder Successfully Mounted! > ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always will still run. > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: > ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory. > ==> default: To modify the number of cores and/or available memory set the environment variables > ==> default: VM_CPU respectively VM_MEMORY. > ==> default: > ==> default: You can now access the OpenShift console on: https://openshift.cdk:8443/console > ==> default: > ==> default: To use OpenShift CLI, run: > ==> default: $ vagrant ssh > ==> default: $ oc login > ==> default: > ==> default: Configured users are (<username>/<password>): > ==> default: openshift-dev/devel > ==> default: admin/admin > ==> default: > ==> default: If you have the oc client library on your host, you can also login from your host. > {code} > These are my plugins: > {code} > $ vagrant plugin list > landrush (1.1.1) > - Version Constraint: 1.1.1 > vagrant-registration (1.2.3) > - Version Constraint: 1.2.3 > vagrant-service-manager (1.3.0) > - Version Constraint: 1.3.0 > vagrant-share (1.1.5, system) > vagrant-sshfs (1.2.0) > - Version Constraint: 1.2.0 > {code} > [1] http://cdk-builds.usersys.redhat.com/builds/weekly/12-Aug-2016.rc1/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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