[JBoss JIRA] (JBDS-4033) Cannot add virtualbox box files on windows during installation of CDK via devstuite bundle installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4033?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4033:
--------------------------------
Fix Version/s: 10.2.0.AM3
(was: 10.2.0.AM2)
> Cannot add virtualbox box files on windows during installation of CDK via devstuite bundle installer
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4033
> URL: https://issues.jboss.org/browse/JBDS-4033
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Environment: NB: windows 10 Pro, x86_64
> Virtual machines:
> windows 10 Enterprise, x86_64
> windows 7 Pro, x86_64, SP1
> Reporter: Ondrej Dockal
> Assignee: Denis Golovin
> Priority: Critical
> Labels: release_notes, ui
> Fix For: 10.2.0.AM3
>
>
> Installation ends up with CDK failed status. Others installation of components is completed.
> Error message from install log:
> ------------------------------
> Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute command vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box
> Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute options {
> "env": {
> "ALLUSERSPROFILE": "C:\\ProgramData",
> "APPDATA": "C:\\Users\\jbossqa\\AppData\\Roaming",
> "CommonProgramFiles": "C:\\Program Files\\Common Files",
> "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files",
> "CommonProgramW6432": "C:\\Program Files\\Common Files",
> "COMPUTERNAME": "SOME-PC",
> "ComSpec": "C:\\Windows\\system32\\cmd.exe",
> "FP_NO_HOST_CHECK": "NO",
> "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q",
> "HOMEDRIVE": "C:",
> "HOMEPATH": "\\Users\\jbossqa",
> "LOCALAPPDATA": "C:\\Users\\jbossqa\\AppData\\Local",
> "LOGONSERVER": "\\\\SOME-PC",
> "NUMBER_OF_PROCESSORS": "2",
> "OS": "Windows_NT",
> "Path": "C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\DevelopmentSuite\\jdk8\\bin;C:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;C:\\DevelopmentSuite\\vagrant\\bin;bin;C:\\DevelopmentSuite\\virtualbox\\",
> "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC",
> "PROCESSOR_ARCHITECTURE": "AMD64",
> "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 1, GenuineIntel",
> "PROCESSOR_LEVEL": "6",
> "PROCESSOR_REVISION": "3c01",
> "ProgramData": "C:\\ProgramData",
> "ProgramFiles": "C:\\Program Files",
> "ProgramFiles(x86)": "C:\\Program Files (x86)",
> "ProgramW6432": "C:\\Program Files",
> "PSModulePath": "C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\",
> "PUBLIC": "C:\\Users\\Public",
> "SystemDrive": "C:",
> "SystemRoot": "C:\\Windows",
> "TEMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp",
> "TMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp",
> "USERDOMAIN": "Some-PC",
> "USERNAME": "jbossqa",
> "USERPROFILE": "C:\\Users\\jbossqa",
> "VAGRANT_DETECTED_OS": "cygwin",
> "VBOX_MSI_INSTALL_PATH": "C:\\DevelopmentSuite\\virtualbox\\",
> "windir": "C:\\Windows",
> "windows_tracing_flags": "3",
> "windows_tracing_logfile": "C:\\BVTBin\\Tests\\installpackage\\csilogfile.log",
> "__COMPAT_LAYER": "VistaSetup"
> },
> "cwd": "c:\\DevelopmentSuite\\cdk\\boxes"
> }
> Wed, 31 Aug 2016 11:23:39 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box
> [0;31mAn error occurred while downloading the remote file. The error
> message, if any, is reproduced below. Please fix this error and try
> again.
> ----------------------
> After manual attempt to add box via cli with commad: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box:
> ---------------------
> C:\DevelopmentSuite\cdk\boxes>vagrant box add --name cdkv2 rhel-vagrant-virtualb
> ox.box
> ==> box: Box file was not detected as metadata. Adding it directly...
> ==> box: Adding box 'cdkv2' (v0) for provider:
> box: Unpacking necessary files from: file://C:/DevelopmentSuite/cdk/boxes/rh
> el-vagrant-virtualbox.box
> box:
> An error occurred while downloading the remote file. The error
> message, if any, is reproduced below. Please fix this error and try
> again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4096) profile self is not registered?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4096?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4096:
--------------------------------
Assignee: Fred Bricon
> profile self is not registered?
> -------------------------------
>
> Key: JBDS-4096
> URL: https://issues.jboss.org/browse/JBDS-4096
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 10.2.0.AM1
> Environment: {code}
> Red Hat JBoss Developer Studio
> Version: 10.2.0.AM1
> Build id: AM1-v20160923-1714-B6096
> Build date: 20160923-1714
> $➔ uname -a
> Linux t540p-f24-vm01 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> [14:00:12] nboldt@t540p-f24-vm01:~/devstudio-10.2.0.AM1
> $➔ java -version
> openjdk version "1.8.0_65"
> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> {code}
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Attachments: profile-self-is-not-registered.png
>
>
> Tried to install the m2e-wtp-jsf connector from Central and got this:
> {code}Profile id _SELF_ is not registered.
> java.lang.IllegalArgumentException: Profile id _SELF_ is not registered.
> at org.eclipse.equinox.internal.p2.director.ProfileChangeRequest.createByProfileId(ProfileChangeRequest.java:46)
> at org.eclipse.equinox.p2.operations.InstallOperation.computeProfileChangeRequest(InstallOperation.java:74)
> at org.eclipse.equinox.p2.operations.ProfileChangeOperation.makeResolveJob(ProfileChangeOperation.java:165)
> at org.eclipse.equinox.p2.operations.ProfileChangeOperation.resolveModal(ProfileChangeOperation.java:113)
> at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.resolveInstall(PrepareInstallProfileJob.java:268)
> at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:120)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> eclipse.buildId=unknown
> java.version=1.8.0_65
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product -debug -console -consolelog
> {code}
> !profile-self-is-not-registered.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4062) Error about space in User's Profile location (home) folder should be reported on confirmation page
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4062?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4062:
--------------------------------
Fix Version/s: 10.2.0.AM3
(was: 10.2.0.AM2)
> Error about space in User's Profile location (home) folder should be reported on confirmation page
> --------------------------------------------------------------------------------------------------
>
> Key: JBDS-4062
> URL: https://issues.jboss.org/browse/JBDS-4062
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.2.0.AM3
>
>
> Considering every component from currently provided stack is optional for installation there is no reason to block installation process on Target Install Folder selection page in case user has space in his profile folder name (home folder). It should be reported on Confirmation page when vagrant is selected for install. It should not block installation for OpenJDK and DevStudio only.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22628) Zoom in / out functionality is not working with Visual Page Editor
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22628?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22628:
------------------------------------
[~mickael_istria] we don't generally move up to building with a simrel.X release unless we absolutely have to do so (eg., a breaking API change in WTP forces our hand). If there's a reason to drop support for installation into Neon.0, then [~akazakov] needs to approve that. After that it's a trivial change to make that happen in parent pom (one line) and the job configs (40 one-line changes).
> Zoom in / out functionality is not working with Visual Page Editor
> --------------------------------------------------------------------
>
> Key: JBIDE-22628
> URL: https://issues.jboss.org/browse/JBIDE-22628
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, visual-page-editor-core
> Affects Versions: 4.4.0.Alpha2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: upstream
> Fix For: 4.4.2.AM3
>
>
> New zoom in / out functionality (Cntl + / -) which is available in Neon is not working in Visual Page Editor. The interesting thing, that if you do Zoom in / out in the html editor which supports this functionality and reopen file again in the Visual Editor the new scale will be adjusted
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months