February 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4223) Promisify installer's detection methods

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4223?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4223: -------------------------------- Fix Version/s: 10.4.0.AM1 (was: 10.3.0.AM2) > Promisify installer's detection methods > --------------------------------------- > > Key: JBDS-4223 > URL: https://issues.jboss.org/browse/JBDS-4223 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.3.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.4.0.AM1 > > > Current implementation gets callbak to notify about detection results, method should return promise instance instead to simplify chaining and testing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4246) Implement minishift cdk-setup in devsuite installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4246?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4246: -------------------------------- Fix Version/s: 10.4.0.AM1 (was: 10.3.0.AM2) > Implement minishift cdk-setup in devsuite installer > --------------------------------------------------- > > Key: JBDS-4246 > URL: https://issues.jboss.org/browse/JBDS-4246 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Environment: Windows, mac OS, Linux > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.4.0.AM1 > > > Instead of downloading three resources from three different URL's installer will need to download only one and run with 'cdk-setup' parameter during installation: > 1. copy minishift to $\{target.folder\}/cdk/bin > 2. remove ~/.minishift > 3.1. run for virtualbox setup $\{target.folder\}/cdk/bin/minishift.exe setup-cdk --default-vm-driver=virtualbox > 3.2. run for hyper-v setup $\{target.folder\}/cdk/bin/minishift.exe setup-cdk > 4. find location of oc.exe in ~/.minishift/cache/** and add it to PATH > 5. add $\{target.folder\}/cdk/bin to PATH -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4159) On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4159: -------------------------------- Fix Version/s: 10.4.0.AM1 (was: 10.3.0.GA) > On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-4159 > URL: https://issues.jboss.org/browse/JBDS-4159 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 1.1.0.GA > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.4.0.AM1 > > > On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The current embedded CDK is expecting Docker in a Virtualbox. The installer should handle both cases. > here is the error: > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > ==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569 > ==> default: Clearing any previously set network interfaces... > ==> 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... > There was an error while executing `VBoxManage`, a CLI used by Vagrant > for controlling VirtualBox. The command and stderr is shown below. > Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"] > Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX) > VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3869) DevSuite Installer should check/warn if Hyper-V is already enabled

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3869: -------------------------------- Fix Version/s: 10.4.0.AM1 (was: 10.3.0.AM2) > DevSuite Installer should check/warn if Hyper-V is already enabled > ------------------------------------------------------------------ > > Key: JBDS-3869 > URL: https://issues.jboss.org/browse/JBDS-3869 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 10 Pro, 64 bit. > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: ui > Fix For: 10.4.0.AM1 > > > 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 (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23872) Tools clear war deployed files

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23872?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23872: ------------------------------------- I am experiencing the following: 1) When i close the workspace, the server itself is terminated 2) When i re-open the workspace, the server requires a republish 3) If I start the server, a request for PUBLISH_FULL is made, however... the exact same logic is used at this point whether we have a clean or a full publish request. We never use the 'kind' or 'modulePublishState' or 'deltaKind' variables again. We only use the return value of this method, in this case, FULL_PUBLISH. I've tried it on linux and on windows. It works for me in both environments. Basically, after a workspace restart, the state of the module is 'unknown'. Whether we get a 'clean' publish request, or you just start the server and we get get an automatic 'full' publish request, we do the exact same behavior. And [~cweiler], there is a 'Full Publish' action if you right-click on the module instead of on the server. However, as I said, simply starting the server, or executing a normal 'publish', or executing a 'full publish' or a 'clean...' all have the exact same behavior when executed after a workspace restart. After a workspace restart, the module is in an unknown state, and **always** gets a full / clean publish. We treat these as identical. [~mmalina] Can you replicate this? > Tools clear war deployed files > ------------------------------ > > Key: JBIDE-23872 > URL: https://issues.jboss.org/browse/JBIDE-23872 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.Final > Environment: Windows 7 64 > JDK 8 > Eclipse Neon 1 > JBoss Tools 4.4 > WildFly 10.1 > Reporter: Claudio Weiler > Assignee: Rob Stryker > Fix For: 4.4.3.Final > > > After an Eclipse start war deployed files are deleted and not republished. > I have created a system lock to one of the html resources to try to dig more infos, but the exception shown refers to another resource: > "Error renaming D:\Aplic\wildfly-10.1.0\standalone\tmp\tmp7250132485298982117.MF to D:\Aplic\wildfly-10.1.0\standalone\deployments\testing-ear.ear\META-INF\MANIFEST.MF." -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4277) Migrate rpm jobs from Wonka to CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4277?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4277: -------------------------------- Assignee: Nick Boldt > Migrate rpm jobs from Wonka to CCI > ---------------------------------- > > Key: JBDS-4277 > URL: https://issues.jboss.org/browse/JBDS-4277 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Affects Versions: 10.3.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Migrate the rpm and signing jobs to CCI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4277) Migrate rpm jobs from Wonka to CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4277?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4277: ----------------------------- Description: Migrate the 2 rpm and 2 signing jobs to CCI: http://wonka.mw.lab.eng.bos.redhat.com/jenkins/view/devstudio/ was:Migrate the rpm and signing jobs to CCI. > Migrate rpm jobs from Wonka to CCI > ---------------------------------- > > Key: JBDS-4277 > URL: https://issues.jboss.org/browse/JBDS-4277 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Affects Versions: 10.3.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Migrate the 2 rpm and 2 signing jobs to CCI: > http://wonka.mw.lab.eng.bos.redhat.com/jenkins/view/devstudio/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4277) Migrate rpm jobs from Wonka to CCI

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4277: -------------------------------- Summary: Migrate rpm jobs from Wonka to CCI Key: JBDS-4277 URL: https://issues.jboss.org/browse/JBDS-4277 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Sub-task Components: build Affects Versions: 10.3.0.AM2 Reporter: Nick Boldt Migrate the rpm and signing jobs to CCI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23872) Tools clear war deployed files

by Claudio Weiler (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23872?page=com.atlassian.jira.plugi... ] Claudio Weiler updated JBIDE-23872: ----------------------------------- Workaround Description: Server adapter "Clean..." context menu action. or For each added module do a "Full Publish" context menu action. was:"Clean" the deployment and "Full Publish" > Tools clear war deployed files > ------------------------------ > > Key: JBIDE-23872 > URL: https://issues.jboss.org/browse/JBIDE-23872 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.Final > Environment: Windows 7 64 > JDK 8 > Eclipse Neon 1 > JBoss Tools 4.4 > WildFly 10.1 > Reporter: Claudio Weiler > Assignee: Rob Stryker > Fix For: 4.4.3.Final > > > After an Eclipse start war deployed files are deleted and not republished. > I have created a system lock to one of the html resources to try to dig more infos, but the exception shown refers to another resource: > "Error renaming D:\Aplic\wildfly-10.1.0\standalone\tmp\tmp7250132485298982117.MF to D:\Aplic\wildfly-10.1.0\standalone\deployments\testing-ear.ear\META-INF\MANIFEST.MF." -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23872) Tools clear war deployed files

by Claudio Weiler (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23872?page=com.atlassian.jira.plugi... ] Claudio Weiler edited comment on JBIDE-23872 at 2/9/17 3:17 PM: ---------------------------------------------------------------- [~rob.stryker] what is strange? "Full project publish" and "clean server" are workarounds, not issues. edit. There is no "full publish" action on server view, only "publish" and this action do not work like "clean" action. was (Author: cweiler): [~rob.stryker] what is strange? "Full project publish" and "clean server" are workarounds, not issues. > Tools clear war deployed files > ------------------------------ > > Key: JBIDE-23872 > URL: https://issues.jboss.org/browse/JBIDE-23872 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.Final > Environment: Windows 7 64 > JDK 8 > Eclipse Neon 1 > JBoss Tools 4.4 > WildFly 10.1 > Reporter: Claudio Weiler > Assignee: Rob Stryker > Fix For: 4.4.3.Final > > > After an Eclipse start war deployed files are deleted and not republished. > I have created a system lock to one of the html resources to try to dig more infos, but the exception shown refers to another resource: > "Error renaming D:\Aplic\wildfly-10.1.0\standalone\tmp\tmp7250132485298982117.MF to D:\Aplic\wildfly-10.1.0\standalone\deployments\testing-ear.ear\META-INF\MANIFEST.MF." -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017