[JBoss JIRA] (JBIDE-23497) Integration tests: StoreConnectionTest isnt working
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23497?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23497:
-------------------------------------
Labels: integration_tests (was: )
> Integration tests: StoreConnectionTest isnt working
> ---------------------------------------------------
>
> Key: JBIDE-23497
> URL: https://issues.jboss.org/browse/JBIDE-23497
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.2.Final
>
>
> StoreConnectionTest isnt working. There are a few problems with it:
> * It can trigger the ssl certificate dialog if it's the test is the 1st test that is run against the given connection (and the certificate wasnt stored beforehand). The test wont take this possibility into account
> * The test isnt autonoumous, it relies on a connection being set up beforehand
> * etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23497) Integration tests: StoreConnectionTest isnt working
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-23497:
----------------------------------------
Summary: Integration tests: StoreConnectionTest isnt working
Key: JBIDE-23497
URL: https://issues.jboss.org/browse/JBIDE-23497
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.2.AM3
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.4.2.Final
StoreConnectionTest isnt working. There are a few problems with it:
* It can trigger the ssl certificate dialog if it's the test is the 1st test that is run against the given connection (and the certificate wasnt stored beforehand). The test wont take this possibility into account
* The test isnt autonoumous, it relies on a connection being set up beforehand
* etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-22810:
------------------------------------
Managed to reproduce it with the dev env.
This is design problem. The connections are stored in *ConnectionsRegistry* (from bundle _org.jboss.tools.openshift.common.core_) but this registry is filled by the bundles activators (_org.jboss.tools.openshift.core_ and _org.jboss.tools.openshift.express.core_).
So if no classes are loaded from those bundles, then the registry is not filled.
Solution is to switch to components or extension points
> OpenShift Explorer: empty at start
> ----------------------------------
>
> Key: JBIDE-22810
> URL: https://issues.jboss.org/browse/JBIDE-22810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Environment: windows
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v3, windows
> Fix For: 4.4.2.Final
>
> Attachments: EmptyViewAtStart.png
>
>
> When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections.
> I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-948:
----------------------------------
Assigned to Rob to evaluate non-GUI installer-based install not updating the JBoss Runtime Detection preferences to add ~/devstudio/runtimes.
> Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml
> ----------------------------------------------------------------------------------------
>
> Key: JBTIS-948
> URL: https://issues.jboss.org/browse/JBTIS-948
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Rob Stryker
> Attachments: ds-10.2-pref-cmd-install.png, ds-10.2-pref-gui-install.png
>
>
> Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}.
> The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-948:
--------------------------------
Assignee: Rob Stryker (was: Paul Leacu)
> Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml
> ----------------------------------------------------------------------------------------
>
> Key: JBTIS-948
> URL: https://issues.jboss.org/browse/JBTIS-948
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Rob Stryker
> Attachments: ds-10.2-pref-cmd-install.png, ds-10.2-pref-gui-install.png
>
>
> Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}.
> The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-981) NumberFormatException if you select more features to install
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-981?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-981.
------------------------------
Fix Version/s: 10.1.0.GA
Resolution: Done
https://github.com/jbosstools/jbosstools-integration-stack/commit/278e17c...
Update the JSON files to set the size field.
> NumberFormatException if you select more features to install
> ------------------------------------------------------------
>
> Key: JBTIS-981
> URL: https://issues.jboss.org/browse/JBTIS-981
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Environment: devstudio-is-installer-10.0.0-SNAPSHOT.jar
> devstudio-is-runtime-installer-10.0.0-SNAPSHOT.jar
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 10.1.0.GA
>
>
> {code}
> java.lang.NumberFormatException: For input string: "null"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Long.parseLong(Long.java:589)
> at java.lang.Long.parseLong(Long.java:631)
> at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.calculateAggregateSize(DiskSpaceCheckPanel.java:71)
> at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.getInstallationSize(DiskSpaceCheckPanel.java:94)
> at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.panelActivate(DiskSpaceCheckPanel.java:36)
> at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFrame.java:864)
> at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1475)
> at com.izforge.izpack.installer.InstallerFrame.skipPanel(InstallerFrame.java:1401)
> at com.jboss.devstudio.core.installer.UpdatePacksPanel.panelActivate(UpdatePacksPanel.java:25)
> at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFrame.java:864)
> at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1475)
> at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1443)
> at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionPerformed(InstallerFrame.java:1585)
> at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)
> at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348)
> at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
> at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
> at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
> at java.awt.Component.processMouseEvent(Component.java:6535)
> at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
> at java.awt.Component.processEvent(Component.java:6300)
> at java.awt.Container.processEvent(Container.java:2236)
> at java.awt.Component.dispatchEventImpl(Component.java:4891)
> at java.awt.Container.dispatchEventImpl(Container.java:2294)
> at java.awt.Component.dispatchEvent(Component.java:4713)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888)
> at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4525)
> at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466)
> at java.awt.Container.dispatchEventImpl(Container.java:2280)
> at java.awt.Window.dispatchEventImpl(Window.java:2750)
> at java.awt.Component.dispatchEvent(Component.java:4713)
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
> at java.awt.EventQueue.access$500(EventQueue.java:97)
> at java.awt.EventQueue$3.run(EventQueue.java:709)
> at java.awt.EventQueue$3.run(EventQueue.java:703)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
> at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
> at java.awt.EventQueue$4.run(EventQueue.java:731)
> at java.awt.EventQueue$4.run(EventQueue.java:729)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
> at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months