[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3981:
-----------------------------
Attachment: IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt
rh-eclipse46-devstudio.provides.list.02
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23031) OpenShift can't push Docker Images with latest Docker Neon.1 bits
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23031?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-23031:
----------------------------------------
I have merged https://github.com/jbosstools/jbosstools-openshift/pull/1295
Thanks [~rob.stryker].
> OpenShift can't push Docker Images with latest Docker Neon.1 bits
> -----------------------------------------------------------------
>
> Key: JBIDE-23031
> URL: https://issues.jboss.org/browse/JBIDE-23031
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Environment: DevStudio 10.1.0.AM3
> Docker Tooling 2.1.0.201608221023
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 4.4.1.Final
>
>
> After installing Docker Tooling 2.1.0.201608221023 on top of Devstudio 10.1.0.AM3, when I try to push a docker image to openshift, I get this error:
> {noformat}
> java.lang.NoClassDefFoundError: org/eclipse/linuxtools/internal/docker/ui/views/ImagePushProgressHandler
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:66)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler cannot be found by org.jboss.tools.openshift.ui_3.3.0.v20160812-0126
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 3 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3627:
---------------------------------
Fix Version/s: 10.1.0.GA
(was: 10.1.0.AM3)
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.GA
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3614) DevSuite Installer
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3614?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3614:
---------------------------------
Fix Version/s: 10.1.0.GA
(was: 10.1.0.AM3)
> DevSuite Installer
> ------------------
>
> Key: JBDS-3614
> URL: https://issues.jboss.org/browse/JBDS-3614
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Fix For: 10.1.0.GA
>
>
> Make installer that has:
> VirtualBox
> Vagrant
> Cygwin
> CDK
> (custom VagrantFile?)
> (docker client?)
> OpenJDK
> Red Hat Developer Studio 9.1
> (with or without JBoss EAP ? - EAP 7 not available)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3797) Installer: temporary files are not removed when window is closed
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3797?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3797:
---------------------------------
Fix Version/s: 10.1.0.GA
(was: 10.1.0.AM3)
> Installer: temporary files are not removed when window is closed
> ----------------------------------------------------------------
>
> Key: JBDS-3797
> URL: https://issues.jboss.org/browse/JBDS-3797
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer, upstream
> Reporter: Pavol Pitonak
> Labels: havoc
> Fix For: 10.1.0.GA
>
>
> # download installer exe
> # run DeveloperPlatformInstaller*.exe
> # when installer's window opens, close the window
> # look into _C:\Users\yourusername\AppData\Local\Temp_
> result:
> Temp folder contains several files and directories with name starting *7zS*, with total size of about *1.7GB*, when you open start the installer multiple times, it appears multiple times in Temp
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3758) when something goes wrong, give user call to action / report of what went wrong
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3758?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3758:
---------------------------------
Fix Version/s: 10.1.0.GA
(was: 10.1.0.AM3)
> when something goes wrong, give user call to action / report of what went wrong
> -------------------------------------------------------------------------------
>
> Key: JBDS-3758
> URL: https://issues.jboss.org/browse/JBDS-3758
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: jbds-install-ste-failed-progress-bar-keeps-moving.png
>
>
> I attempted to install from Setup-bundled-0.0.2-20160401-33.exe and while the installer was OK with my using my pre-installed JDK 8 in C:\Program Files\Java\jdk1.8.0_25 (or C:\Program Files\Java\jre1.8.0_25) it then ran into a problem using that JDK to install JBDS.
> I noticed the problem at about 12% on the progress bar but it was still moving along at 45% when I grabbed the screenshot (attached).
> If a failure occurs, perhaps *we could change the bar from blue to red and move it to 100%* ?
> Also, should there be a call to action for the user?
> Even something simple like "*go check in C:\DeveloperPlatform\install.log for what might have happened*" would be useful here.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3869) platform installer should check/warn if Hyper-V is already enabled.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3869:
---------------------------------
Fix Version/s: 10.1.0.GA
(was: 10.1.0.AM3)
> platform 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
> Fix For: 10.1.0.GA
>
>
> 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
(v6.4.11#64026)
9 years, 7 months