October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18912) Custom deploy dir with remote server using filesystem operations does not work

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18912: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > Custom deploy dir with remote server using filesystem operations does not work > ------------------------------------------------------------------------------ > > Key: JBIDE-18912 > URL: https://issues.jboss.org/browse/JBIDE-18912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: help_wanted > Fix For: 4.4.2.AM3 > > > This is a follow up of JBIDE-17180 and JBIDE-13445 which added the option to add a custom deployment directory if your remote server is using filesystem operations (for management api it's not relevant since the deployment happens directly, no directory is used). > Unfortunately it does not work. It seems I haven't really tried it when reviewing those other JIRAs because there were other obstacles. > I tried this several times and still could not get it to work. > Perhaps it might be worth to try and get this in the final 4.2.1.Final build? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4117) integration tests job should fetch a copy of devstudio and install it headlessly, then pass that install folder to the maven test run process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4117?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4117: ----------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > integration tests job should fetch a copy of devstudio and install it headlessly, then pass that install folder to the maven test run process > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4117 > URL: https://issues.jboss.org/browse/JBDS-4117 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, install-tests, integration-tests > Affects Versions: 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > integration tests job should fetch a copy of devstudio and install it headlessly, then pass that install folder to the maven test run process -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21065: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > Server host name address should not be defaulted during server adapter creation > ------------------------------------------------------------------------------- > > Key: JBIDE-21065 > URL: https://issues.jboss.org/browse/JBIDE-21065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}. > This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address. > Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23143) Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2/RC3 (remediation required)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23143?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23143: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2/RC3 (remediation required) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23143 > URL: https://issues.jboss.org/browse/JBIDE-23143 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform, updatesite, upstream, webservices > Affects Versions: 4.4.1.Final > Reporter: Martin Malina > Assignee: Mickael Istria > Fix For: 4.4.2.AM3 > > Attachments: jbt4.4.1_on_neon.1.RC3.png, jbt4.4.1_on_neon.1.RC3_disabled_sites.png, jbt4.4.1_on_neon.1.RC3_remediation_needed.png, jbt4.4.1_on_neon.1.RC3_remediation_opt2.png, neon-1-byoe.png, neon-1-remediation.png, update-sites-enabled.png > > > When I try to install JBoss Tools 4.4.1.Final [1] Abridged category into eclipse-java-neon-1-RC2-macosx-cocoa-x86_64.tar.gz , I am shown a remediation screen. > !neon-1-remediation.png! > If I choose Update my installation, it offers to install what I want, but uninstall Eclipse XML Editors and Tools. > This is the original error message (third option): > {code} > Your original request has been modified. > "Code Recommenders Snipmatch" will be ignored because a newer version is already installed. > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648) > Software currently installed: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824) > Only one of the following can be installed at once: > Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201605120129) > Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.jar 3.9.0.v201608061824) > Cannot satisfy dependency: > From: Eclipse Web Developer Tools 3.8.0.v201606030549 (org.eclipse.wst.web_ui.feature.feature.group 3.8.0.v201606030549) > To: org.eclipse.wst.xml_ui.feature.feature.group [3.8.0.v201605120129] > Cannot satisfy dependency: > From: Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201605120129) > To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201605120129] > Cannot satisfy dependency: > From: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824) > To: org.eclipse.wst.xml_ui.feature.feature.jar [3.9.0.v201608061824] > Cannot satisfy dependency: > From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648) > To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0) > {code} > [1] http://download.jboss.org/jbosstools/neon/staging/updates/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23135) Verify every EAP 7.1 devel/candidate works with eap7x Server adapter

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23135?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23135: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > Verify every EAP 7.1 devel/candidate works with eap7x Server adapter > -------------------------------------------------------------------- > > Key: JBIDE-23135 > URL: https://issues.jboss.org/browse/JBIDE-23135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23017) use sshfs to speed up publishing process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23017?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23017: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > use sshfs to speed up publishing process > ----------------------------------------- > > Key: JBIDE-23017 > URL: https://issues.jboss.org/browse/JBIDE-23017 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > Currently, publishing from /snapshots to /staging and from /staging to /development requires that we fetch several GBs of data from filemgmt.jboss.org to a temp folder, then push those bits to a new folder on filemgmt.jboss.org. > If we could simply copy bits over sshfs, the process might be a lot faster than these times: > {code} > JBT coretests 1.1G: 59m20 > JBT core 1.2G: 64m23 > devstudio (copy from filemgmt to filemgmt) 2.4G: 2h13 > devstudio (copy from local to www.qa) 3.1G: 6mins(?) > {code} > To make this work, however, we need more slaves to have sshfs installed. Currently, it appears that only dev01 [1] is so equipped. And that slave, currently, has a build queue more than 170 jobs long, making it impractical to even TEST publishing over sshfs. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev01-rhel5-x86/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23364) bump version of Code Recommenders in JBT TP to 2.4.3 (not 2.4.0)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23364?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23364: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > bump version of Code Recommenders in JBT TP to 2.4.3 (not 2.4.0) > ---------------------------------------------------------------- > > Key: JBIDE-23364 > URL: https://issues.jboss.org/browse/JBIDE-23364 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Fix For: 4.4.2.AM3 > > > This remediation error occurs when trying to install JBT 4.4.2.AM2 into Eclipse JEE bundle Neon.1a: > {code} > Your original request has been modified. > "JavaScript Development Tools" will be ignored because a newer version is already installed. > "Eclipse JSON Editors and Tools" will be ignored because a newer version is already installed. > "WST JSON Core" will be ignored because a newer version is already installed. > Cannot complete the install because of a conflicting dependency. > Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609) > Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645) > Only one of the following can be installed at once: > Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609) > Code Recommenders Dependency Identification UI 2.4.3.v20160913-0645 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160913-0645) > Cannot satisfy dependency: > From: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645) > To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160913-0645] > Cannot satisfy dependency: > From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609) > To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1) > Cannot satisfy dependency: > From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609) > To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23302) https no longer working on tools.jboss.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23302?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23302: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > https no longer working on tools.jboss.org > ------------------------------------------ > > Key: JBIDE-23302 > URL: https://issues.jboss.org/browse/JBIDE-23302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, website > Reporter: Nick Boldt > Fix For: 4.4.2.AM3 > > > Is it expected that tools.jboss.org no longer provides https? > https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg: > {code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901 > {code} > To see this in action, go here: > https://tools.jboss.org --> redirects to http://tools.jboss.org > or, go here: > https://tools.jboss.org:443/ --> redirects to http://tools.jboss.org > I bet this is a problem for eng-ops@ or the new PnT portal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23265?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23265: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > 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.AM3 > > > 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-23170) Red Hat Central page auto-resizing gets broken after editing options

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23170?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23170: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > Red Hat Central page auto-resizing gets broken after editing options > -------------------------------------------------------------------- > > Key: JBIDE-23170 > URL: https://issues.jboss.org/browse/JBIDE-23170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.Final > Environment: Windows 10 Home > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.4.2.AM3 > > Attachments: 2016 09 14 2223 34.mp4, jbosstools-central-webpage-2.0.0-SNAPSHOT.zip > > > I noticed sometimes Red Hat Central stops resizing to editor part size and shows horizontal scrollbar. It happens when options button is clicked when editor part with central is maximized (see attached video). > !2016 09 14 2223 34.mp4! -- 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