September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23132) When ftl file is opened in devstudio/eclipse it does not get cursor

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23132?page=com.atlassian.jira.plugi... ] Ondrej Dockal reassigned JBIDE-23132: ------------------------------------- Description: When I open a freemarker file (.ftl) in devstudio (project/package explorer), new tab with editor is opened, but there is missing a cursor and I cannot actually set the cursor in calling setCursorPosition and thus, opening of content assistant throws a timeoutexception. It looks like editor is not focused. (was: When I open a freemarker file (.ftl) in devstudio, new tab with editor is opened, but there is missing a cursor and I cannot actually set the cursor in calling setCursorPosition and thus, opening of content assistant throws a timeoutexception. It looks like editor is not focused.) Workaround Description: There is a workaround, open the file twice ( programmatically, something like calling TreeItem.doubleClick()). Workaround: Workaround Exists Assignee: Alexey Kazakov > When ftl file is opened in devstudio/eclipse it does not get cursor > ------------------------------------------------------------------- > > Key: JBIDE-23132 > URL: https://issues.jboss.org/browse/JBIDE-23132 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.4.1.Final > Environment: Fedora 24, x86_64, devstudio: > Version: 10.1.0.GA > Build id: GA-v20160902-1725-B43 > Eclipse neon 1, RC1 > Reporter: Ondrej Dockal > Assignee: Alexey Kazakov > > When I open a freemarker file (.ftl) in devstudio (project/package explorer), new tab with editor is opened, but there is missing a cursor and I cannot actually set the cursor in calling setCursorPosition and thus, opening of content assistant throws a timeoutexception. It looks like editor is not focused. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23132) When ftl file is opened in devstudio/eclipse it does not get cursor

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-23132: ------------------------------------- Summary: When ftl file is opened in devstudio/eclipse it does not get cursor Key: JBIDE-23132 URL: https://issues.jboss.org/browse/JBIDE-23132 Project: Tools (JBoss Tools) Issue Type: Bug Components: freemarker Affects Versions: 4.4.1.Final Environment: Fedora 24, x86_64, devstudio: Version: 10.1.0.GA Build id: GA-v20160902-1725-B43 Eclipse neon 1, RC1 Reporter: Ondrej Dockal When I open a freemarker file (.ftl) in devstudio, new tab with editor is opened, but there is missing a cursor and I cannot actually set the cursor in calling setCursorPosition and thus, opening of content assistant throws a timeoutexception. It looks like editor is not focused. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-852) JBTIS EA composite files refer to a non-existing folder

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-852?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-852. ----------------------------------- Verified, jobs are not failing anymore. > JBTIS EA composite files refer to a non-existing folder > ------------------------------------------------------- > > Key: JBTIS-852 > URL: https://issues.jboss.org/browse/JBTIS-852 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.3.2-SNAPSHOT > > > The composite files at > http://download.jboss.org/jbosstools/mars/staging/updates/integration-sta... > refer to a non-existing folder 4.3.1.CR3 > {code:title=compositeArtifacts.xml} > <?xml version='1.0' encoding='UTF-8'?> > <?compositeArtifactRepository version='1.0.0'?> > <repository name='JBoss Tools Integration Stack Update Site' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'> > <properties size='2'> > <property name='p2.compressed' value='true'/> >  > <property name='p2.timestamp' value='1469541837000'/> > </properties> > <children size='2'> >  > <child location='http://download.jboss.org/jbosstools/mars/staging/updates/integration-sta...'/> > <child location='http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.2-SN...'/> > </children> > </repository> > {code} > The file compositeContent.xml refers to 4.3.1.CR3 as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-852) JBTIS EA composite files refer to a non-existing folder

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-852?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-852. ------------------------------ Fix Version/s: 4.3.2-SNAPSHOT Assignee: Paul Leacu Resolution: Done staging is now at 4.3.2-SNAPSHOT > JBTIS EA composite files refer to a non-existing folder > ------------------------------------------------------- > > Key: JBTIS-852 > URL: https://issues.jboss.org/browse/JBTIS-852 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.3.2-SNAPSHOT > > > The composite files at > http://download.jboss.org/jbosstools/mars/staging/updates/integration-sta... > refer to a non-existing folder 4.3.1.CR3 > {code:title=compositeArtifacts.xml} > <?xml version='1.0' encoding='UTF-8'?> > <?compositeArtifactRepository version='1.0.0'?> > <repository name='JBoss Tools Integration Stack Update Site' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'> > <properties size='2'> > <property name='p2.compressed' value='true'/> >  > <property name='p2.timestamp' value='1469541837000'/> > </properties> > <children size='2'> >  > <child location='http://download.jboss.org/jbosstools/mars/staging/updates/integration-sta...'/> > <child location='http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.2-SN...'/> > </children> > </repository> > {code} > The file compositeContent.xml refers to 4.3.1.CR3 as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23131: ------------------------------------- Fix Version/s: 4.4.2.AM1 > Integration tests: move openshift integration tests to jbosstools/openshift repo > -------------------------------------------------------------------------------- > > Key: JBIDE-23131 > URL: https://issues.jboss.org/browse/JBIDE-23131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test > Fix For: 4.4.2.AM1 > > > we need to move jbosstools/openshift integration tests from their [repo|https://github.com/jbosstools/jbosstools-integration-tests] to the jbosstools/openshift tools [repo|https://github.com/jbosstools/jbosstools-openshift] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23131: ------------------------------------- Labels: integration-test (was: ) > Integration tests: move openshift integration tests to jbosstools/openshift repo > -------------------------------------------------------------------------------- > > Key: JBIDE-23131 > URL: https://issues.jboss.org/browse/JBIDE-23131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test > Fix For: 4.4.2.AM1 > > > we need to move jbosstools/openshift integration tests from their [repo|https://github.com/jbosstools/jbosstools-integration-tests] to the jbosstools/openshift tools [repo|https://github.com/jbosstools/jbosstools-openshift] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23131: ------------------------------------- Sprint: devex #120 September 2016 > Integration tests: move openshift integration tests to jbosstools/openshift repo > -------------------------------------------------------------------------------- > > Key: JBIDE-23131 > URL: https://issues.jboss.org/browse/JBIDE-23131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test > Fix For: 4.4.2.AM1 > > > we need to move jbosstools/openshift integration tests from their [repo|https://github.com/jbosstools/jbosstools-integration-tests] to the jbosstools/openshift tools [repo|https://github.com/jbosstools/jbosstools-openshift] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23131: ---------------------------------------- Summary: Integration tests: move openshift integration tests to jbosstools/openshift repo Key: JBIDE-23131 URL: https://issues.jboss.org/browse/JBIDE-23131 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.4.1.Final Reporter: Andre Dietisheim Assignee: Andre Dietisheim we need to move jbosstools/openshift integration tests from their [repo|https://github.com/jbosstools/jbosstools-integration-tests] to the jbosstools/openshift tools [repo|https://github.com/jbosstools/jbosstools-openshift] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22598) Support runtime detection for manual CDK install

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22598?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22598: -------------------------------- Sprint: devex #120 September 2016 > Support runtime detection for manual CDK install > ------------------------------------------------ > > Key: JBIDE-22598 > URL: https://issues.jboss.org/browse/JBIDE-22598 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, runtime-detection > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.x > > > Right now with CDK 2.1 when you have a manual cdk install (i.e. using cdk.zip and then adding the vagrant box yourself), there will be no .cdk marker, so Runtime Detection will not work. > The only case where Runtime Detection will work is when you use the (as of now Windows-only) suite installer. At that point Runtime Detection will do its thing silently without you noticing. > The way I see it there are two options: > a) Create and upstream issue with CDK and ask them to include a basic .cdk in their zip > b) Make the runtime detection work without .cdk -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23123) tooling blocks docker cert files even after cdk is stopped on Windows

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23123?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-23123: --------------------------------------- Also, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=492235 upstream for updates on the Docker client. This issue is about Spotify client 3.6.4 but once it is resolved (this task requires a lot of third-party dependency updates), updating to a newer version of the library should be easier (but may still require some code changes if some API changed). > tooling blocks docker cert files even after cdk is stopped on Windows > --------------------------------------------------------------------- > > Key: JBIDE-23123 > URL: https://issues.jboss.org/browse/JBIDE-23123 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker > Affects Versions: 4.4.1.Final > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Critical > > When you stop cdk in Eclipse, it does "vagrant halt" but it seems something still holds a lock on the docker cert files, because I can't do "vagrant destroy" from CLI. > Steps: > 1. Start cdk in Eclipse > 2. Open Docker Explorer and expand to see the containers > 3. Stop cdk in Eclipse > 4. run "vagrant destroy" in CLI > This will fail: > {code} > $ vagrant destroy > default: Are you sure you want to destroy the 'default' VM? [y/N] y > ==> default: Destroying VM and associated drives... > C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/fileutils.rb:1444:in `rmdir': Directory not empty @ dir_s_rmdir - C:/mmalina/cdk2.2.rc3/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker (Errno::ENOTEMPTY) > from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/fileutils.rb:1444:in `block in remove_dir1' > from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/fileutils.rb:1458:in `platform_support' > from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/fileutils.rb:1443:in `remove_dir1' > from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/fileutils.rb:1436:in `remove' > from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/fileutils.rb:778:in `block in remove_entry' > from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/fileutils.rb:1493:in `postorder_traverse' > from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/fileutils.rb:776:in `remove_entry' > from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/fileutils.rb:634:in `block in rm_r' > from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/fileutils.rb:630:in `each' > from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/fileutils.rb:630:in `rm_r' > from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/pathname.rb:575:in `rmtree' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:345:in `block in id=' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:343:in `each' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:343:in `id=' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/providers/virtualbox/action/destroy.rb:12:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:95:in `block in finalize_action' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:95:in `block in finalize_action' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/providers/virtualbox/action/forced_halt.rb:20:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:95:in `block in finalize_action' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder.rb:116:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `block in run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:19:in `busy' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin/call.rb:53:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:95:in `block in finalize_action' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:95:in `block in finalize_action' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder.rb:116:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `block in run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:19:in `busy' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin/call.rb:53:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/providers/virtualbox/action/discard_state.rb:15:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:95:in `block in finalize_action' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder.rb:116:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `block in run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:19:in `busy' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin/call.rb:53:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin/env_set.rb:19:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin/provisioner_cleanup.rb:25:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin/config_validate.rb:25:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:95:in `block in finalize_action' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder.rb:116:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `block in run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:19:in `busy' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin/call.rb:53:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:95:in `block in finalize_action' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder.rb:116:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `block in run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:19:in `busy' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin/call.rb:53:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/Users/rasp/.vagrant.d/gems/gems/vagrant-registration-1.3.0/lib/vagrant-registration/action/unregister_on_destroy.rb:29:in `rescue in call' > from C:/Users/rasp/.vagrant.d/gems/gems/vagrant-registration-1.3.0/lib/vagrant-registration/action/unregister_on_destroy.rb:14:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder.rb:116:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `block in run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:19:in `busy' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `run' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:224:in `action_raw' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:199:in `block in action' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:561:in `lock' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:185:in `call' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:185:in `action' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/commands/destroy/command.rb:31:in `block in execute' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/plugin/v2/command.rb:235:in `block in with_target_vms' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/plugin/v2/command.rb:229:in `each' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/plugin/v2/command.rb:229:in `with_target_vms' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/commands/destroy/command.rb:30:in `execute' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/cli.rb:42:in `execute' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:302:in `cli' > from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/bin/vagrant:174:in `<main>' > {code} > It simply cannot remove /rhel-ose/.vagrant/machines/default/virtualbox/docker which contains the certificates for docker connection. > Note that without step 2. this works, so it may actually be docker tooling who's at fault here. > Environment: > devstudio 10.1.0.GA B5921 > cdk 2.2 rc3 > Windows 10 x64 -- 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 September 2016