[JBoss JIRA] (JBIDE-21716) Don't re-prompt for password
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21716?page=com.atlassian.jira.plugi... ]
Pete Muir commented on JBIDE-21716:
-----------------------------------
An environment variable which is set per session (as opposed to written to disk e.g. in to your bash .profile or .bashrc) is pretty secure, as once the session ends the password is removed. This is really not very different from storing the password in a field or variable inside your program.
It's not ideal, and long term we should write a vagrant plugin that can handle this better, but for now...
> Don't re-prompt for password
> ----------------------------
>
> Key: JBIDE-21716
> URL: https://issues.jboss.org/browse/JBIDE-21716
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Reporter: Pete Muir
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> Having installed JBDS and CDK from the installer, and entered your password there, you get re-prompted for your password for the customer portal. This is a poor user experience.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21794) Can't create new JIRA from AERI webapp
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-21794:
-----------------------------------
Summary: Can't create new JIRA from AERI webapp
Key: JBIDE-21794
URL: https://issues.jboss.org/browse/JBIDE-21794
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aeri
Reporter: Fred Bricon
When trying to create a new JIRA from the AERI webapp, after selecting the project, the component and version contain irrelevant values:
http://screencast.com/t/lsQydPTusV
Creating a new ticket then fails
Typing unlisted values in those lists is then ignored, so there really is no way for me to open JIRAs from AERI incidents
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21793) Zero-click import of CDK
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21793?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21793:
--------------------------------
Description:
When the installer with the CDK completes, and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
We should try to import the CDK with no-clicks, and hide the detection dialog.
was:We should try to import the CDK with no-clicks, and hide the detection dialog.
> Zero-click import of CDK
> ------------------------
>
> Key: JBIDE-21793
> URL: https://issues.jboss.org/browse/JBIDE-21793
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta2
> Reporter: Pete Muir
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When the installer with the CDK completes, and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
> We should try to import the CDK with no-clicks, and hide the detection dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21793) Zero-click import of CDK
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21793?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21793:
--------------------------------
Description:
When the installer with the CDK completes and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
We should try to import the CDK with no-clicks, and hide the detection dialog.
was:
When the installer with the CDK completes, and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
We should try to import the CDK with no-clicks, and hide the detection dialog.
> Zero-click import of CDK
> ------------------------
>
> Key: JBIDE-21793
> URL: https://issues.jboss.org/browse/JBIDE-21793
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta2
> Reporter: Pete Muir
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When the installer with the CDK completes and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
> We should try to import the CDK with no-clicks, and hide the detection dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21793) Zero-click import of CDK
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21793?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21793:
--------------------------------
Affects Version/s: 4.3.1.Beta2
> Zero-click import of CDK
> ------------------------
>
> Key: JBIDE-21793
> URL: https://issues.jboss.org/browse/JBIDE-21793
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta2
> Reporter: Pete Muir
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When the installer with the CDK completes and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
> We should try to import the CDK with no-clicks, and hide the detection dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-47) Translate breakpoints from .js files to Chromium/Node V8 JavaScript Engine [EBZ#486061]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-47?page=com.atlassian.jira.plugin.sys... ]
Ilya Buziuk commented on ERT-47:
--------------------------------
[~dgolovin], After investigating both JSDT & Chromium breakpoint model !breakpoints.png|thumbnail! I have figured out that using correct annotation id is not the only thing that should be changed to make it work. The main action happens in *BreakpointSynchronizer* which use *ChromiumBreakpointAdapter* - https://github.com/ChromeDevTools/cdt-java/blob/master/plugins/org.chromi... for breakpoint sync
So, if the JSDT breakpoint would be created with the correct Marker attributes mapping will not work - in order to make it work adapter should recognize and process JSDT breakpoint correctly. The main problem is that many things are coupled to ChromiumLineBreakpoint class directly, so it seems that the architecture should be changed to make those two work / sync correctly.
> Translate breakpoints from .js files to Chromium/Node V8 JavaScript Engine [EBZ#486061]
> ---------------------------------------------------------------------------------------
>
> Key: ERT-47
> URL: https://issues.jboss.org/browse/ERT-47
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Assignee: Ilya Buziuk
> Labels: Debug, bzira
> Attachments: breakpoints.png
>
>
> Current implementation in ChromeDevTools can map breakpoints from files in workspace to running VM. Problem is .js file editor from ChomeDevTools should be used to create breakpoints, because breakpoint annotation id used in mapping is different from breakpoint annotation id used in JSDT.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBTIS-564) Cannot install Fuse / SwitchYard tooling in offline mode
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-564?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-564:
----------------------------------
*Reason:* Move dependencies for an offline build out of the devstudio site-ea category.xml and into the jBTIS TP
*Project page/sources:*
*Version:* 4.3.1.Beta1b-SNAPSHOT
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:* JBDSIS
*Include in JBDS:* Yes (JBDSIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
> org.eclipse.rse.dstore.feature.group [3.7.0.201505221634]
> org.eclipse.rse.doc.user [3.4.100.201403101646]
> org.eclipse.rse.connectorservice.local [2.1.400.201403100950]
> org.eclipse.zest.feature.group [1.6.1.201508170204]
> org.eclipse.rse.services [3.3.0.201403100950]
> org.eclipse.rse.subsystems.processes.dstore [2.1.400.201403100950]
> org.eclipse.rse.useractions.feature.group [3.7.0.201505221634]
> org.eclipse.dstore.core [3.4.0.201501311530]
> org.eclipse.rse.dstore.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.core.feature.group [3.7.0.201505221634]
> org.eclipse.rse.subsystems.terminals.ssh [1.0.200.201411271155]
> org.eclipse.rse.importexport [1.2.300.201403100950]
> org.eclipse.rse.processes.ui [3.0.400.201403100950]
> org.eclipse.rse.subsystems.files.dstore [2.1.300.201403100950]
> org.eclipse.rse.connectorservice.ssh [2.1.300.201505220524]
> org.eclipse.rse.core.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.telnet.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.useractions.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.connectorservice.dstore [3.1.301.201403100950]
> org.eclipse.dstore.extra [2.1.400.201403100950]
> org.eclipse.rse.core [3.3.100.201407181907]
> org.eclipse.rse.services.local [2.2.0.201502030655]
> org.eclipse.rse.subsystems.processes.core [3.1.300.201403100950]
> org.eclipse.rse.ftp.feature.group [3.7.0.201505221634]
> org.eclipse.rse.ftp.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.feature.group [3.7.0.201505221634]
> org.eclipse.rse [3.5.0.201403100950]
> org.eclipse.rse.ui [3.3.100.201503112018]
> org.eclipse.rse.subsystems.files.core [3.3.1.201403100950]
> org.eclipse.rse.files.ui [3.2.200.201502052140]
> org.eclipse.rse.subsystems.shells.local [2.1.400.201403100950]
> org.eclipse.rse.subsystems.shells.dstore [2.1.400.201403100950]
> org.eclipse.rse.subsystems.shells.telnet [1.2.300.201403100950]
> org.eclipse.rse.telnet.feature.group [3.7.0.201505221634]
> org.eclipse.rse.subsystems.processes.shell.linux [1.1.400.201403100950]
> org.eclipse.rse.subsystems.files.local [2.1.300.201403251512]
> org.eclipse.rse.terminals.feature.jar [3.8.0.201505221634]
> org.eclipse.rse.subsystems.shells.ssh [2.1.400.201403100950]
> org.eclipse.zest.core [1.5.201.201508170204]
> org.eclipse.rse.dstore.security [3.0.400.201403100950]
> org.eclipse.rse.subsystems.files.ftp [2.2.0.201403100950]
> org.eclipse.rse.local.feature.group [3.7.0.201505221634]
> org.eclipse.zest.layouts [1.1.200.201508170204]
> org.eclipse.rse.ssh.feature.group [3.7.0.201505221634]
> org.eclipse.rse.subsystems.files.ssh [2.1.300.201403100950]
> org.eclipse.rse.terminals.ui [1.3.0.201504210807]
> org.eclipse.zest.feature.jar [1.6.1.201508170204]
> org.eclipse.rse.services.files.ftp [3.0.500.201403100950]
> org.eclipse.rse.subsystems.processes.local [2.1.400.201403100950]
> org.eclipse.rse.subsystems.terminals.core [1.0.300.201411271155]
> org.eclipse.draw2d.feature.jar [3.10.1.201508170204]
> org.eclipse.rse.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.local.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.shells.ui [3.0.500.201403271554]
> org.eclipse.draw2d.feature.group [3.10.1.201508170204]
> org.eclipse.rse.useractions [1.1.500.201403100950]
> org.eclipse.rse.services.ssh [3.2.100.201403281521]
> org.eclipse.rse.terminals.feature.group [3.8.0.201505221634]
> org.eclipse.rse.connectorservice.telnet [1.2.300.201505220524]
> org.apache.commons.net [3.2.0.v201305141515]
> org.eclipse.rse.services.telnet [2.0.400.201403100950]
> org.eclipse.rse.ssh.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.efs.ui [2.1.400.201403100950]
> org.eclipse.rse.efs [2.1.401.201503171741]
> org.eclipse.rse.services.dstore [3.3.0.201406041609]
> org.eclipse.rse.subsystems.shells.core [3.1.300.201403271554]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 66 unique IUs
{code}
> Cannot install Fuse / SwitchYard tooling in offline mode
> --------------------------------------------------------
>
> Key: JBTIS-564
> URL: https://issues.jboss.org/browse/JBTIS-564
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 9.0.0.Beta1
> Environment: JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1a EA Zip (md5 6ab445b312d39c451802232c5a54846b)
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Critical
>
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645)
> Missing requirement: SwitchYard 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) requires 'org.eclipse.zest.feature.group [1.5.0,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645)
> To: org.switchyard.tools.feature.feature.group 0.0.0
> {code}
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731)
> Missing requirement: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731) requires 'org.eclipse.zest.core 0.0.0' but it could not be found
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month