[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3868:
--------------------------------
Fix Version/s: 11.1.0.AM1
(was: 11.x)
> Document (and check) required disk space before beginning install
> -----------------------------------------------------------------
>
> Key: JBDS-3868
> URL: https://issues.jboss.org/browse/JBDS-3868
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Labels: ui
> Fix For: 11.1.0.AM1
>
>
> The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process.
> Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24448) Application wizard: error decoration is not removed when I correct "Custom Template" url to be valid
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24448?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24448:
-------------------------------------
What I've verified thus far:
Both validators for this widget, anonymously in ApplicationSourceListPage (L316) and ApplicationSourceListPage$TemplateListPageValidator (L706) are returning OK status objects. I've also verified that a cut and paste will also reset the control decorator to a correct value.
Can't seem to find anything else :|
> Application wizard: error decoration is not removed when I correct "Custom Template" url to be valid
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24448
> URL: https://issues.jboss.org/browse/JBIDE-24448
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Environment: Win 10.
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.5.1.AM1
>
>
> Error decorator is not redrawn until windows is resized.
> See screencast: https://youtu.be/BQo-NtDS_c0
> For more detailed info, see JBIDE-23473
> I tried it on Win10 & Fedora 25.... Win10 has this issue, Fedora 25 does not.
> Mac is not affected either.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4417) Bundle org.eclipse.wst.jsdt.nashorn.extension not found
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBDS-4417?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBDS-4417:
-----------------------------------------------
errata-xmlrpc <errata-xmlrpc(a)redhat.com> changed the Status of [bug 1459637|https://bugzilla.redhat.com/show_bug.cgi?id=1459637] from RELEASE_PENDING to CLOSED
> Bundle org.eclipse.wst.jsdt.nashorn.extension not found
> -------------------------------------------------------
>
> Key: JBDS-4417
> URL: https://issues.jboss.org/browse/JBDS-4417
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Affects Versions: 11.0.0.AM1
> Environment: Devstudio installed form devstudio-11.0.0.AM1-v20170531-1042-B189-installer-standalone.jar
> Reporter: Lukáš Valach
> Assignee: Mat Booth
> Priority: Minor
> Fix For: 11.0.0.AM2
>
>
> I have this error message in eclipse log:
> {code}
> !SESSION Wed May 31 14:13:11 CEST 2017 -----------------------------------------
> !ENTRY org.eclipse.equinox.launcher 4 0 2017-05-31 14:13:11.062
> !MESSAGE Could not find extension: org.eclipse.wst.jsdt.nashorn.extension
> !SESSION 2017-05-31 14:13:11.038 -----------------------------------------------
> eclipse.buildId=11.0.0.AM1-v20170531-1042-B189
> java.version=1.8.0_131
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.eclipse.osgi 4 0 2017-05-31 14:13:11.805
> !MESSAGE Bundle org.eclipse.wst.jsdt.nashorn.extension not found.
> {code}
> I see that plugin org.eclipse.wst.jsdt.nashorn.extension isn't installed in .../Devstudio/studio/plugins/ folder.
> Possibly we have to remove this line from devstudio.ini?
> {code}
> -Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24340) CDK3 tools works behind proxy - Test case
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24340?page=com.atlassian.jira.plugi... ]
Ondrej Dockal resolved JBIDE-24340.
-----------------------------------
Resolution: Done
> CDK3 tools works behind proxy - Test case
> -----------------------------------------
>
> Key: JBIDE-24340
> URL: https://issues.jboss.org/browse/JBIDE-24340
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdk, docker, integration-tests, openshift
> Affects Versions: 4.4.4.Final
> Environment: Linux (Fedora), Mac OS, Windows
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.5.1.AM1
>
> Attachments: create_proxy-test_env.sh
>
>
> It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
> Steps to follow:
> 1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] )
> 2. Download/install devstudio
> 3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
> 4. ASSERT: Cannot subscribe minishift-rhel image during minishift start, can be done via cli
> 4. Set env. variable MINISHIFT_HTTP(S)_PROXY
> 5. Start devstudio, add new Container Development Environement server
> 6. Start server adapter
> 7. ASSERT: CDK tools are working properly - CDK started successfully
> * rhel-image was subscribed
> * docker image pulled
> * log into openshift
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24340) CDK3 tools works behind proxy - Test case
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24340?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-24340:
---------------------------------------
There should be discussion whether CDK/OS tooling will support proxy set in IDE and work with them. The question was posed in related jira. Since there is nothing to do here, I am resolving this jira and can be opened once there will be some resolution as of tooling is supporting proxy from IDE.
> CDK3 tools works behind proxy - Test case
> -----------------------------------------
>
> Key: JBIDE-24340
> URL: https://issues.jboss.org/browse/JBIDE-24340
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdk, docker, integration-tests, openshift
> Affects Versions: 4.4.4.Final
> Environment: Linux (Fedora), Mac OS, Windows
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.5.1.AM1
>
> Attachments: create_proxy-test_env.sh
>
>
> It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
> Steps to follow:
> 1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] )
> 2. Download/install devstudio
> 3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
> 4. ASSERT: Cannot subscribe minishift-rhel image during minishift start, can be done via cli
> 4. Set env. variable MINISHIFT_HTTP(S)_PROXY
> 5. Start devstudio, add new Container Development Environement server
> 6. Start server adapter
> 7. ASSERT: CDK tools are working properly - CDK started successfully
> * rhel-image was subscribed
> * docker image pulled
> * log into openshift
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months