[JBoss JIRA] (JBDS-3761) when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3761:
----------------------------------
FWIW:
{code:title=c:\WINDOWS\system32\cmd.exe}
C:\Program Files\Oracle\VirtualBox>where virtualbox
C:\Program Files\Oracle\VirtualBox\VirtualBox.exe{code}
> when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 9.1.0.GA
>
> Attachments: JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png, vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
> !vbox-install-omits-guestadditions.png!
> I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
> Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3761 at 4/4/16 11:36 AM:
-----------------------------------------------------------
After purging the Devplatform installer-installed version of VBox 5.0.8, I reinstalled VBox 5.0.8 by hand from [1].
[1] http://download.virtualbox.org/virtualbox/5.0.8/VirtualBox-5.0.8-103449-W...
Then, using the latest build of the installer (built locally today from latest in master), I get this:
!JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png!
So even though it's installed, the DP installer won't accept it. Perhaps it's a registry issue? Perhaps it's that the installer wants it in c:\devplatform\vbox instead of c:\progra~1\oracle\virtualbox ?
was (Author: nickboldt):
After purging the Devplatform installer-installed version of VBox 5.0.8, I reinstalled VBox 5.0.8 by hand from [1].
Then, using the latest build of the installer (built locally today from latest in master), I get this:
!JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png!
So even though it's installed, the DP installer won't accept it. Perhaps it's a registry issue? Perhaps it's that the installer wants it in c:\devplatform\vbox instead of c:\progra~1\oracle\virtualbox ?
> when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 9.1.0.GA
>
> Attachments: JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png, vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
> !vbox-install-omits-guestadditions.png!
> I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
> Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3761 at 4/4/16 11:36 AM:
-----------------------------------------------------------
After purging the Devplatform installer-installed version of VBox 5.0.8, I reinstalled VBox 5.0.8 by hand from [1].
[1] http://download.virtualbox.org/virtualbox/5.0.8/VirtualBox-5.0.8-103449-W...
*Several reboots later...*
Then, using the latest build of the installer (built locally today from latest in master), I get this:
!JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png!
So even though it's installed, the DP installer won't accept it. Perhaps it's a registry issue? Perhaps it's that the installer wants it in c:\devplatform\vbox instead of c:\progra~1\oracle\virtualbox ?
was (Author: nickboldt):
After purging the Devplatform installer-installed version of VBox 5.0.8, I reinstalled VBox 5.0.8 by hand from [1].
[1] http://download.virtualbox.org/virtualbox/5.0.8/VirtualBox-5.0.8-103449-W...
Then, using the latest build of the installer (built locally today from latest in master), I get this:
!JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png!
So even though it's installed, the DP installer won't accept it. Perhaps it's a registry issue? Perhaps it's that the installer wants it in c:\devplatform\vbox instead of c:\progra~1\oracle\virtualbox ?
> when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 9.1.0.GA
>
> Attachments: JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png, vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
> !vbox-install-omits-guestadditions.png!
> I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
> Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3761:
-----------------------------
Attachment: JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png
After purging the Devplatform installer-installed version of VBox 5.0.8, I reinstalled VBox 5.0.8 by hand from [1].
Then, using the latest build of the installer (built locally today from latest in master), I get this:
!JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png!
So even though it's installed, the DP installer won't accept it. Perhaps it's a registry issue? Perhaps it's that the installer wants it in c:\devplatform\vbox instead of c:\progra~1\oracle\virtualbox ?
> when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 9.1.0.GA
>
> Attachments: JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png, vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
> !vbox-install-omits-guestadditions.png!
> I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
> Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22079) Error when import a project already existing in workspace
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22079:
-------------------------------------
Steps to Reproduce:
ASSERT: Have a project (jboss-kitchensink from EAP template) in workspace.
EXEC: Create a new application using jboss eap template and kitchensink project (CONTEXT_DIR param is equal to kitchensink)
ASSERT: In Import wizard user is asked to provide alternative git repo if it already exists or reuse the existing one. You can choose different git clone location or reuse the one (it does not matter).
EXEC: Finish the import wizard.
RESULT: Application is trying to import a project to workspace but it fails and show the error.
!import-error.png!
was:
ASSERT: Have a project (jboss-kitchensink from EAP template) in workspace.
EXEC: Create a new application using jboss eap template and kitchensink project (CONTEXT_DIR param is equal to kitchensink)
ASSERT: In Import wizard user is asked to provide alternative git repo if it already exists or reuse the existing one. You can choose different git clone location or reuse the one (it does not matter).
EXEC: Finish the import wizard.
RESULT: Application is trying to import a project to workspace but it fails and show the error.
> Error when import a project already existing in workspace
> ---------------------------------------------------------
>
> Key: JBIDE-22079
> URL: https://issues.jboss.org/browse/JBIDE-22079
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: import_wizard, openshift_v3
> Attachments: import-error.png
>
>
> When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear).
> Error:
> {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts.
> One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again.
> An exception stack trace is not available.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22079) Error when import a project already existing in workspace
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22079:
-------------------------------------
Attachment: import-error.png
> Error when import a project already existing in workspace
> ---------------------------------------------------------
>
> Key: JBIDE-22079
> URL: https://issues.jboss.org/browse/JBIDE-22079
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: import_wizard, openshift_v3
> Attachments: import-error.png
>
>
> When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear).
> Error:
> {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts.
> One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again.
> An exception stack trace is not available.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3669) Inject version, timestamp and Jenkins build number into installer to show in installer window
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3669?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3669 at 4/4/16 11:17 AM:
-----------------------------------------------------------
After recent refactorings, here's the new process:
{code}
hub checkout https://github.com/redhat-developer-tooling/developer-platform-install/pu...
gulp; gulp package; gulp 7zip-cleanup
{code}
Of course the same works with a temporary version change applied into the package.json file:
{code}
npm --no-git-tag-version version 0.0.2-v20160404-1103-B667
gulp package; gulp 7zip-cleanup
git checkout package.json # revert temporary change to the version string
{code}
!JBDS3669-new-UI.png!
was (Author: nickboldt):
After recent refactorings, here's the new process:
{code}
hub checkout https://github.com/redhat-developer-tooling/developer-platform-install/pu...
gulp; gulp package; gulp 7zip-cleanup
{code}
Of course the same works with a temporary version change applied into the package.json file:
{code}
npm --no-git-tag-version version 0.0.2-v20160404-1103-B667
gulp package; gulp 7zip-cleanup
git checkout package.json # revert temporary change to the version string
{code}
However, in this case the appended suffix doesn't appear - only the first 3 digits:
!JBDS3669-new-UI.png!
> Inject version, timestamp and Jenkins build number into installer to show in installer window
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-3669
> URL: https://issues.jboss.org/browse/JBDS-3669
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Affects Versions: 9.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: JBDS3669-new-UI.png, version-string-in-exe-and-first-page-of-installer.png
>
>
> Currently this information is not available in installer at execution time, we should create json or js file with this info before executing the build, include it in installer and use during installation to get required data.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3669) Inject version, timestamp and Jenkins build number into installer to show in installer window
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3669?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3669:
-----------------------------
Attachment: (was: JBDS3669-new-UI.png)
> Inject version, timestamp and Jenkins build number into installer to show in installer window
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-3669
> URL: https://issues.jboss.org/browse/JBDS-3669
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Affects Versions: 9.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: JBDS3669-new-UI.png, version-string-in-exe-and-first-page-of-installer.png
>
>
> Currently this information is not available in installer at execution time, we should create json or js file with this info before executing the build, include it in installer and use during installation to get required data.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years