[JBoss JIRA] (JBIDE-17975) Reverse the order of version on /documentation/whatsnew
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-17975:
-------------------------------------
Summary: Reverse the order of version on /documentation/whatsnew
Key: JBIDE-17975
URL: https://issues.jboss.org/browse/JBIDE-17975
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: website
Affects Versions: 4.2.0.Beta2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.2.0.Beta3
put the 'stable' on the left, then last 'development' / 'coming soon' on the right.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBDS-3072) Cannot update from JBDS 8.0.0.Beta1 to Beta2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3072?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3072:
----------------------------------
Confirmed, you cannot upgrade from pre-refactoring Alpha (com.jboss.jbds) to post-refactoring Beta, CR or GA (com.jboss.devstudio). A new installer jar is required because p2 won't see the refactored IUs as an upgrade but rather a new install.
That said, your JBDS 8.0.0.Alpha *workspace* (and all the projects therein) should still work with your JBDS 8.0.0.GA install.
> Cannot update from JBDS 8.0.0.Beta1 to Beta2
> --------------------------------------------
>
> Key: JBDS-3072
> URL: https://issues.jboss.org/browse/JBDS-3072
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build
> Affects Versions: 8.0.0.Beta2
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 8.0.0.Beta3
>
> Attachments: beta2c-site-added.png, update-beta1-to-beta2c.png
>
>
> {code}
> Your original request has been modified.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Maven Seam Integration" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Mobile Browser Simulator" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Portlet" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "Maven Integration for Eclipse JDT APT" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration (Experimental)" is already installed, so an update will be performed instead.
> "JBoss OpenShift Tools" is already installed, so an update will be performed instead.
> "JBoss Runtime Seam Detector" is already installed, so an update will be performed instead.
> "Seam 3 Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Developer Studio (Core Features) 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta2-v20140613-0252-B130)
> Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.package 8.0.0.Beta1-v20140408-2350-B93)
> Only one of the following can be installed at once:
> JBoss Developer Studio Project Examples 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.project.examples 8.0.0.Beta1-v20140408-2350-B93)
> JBoss Developer Studio Project Examples 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.project.examples 8.0.0.Beta2-v20140613-0252-B130)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta1-v20140408-2350-B93)
> To: com.jboss.devstudio.core.project.examples [8.0.0.Beta1-v20140408-2350-B93]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta2-v20140613-0252-B130)
> To: com.jboss.devstudio.core.project.examples [8.0.0.Beta2-v20140613-0252-B130]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.package 8.0.0.Beta1-v20140408-2350-B93)
> To: com.jboss.devstudio.core.feature.feature.group [8.0.0.Beta1-v20140408-2350-B93]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17897) Cannot restart Forge runtime - Failed to create the part's controls.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17897?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17897:
---------------------------------------------
no, beta3 is done.
> Cannot restart Forge runtime - Failed to create the part's controls.
> --------------------------------------------------------------------
>
> Key: JBIDE-17897
> URL: https://issues.jboss.org/browse/JBIDE-17897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta2
> Reporter: Radim Hopp
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: screen-view.png
>
>
> After stopping Forge 2.7.0. through Stop button in Forge console view, Stop button remains enabled and Start button remains disabled. Thus user is unable to start forge again without switching forge to forge 1.x and back to 2.7.
> Additionally, when user closes Forge console view when in this "inconsistent" state (forge is stopped, Stop button enabled, start button disabled) and then tries to open again it, console fails to create and this error is thrown:
> {noformat}
> org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:413)
> at org.eclipse.swt.widgets.Widget.addDisposeListener(Widget.java:296)
> at org.jboss.tools.forge.ui.internal.console.AbstractForgeConsole.createControl(AbstractForgeConsole.java:45)
> at org.jboss.tools.forge.ui.internal.part.ForgeConsolePage.createControl(ForgeConsolePage.java:39)
> at org.jboss.tools.forge.ui.internal.part.ForgeConsolePage.createControl(ForgeConsolePage.java:34)
> at org.jboss.tools.forge.ui.internal.part.ForgeConsolePageBook.initializePages(ForgeConsolePageBook.java:30)
> at org.jboss.tools.forge.ui.internal.part.ForgeConsolePageBook.<init>(ForgeConsolePageBook.java:23)
> at org.jboss.tools.forge.ui.internal.part.ForgeConsoleView.createPageBook(ForgeConsoleView.java:43)
> at org.jboss.tools.forge.ui.internal.part.ForgeConsoleView.createPartControl(ForgeConsoleView.java:24)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:140)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityView.createPartControl(CompatibilityView.java:155)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:321)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:888)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:869)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:120)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:337)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:258)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:104)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:73)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:55)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:127)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:983)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:662)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$6.run(PartRenderingEngine.java:547)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:531)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:69)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:983)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:662)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:766)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:737)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:731)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.handleEvent(PartRenderingEngine.java:141)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:187)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4622)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:218)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:81)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.UIElementImpl.setToBeRendered(UIElementImpl.java:303)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:485)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:454)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:692)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:672)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:613)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:601)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1118)
> at org.eclipse.ui.internal.WorkbenchPage.showPart(WorkbenchPage.java:1278)
> at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1269)
> at org.eclipse.ui.internal.WorkbenchPage$13.run(WorkbenchPage.java:4144)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4140)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4120)
> at org.eclipse.ui.internal.quickaccess.ViewElement.execute(ViewElement.java:71)
> at org.eclipse.ui.internal.quickaccess.SearchField$2.handleElementSelected(SearchField.java:179)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:461)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:451)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:496)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1424)
> at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:824)
> at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3269)
> at org.eclipse.swt.widgets.Text.gtk_key_press_event(Text.java:1795)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2098)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510)
> at org.eclipse.swt.widgets.Text.windowProc(Text.java:2744)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9074)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2473)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17973) Obscure database password
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17973?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17973:
---------------------------------------------
btw. if users uses "show environment variables" they will get context sensitive passwords dumped on the screen too.
> Obscure database password
> -------------------------
>
> Key: JBIDE-17973
> URL: https://issues.jboss.org/browse/JBIDE-17973
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Labels: uxtest
> Fix For: 4.3.x
>
>
> When creating an OpenShift application with a database cartridge, the database password is shown in clear text. This password should be obscured.
> It was noted that OpenShift does show clear text passwords in some locations, the difference here is that the user did not prompt for this information meaning we are displaying a password in clear text at a potential point where the user is not aware they need to be in a 'secure' environment.
> Reproduce steps:
> 1. Open new OpenShift Application wizard
> 2. Sign in & proceed to next screen
> 3. Choose application cartridge (JBoss EAP 6 for instance) & proceed to next screen
> 4. Add embedded cartridge for database (mySQL 5.5 for instance) & proceed to next screen
> 5. Click next on set up project screen
> 6. Click finish on next screen
> 7 -> ISSUE HERE. Once app is created, pop-up is shown with mySQL database password shown in clear text. Screenshot: https://www.evernote.com/shard/s230/sh/cd8123fb-a400-4699-ad08-bcbc06f7b5...
> Expected: Password on this pop-up should be obscured.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17972) Add ability to "always accept" the hostkey of the SSH connection for cloning git repos
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17972?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17972:
----------------------------------------
users who do not care about this security aspect can do the following:
In your ~/.ssh/config (if this file doesn't exist, just create it):
Host *
StrictHostKeyChecking no
This will make the check skipped by eclipse, rhc and normal ssh for any hosts.
> Add ability to "always accept" the hostkey of the SSH connection for cloning git repos
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-17972
> URL: https://issues.jboss.org/browse/JBIDE-17972
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Labels: uxtest
> Fix For: 4.3.x
>
>
> Each time JBDS does a git clone, it gives me a warning about the hostkey of the SSH connection. As a developer, I will always accept this. I'd like the ability to click an "always accept" checkbox so I don't have to see this pop-up every time.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17972) Add ability to "always accept" the hostkey of the SSH connection for cloning git repos
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17972?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-17972.
-----------------------------------------
Resolution: Rejected
moving from wont fix to rejected since it turns out we actually support this via standard ssh config files.
> Add ability to "always accept" the hostkey of the SSH connection for cloning git repos
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-17972
> URL: https://issues.jboss.org/browse/JBIDE-17972
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Labels: uxtest
> Fix For: 4.3.x
>
>
> Each time JBDS does a git clone, it gives me a warning about the hostkey of the SSH connection. As a developer, I will always accept this. I'd like the ability to click an "always accept" checkbox so I don't have to see this pop-up every time.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months