[JBoss JIRA] (JBIDE-22641) When an Openshift connection is deleted, the secure entries are not removed
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22641?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22641.
---------------------------------
Verified in devstudio 10.0.1.AM2 build ID AM2-v20160725-1821-B5680
> When an Openshift connection is deleted, the secure entries are not removed
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22641
> URL: https://issues.jboss.org/browse/JBIDE-22641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Jeff MAURY
> Assignee: Dmitry Bocharov
> Priority: Critical
> Labels: connection, openshift_v3, secure_storage
> Fix For: 4.4.1.AM2
>
>
> When a token or password is saved in secure storage for an Openshift connection, then deleting this connection will not remove this data from secure storage. Then creating a new connection with the same address will reuse this infos. This is a security breach
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22646) Starting cdk creates two processes in debug view
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22646?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22646.
---------------------------------
Yeah, that's what I thought. But your description of this JIRA seemed as if there should be two processes, but one should disappear once vagrant up is done. So I wondered what the other process would be.
Closing.
> Starting cdk creates two processes in debug view
> ------------------------------------------------
>
> Key: JBIDE-22646
> URL: https://issues.jboss.org/browse/JBIDE-22646
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk, server
> Affects Versions: 4.4.1.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.1.AM1
>
>
> Starting cdk creates two processes in debug view.
> One does not disappear when the startup process is complete.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-654:
-------------------------------------------
And this detection works seamingless with the runtime detection from within Eclipse itself ? Then awesome! Exactly how i invisioned it ;)
I'll let [~akazakov] answer on when it fits on getting it into sprints and merge.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png, inst1.png, inst1a.png, inst2.png, inst3.png, inst4.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBDS-3757) Add some logging to setup routines
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3757?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3757:
--------------------------------
Sprint: (was: devex #118 July 2016)
> Add some logging to setup routines
> ----------------------------------
>
> Key: JBDS-3757
> URL: https://issues.jboss.org/browse/JBDS-3757
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM3
>
>
> We should log events in setup the same way we now do in download and install phases. For example when the install -> setup transition happens, when setup is fired for an already existing item.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months