[JBoss JIRA] (JBDS-3633) Uninstaller does nothing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3633?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3633:
--------------------------------
Description:
Current implementation just removes record about installation from windows registry.
What it should do:
1. Remove virtual box from vagrant:
{code}vagrant box remove cdk_v2{code}
2. Remove virtual machine from virtual box
{code}vboxmanage --unregister ${vmname}{code}
3. Uninstall what was installed:
vargant
virtual box
developer studio
4. Delete:
CDK
Open JDK 8
5. Cleanup PATH env variable
was:Current implementation just removes record about installation fro windows registry
> Uninstaller does nothing
> ------------------------
>
> Key: JBDS-3633
> URL: https://issues.jboss.org/browse/JBDS-3633
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> Current implementation just removes record about installation from windows registry.
> What it should do:
> 1. Remove virtual box from vagrant:
> {code}vagrant box remove cdk_v2{code}
> 2. Remove virtual machine from virtual box
> {code}vboxmanage --unregister ${vmname}{code}
> 3. Uninstall what was installed:
> vargant
> virtual box
> developer studio
> 4. Delete:
> CDK
> Open JDK 8
> 5. Cleanup PATH env variable
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3690) Update to CDK Beta5
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBDS-3690:
------------------------------------
Summary: Update to CDK Beta5
Key: JBDS-3690
URL: https://issues.jboss.org/browse/JBDS-3690
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Reporter: Alexey Kazakov
Priority: Critical
Fix For: 9.1.0.CR1
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3689) ask user for JDK location when old location is gone
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3689?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3689:
------------------------------------
Fix Version/s: 4.4
Assignee: Mickael Istria (was: Max Rydahl Andersen)
This functionality comes from Eclipse. Not JBDS. And I agree it would be more user-friendly to at least suggest to update the *.ini file to point it to some correct jvm location.
[~mickael_istria] can you take a look and at least report this issue to Eclipse? Thanks!
> ask user for JDK location when old location is gone
> ---------------------------------------------------
>
> Key: JBDS-3689
> URL: https://issues.jboss.org/browse/JBDS-3689
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: upstream
> Affects Versions: 9.1.0.Beta2
> Environment: Fedora 23
> Reporter: Aleksandar Kostadinov
> Assignee: Mickael Istria
> Fix For: 4.4
>
>
> Hello, installed 9.1.0.Beta2 and starting it after some fedora update, yielded an error that JDK is not found. With no help how to fix.
> Searching over the internet I found
> https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu...
> But it makes much more sense to let the user select a different location. Or at least point user at the ini file to be updated. Currently user is left wondering why JBDS fails to start when system has a perfectly working JDK installed on standard location. My first thought was that for some reason JBDS installation broke.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21849?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21849:
---------------------------------------------
I have no real concept of what supporting Atomic Platform means - I assume it means supporting plain Kubernetes ?
Then yes, that was not a goal/requirement, but something that might/probably will come up later.
Agree it would not be a 9.1 thing, but something to consider for next major.
> [AP] Not able to list services under a project after login to AP
> ----------------------------------------------------------------
>
> Key: JBIDE-21849
> URL: https://issues.jboss.org/browse/JBIDE-21849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: -JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191
> -AP puddle: 2016-03-09.2
> -oc version:
> oc v3.2.0.1
> kubernetes v1.2.0-alpha.7-703-gbc4550d
> Reporter: Xia Zhao
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.x
>
>
> -Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}"
> -Issue did not repro if switch to OSE
> -Repro on Linux/Windows/Mac OS
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21836:
---------------------------------------------
[~mlabuda] if I have set a value in the preferences my path should not influence this at all. The path is *last* place to lookup, not the first.
[~scabanovich] I'll try when I run this on my windows instance again.
> Preferences: openshift 3 oc location resets to a different/old value on restart
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21836
> URL: https://issues.jboss.org/browse/JBIDE-21836
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: oc_binary, openshift_v3, preferences
> Fix For: 4.3.1.CR1
>
>
> on start of eclipse new workspace the value is for reason unknown to me set to:
> {code}
> /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc
> {code}
> which does exist, but is old version and publish fails.
> Then I set it to
> {code}
> /usr/local/bin/oc
> {code}
> now publish works.
> Restart eclipse - old value returns and publish starts failing again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years