[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22810:
-------------------------------------
So on Windows, this occurred for me 100% of the time (once I followed the exact instructions). After a lot of inspection, I've discovered the following:
1) org.jboss.tools.openshift.core has activator OpenShiftCoreActivator
2) org.jboss.tools.openshift.express.core has activator ExpressCoreActivator
3) o.j.t.openshift.ui extends the common navigator via ext. pt via the OpenShiftExplorerContentProvider class.
a) OpenShiftExplorerContentProvider creates / uses the OpenShiftUIModel
1) OpenShiftUIModel (in o.j.t.o.ui) calls registry.getAll(Connection.class), which loads the o.j.t.o.core activator and initializes it
4) o.j.t.openshift.express.ui extends the common navigator via ext. pt via the ExpressExplorerContentProvider class.
a) ExpressExplorerContentProvider calls registry.getAll(ExpressConnection.class) which loads the o.j.t.o.express.core activator and initializes it
Basically, the driver of the plugin loaders is the UI extensions to the navigator. The express ui will indirectly cause the express core to be loaded. The v3 ui will cause the v3 core to be loaded. There is no error with the plugins not being loaded, and no error with the content providers returning empty arrays due to some race condition.
Even when the view is empty, the content providers **ARE** returning the proper results. So, why is the view empty? I can't 100% figure it out, but I suspect it's something in how the content providers are returning their results. They're unable to discover the proper treepath to inject it into the tree, or something. Either way, I can't figure it out at the moment. It could be something as simple as ConnectionWrapper requiring a .equals() or .hashCode(). I remember such problems in CNF before.
Despite all this, a 1 line fix to force a refresh while the view is being created fixes this situation 100% of the time in my environment. PR is attached.
> 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: Rob Stryker
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v3, windows
> Fix For: 4.5.1.AM1
>
> 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)
8 years, 8 months
[JBoss JIRA] (JBDS-4444) [DevSuite Installer] Move Account step after Confirmation step
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4444?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4444:
-------------------------------------
Is that looking good?
!about-background.png!
> [DevSuite Installer] Move Account step after Confirmation step
> --------------------------------------------------------------
>
> Key: JBDS-4444
> URL: https://issues.jboss.org/browse/JBDS-4444
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: New_and_noteworthy, ui
> Fix For: 11.0.0.GA
>
> Attachments: about-background.png, about-update1.png, devsuite-installer-1.4.0-workflow.png, devsuite-installer-2.0.0-workflow.png, install-step-3-1.png, install-step-3-2.png, install-step-4.png, install-step-5-1.png, install-step-5-2.png, install-step-6-1.png, install-step-6.png, install-step1.png, install-step2.png
>
>
> As a user I would like to avoid entering login/password on a first page of installer, so I can explore and see what can be installed and then provide my credentials if I decided to proceed with installation.
> Current workflow is
> !devsuite-installer-1.4.0-workflow.png|thumbnail!
> should be transformed to
> !devsuite-installer-2.0.0-workflow.png|thumbnail!
> This would require to change starting page to show only generic information about DevSuite Installer and whole first page 'Account' should appear after confirmation page in case any of Red Hat Products is selected for installation.
> Here are screenshots for how it could look like for scenario when Red Hat Product Selected:
> !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-1.png|thumbnail! !install-step-4.png|thumbnail! !install-step-5-2.png|thumbnail! !install-step-6-1.png|thumbnail!
> and when community or 3rd party components only selected:
> !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-2.png|thumbnail! !install-step-5-1.png|thumbnail! !install-step-6.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4444) [DevSuite Installer] Move Account step after Confirmation step
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4444?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4444:
--------------------------------
Attachment: about-background.png
> [DevSuite Installer] Move Account step after Confirmation step
> --------------------------------------------------------------
>
> Key: JBDS-4444
> URL: https://issues.jboss.org/browse/JBDS-4444
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: New_and_noteworthy, ui
> Fix For: 11.0.0.GA
>
> Attachments: about-background.png, about-update1.png, devsuite-installer-1.4.0-workflow.png, devsuite-installer-2.0.0-workflow.png, install-step-3-1.png, install-step-3-2.png, install-step-4.png, install-step-5-1.png, install-step-5-2.png, install-step-6-1.png, install-step-6.png, install-step1.png, install-step2.png
>
>
> As a user I would like to avoid entering login/password on a first page of installer, so I can explore and see what can be installed and then provide my credentials if I decided to proceed with installation.
> Current workflow is
> !devsuite-installer-1.4.0-workflow.png|thumbnail!
> should be transformed to
> !devsuite-installer-2.0.0-workflow.png|thumbnail!
> This would require to change starting page to show only generic information about DevSuite Installer and whole first page 'Account' should appear after confirmation page in case any of Red Hat Products is selected for installation.
> Here are screenshots for how it could look like for scenario when Red Hat Product Selected:
> !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-1.png|thumbnail! !install-step-4.png|thumbnail! !install-step-5-2.png|thumbnail! !install-step-6-1.png|thumbnail!
> and when community or 3rd party components only selected:
> !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-2.png|thumbnail! !install-step-5-1.png|thumbnail! !install-step-6.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24788) [Maven 3.5] hibernate site does not include new hibernate.reddeer plugin; skipTests not working
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24788?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24788 at 8/3/17 12:58 PM:
-------------------------------------------------------------
Reopen.
For some reason, this build [1] contains the correct, newest hibernate 5.2.0.v20170801-2256 (including hibernate.reddeer and hibernate.ui.bot test plugins):
[1] http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-h...
Yet this later build [2] reverts to NOT having the plugin and including the older feature, 5.2.0.v20170413-1559
[2] http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-h...
Looks like the use of `--projects` doesn't always resolve against the local ~/.m2
was (Author: nickboldt):
Reopen.
For some reason, this build [1] contains the correct, newest hibernate 5.2.0.v20170801-2256 (including hibernate.reddeer and hibernate.ui.bot test plugins):
[1] http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-h...
Yet this later build [2] reverts to NOT having the plugin and including the older feature, 5.2.0.v20170413-1559
[2] http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-h...
Looks like the use of ```--projects`` doesn't always resolve against the local ~/.m2
> [Maven 3.5] hibernate site does not include new hibernate.reddeer plugin; skipTests not working
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-24788
> URL: https://issues.jboss.org/browse/JBIDE-24788
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.5.0.Final
>
>
> After switching jobs to use maven 3.5.0, publishing is no longer working -- old artifacts are being pulled from JBT site, rather than using locally-built artifacts.
> So, hibernate site does not include new hibernate.reddeer plugin, causing this failure in the integration tests site build:
> {code}11:54:30 [ERROR] Missing requirement: org.jboss.tools.forge.ui.bot.test 4.4.100.qualifier requires 'bundle org.jboss.tools.hibernate.reddeer 0.0.0' but it could not be found
> {code} - https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Also, the -DskipTests flag is not working.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24788) [Maven 3.5] hibernate site does not include new hibernate.reddeer plugin; skipTests not working
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24788?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24788 at 8/3/17 12:32 PM:
-------------------------------------------------------------
Reopen.
For some reason, this build [1] contains the correct, newest hibernate 5.2.0.v20170801-2256 (including hibernate.reddeer and hibernate.ui.bot test plugins):
[1] http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-h...
Yet this later build [2] reverts to NOT having the plugin and including the older feature, 5.2.0.v20170413-1559
[2] http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-h...
Looks like the use of ```--projects`` doesn't always resolve against the local ~/.m2
was (Author: nickboldt):
Reopen.
For some reason, this build [1] contains the correct, newest hibernate 5.2.0.v20170801-2256 (including hibernate.reddeer and hibernate.ui.bot test plugins):
[1] http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-h...
Yet this later build [2] reverts to NOT having the plugin and including the older feature, 5.2.0.v20170413-1559
[2] http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-h...
> [Maven 3.5] hibernate site does not include new hibernate.reddeer plugin; skipTests not working
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-24788
> URL: https://issues.jboss.org/browse/JBIDE-24788
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.5.0.Final
>
>
> After switching jobs to use maven 3.5.0, publishing is no longer working -- old artifacts are being pulled from JBT site, rather than using locally-built artifacts.
> So, hibernate site does not include new hibernate.reddeer plugin, causing this failure in the integration tests site build:
> {code}11:54:30 [ERROR] Missing requirement: org.jboss.tools.forge.ui.bot.test 4.4.100.qualifier requires 'bundle org.jboss.tools.hibernate.reddeer 0.0.0' but it could not be found
> {code} - https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Also, the -DskipTests flag is not working.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4495) Missing CDI features
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4495?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4495.
------------------------------
Resolution: Done
[~psrna] told me that it was intended. I did not know that moving Seam3 to RH Central means moving whole CDI.
I am sorry for this misunderstanding.
> Missing CDI features
> --------------------
>
> Key: JBDS-4495
> URL: https://issues.jboss.org/browse/JBDS-4495
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, cdi
> Affects Versions: 11.0.0.GA
> Reporter: Lukáš Valach
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 11.0.0.GA
>
> Attachments: No_CDI_Plugins.png
>
>
> I have installed devstudio-11.0.0.GA-v20170801-0412-B670-installer-standalone.jar and I don't see any CDI functionality. It seems that CDI related plugins wasn't installed.
> Help->About->Installation Detains->Plugins, Search for "CDI", there is nothing.
> !No_CDI_Plugins.png|thumbnail!
> JBoss Tools seems to be ok.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24794) Hibernate Reverse Engineering doesn't work on 4.5.0.AM2
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24794?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-24794:
-------------------------------------
Priority: Major (was: Critical)
Turned out that in the screencast for 4.5.0.AM2 i set the default schema while creating the configuration xml fil, while didn't do it on 4.4.4.Final.
It mustn't have been set at all or must have been uppercase: SAKILA.
Still i think that it isn't right that there is no any interaction with user while reverse engineering, when nothing happens. I really would like to get error or warning. Can it be fixed somehow? [~koen.aers] what do you think?
> Hibernate Reverse Engineering doesn't work on 4.5.0.AM2
> -------------------------------------------------------
>
> Key: JBIDE-24794
> URL: https://issues.jboss.org/browse/JBIDE-24794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Dmitrii Bocharov
> Attachments: 4.4.4.Final-works.webm, 4.5.0.AM2-doesnt-work.webm
>
>
> Reverse Engineering doesn't work at the moment, but it worked in 4.4.4.Final. See the attahced screencasts for details.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4495) Missing CDI features
by Lukáš Valach (JIRA)
Lukáš Valach created JBDS-4495:
----------------------------------
Summary: Missing CDI features
Key: JBDS-4495
URL: https://issues.jboss.org/browse/JBDS-4495
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: build, cdi
Affects Versions: 11.0.0.GA
Reporter: Lukáš Valach
Assignee: Jeff MAURY
Priority: Blocker
Fix For: 11.0.0.GA
Attachments: No_CDI_Plugins.png
I have installed devstudio-11.0.0.GA-v20170801-0412-B670-installer-standalone.jar and I don't see any CDI functionality. It seems that CDI related plugins wasn't installed.
Help->About->Installation Detains->Plugins, Search for "CDI", there is nothing.
!No_CDI_Plugins.png|thumbnail!
JBoss Tools seems to be ok.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months