[JBoss JIRA] (JBIDE-23320) New server window server type picker is single line long on Cinnamon
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23320?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23320.
---------------------------------
I assume this is fixed. Please let us know if you experience otherwise.
> New server window server type picker is single line long on Cinnamon
> --------------------------------------------------------------------
>
> Key: JBIDE-23320
> URL: https://issues.jboss.org/browse/JBIDE-23320
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Environment: Fedora 24 x86-64
> Cinnamon 3.0.7
> Linux 4.7.6
> JBDS 10.1.0.GA
> Reporter: Michal Jurc
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: jbds-10.1-new-server.png
>
>
> In JBoss Developer Studio 10.1.0.GA, the New Server window server type choice only displays single server at time without scrolling which is uncomfortable to navigate through.
> Screenshot attached.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-20676) NPE in org.jboss.tools.jst.web.ui.palette.PaletteAdapter.refreshDynamicDrawer()
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20676?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-20676.
---------------------------------
Verified in devstudio-10.3.0.AM2-v20170127-1155-B6970-installer-eap.jar
> NPE in org.jboss.tools.jst.web.ui.palette.PaletteAdapter.refreshDynamicDrawer()
> -------------------------------------------------------------------------------
>
> Key: JBIDE-20676
> URL: https://issues.jboss.org/browse/JBIDE-20676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.3.0.CR1
> Environment: Linux x86_64 SWT_GTK3=1
> Reporter: Denis Golovin
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.3.AM1
>
>
> Exception below occurs in case of switching between jsp and html editord oprened for the same html5 file. kitchensink-angularjs example from central is good test project for this issue. {code}java.lang.NullPointerException
> at org.jboss.tools.jst.web.ui.palette.PaletteAdapter.refreshDynamicDrawer(PaletteAdapter.java:130)
> at org.jboss.tools.jst.web.ui.palette.PaletteAdapter.activated(PaletteAdapter.java:101)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.PalettePageImpl$1.partActivated(PalettePageImpl.java:71)
> at org.eclipse.ui.internal.WorkbenchPage$14.run(WorkbenchPage.java:4885)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4882)
> at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4870)
> at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:202)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:245)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:242)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:711)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:639)
> at org.eclipse.e4.ui.internal.workbench.swt.AbstractPartRenderer.activate(AbstractPartRenderer.java:106)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer$1.handleEvent(ContributedPartRenderer.java:63)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1338)
> at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1756)
> at org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:3073)
> at org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:3009)
> at org.eclipse.swt.widgets.Composite.gtk_button_press_event(Composite.java:731)
> at org.eclipse.swt.widgets.Tree.gtk_button_press_event(Tree.java:1839)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1959)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5590)
> at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3612)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4717)
> 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:9279)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1225)
> 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:2425)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488){code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23624) clean up skipTests / swtbot.tests.skip references in integration tests
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23624?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23624.
---------------------------------
> clean up skipTests / swtbot.tests.skip references in integration tests
> ----------------------------------------------------------------------
>
> Key: JBIDE-23624
> URL: https://issues.jboss.org/browse/JBIDE-23624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1
>
>
> Rob said:
> {quote}
> swtbot.test.skip is old and shouldnt exist anymore {quote}
> {code}
> $➔ find.sh . "pom.xml" swtbot.test.skip
> ** [1] ./tests/org.jboss.tools.easymport.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <swtbot.test.skip>false</swtbot.test.skip>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> {code}
> Andre said:
> {quote}
> this seems to make no sense at all. These are tests. Why would you want to skip them by default?{quote}
> {code}
> ** [1] ./tests/org.jboss.tools.ui.bot.ext.test/pom.xml **
> 13-
> 14- <properties>
> 15: <skipTests>true</skipTests>
> 16- </properties>
> 17-</project>
> ** [2] ./tests/pom.xml **
> 22- <junitExtensionsProperties>-Dreddeer.close.shells=${reddeer.close.shells} -Dreddeer.close.welcome.screen=${reddeer.close.welcome.screen} -Dreddeer.disable.maven.download.repo.index.on.startup=${reddeer.disable.maven.download.repo.index.on.startup}</junitExtensionsProperties>
> 23- <integrationTestsSystemProperties>-Dswt.bot.test.record.screencast=${swt.bot.test.record.screencast} -Dorg.eclipse.swtbot.screenshots.dir=${project.build.directory}/screenshots -Dusage_reporting_enabled=false -Dcom.atlassian.connector.eclipse.monitor.usage.first.time=false -Dcom.atlassian.connector.eclipse.monitor.usage.enabled=false ${junitExtensionsProperties}</integrationTestsSystemProperties>
> 24: <skipTests>true</skipTests>
> 25- <test.installPath.OSX></test.installPath.OSX>
> 26- <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
> {code}
> There are also three examples of hardcoding skipTests to false, for no obvious reason:
> {code}
> $➔ find.sh . "pom.xml" \<skipTests\>false
> ** [1] ./tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml **
> 19- -->
> 20- <properties>
> 21: <skipTests>false</skipTests>
> 22- <usage_reporting_enabled>false</usage_reporting_enabled>
> 23- <!-- Maven configuration -->
> ** [2] ./tests/org.jboss.tools.arquillian.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <skipTests>false</skipTests>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> ** [3] ./tests/org.jboss.tools.examples.ui.bot.test/pom.xml **
> 30- <jbosstools.test.jboss-eap-7.x.url>http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0/jboss-eap-7.0.0...</jbosstools.test.jboss-eap-7.x.url>
> 31- <surefire.timeout>18000</surefire.timeout>
> 32: <skipTests>false</skipTests>
> 33- <deployOnServer>true</deployOnServer>
> 34- </properties>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4263) possible use constraint violation from slf4j / slf4j-api
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4263:
------------------------------------
The problem is caused by Teiid Designer and Teiid Designer Runtime.
Teiid DataTools Connectivity and Teiid Runtime Clients don't cause problem.
IS repository contains SwitchYard 2.3.0.CR1-v20170120-1347-B20 which works properly.
> possible use constraint violation from slf4j / slf4j-api
> --------------------------------------------------------
>
> Key: JBDS-4263
> URL: https://issues.jboss.org/browse/JBDS-4263
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.3.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 10.3.0.GA
>
> Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> [~lvalach] said: {quote}
> Hi Nick,
> I tested installation of stuff from central as you described. I am not finished yet, but here is what I found.
> -install latest integration stack bits from IS
> -JBoss Fule Development - OK
> -JBoss Business P. and Rules D. - OK
> -JBoss Integration and SOA D. - OK
> -JBoss Data Virtualization D. (IS early acess)
> -there is problem with slf4j
> -IS contains Teiid 11.0.1.CR1-v20170117-222 which should be fixed
> -there are error like this:
> {code}
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method
> "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader
> (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class,
> org/slf4j/LoggerFactory, and the class loader
> (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class,
> org/slf4j/impl/StaticLoggerBinder, have different
> Class objects for the type org/slf4j/ILoggerFactory
> used in the signature{code}
> -install everything from Central (including PMD and Findbugs, and early access stuff. NOTE: newer versions of the Integration Stack connectors should already be installed from the step above)
> -I installed everything using Central-Software/update, *no remediation action* was needed.
> -Eclipse started but with many errors. So I have to find out which feature causes the problem.{quote}
> [~nickboldt] said:
> {quote}
> loader constraint violation == two different versions of slf4j in the installed plugins
> check in :~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 vs. in /opt/rh/
> Problem appears to be in *org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory*. {quote}
> [~lvalach] said:
> {quote}
> {code}
> cd ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
> find . -iname *slf4j*
> ./configuration/org.eclipse.osgi/1293/0/.cp/lib/slf4j-api-1.6.1.jar
> {code}
> The output for /opt/rh/ is quite long but I can say that it contains slf4j.api_1.7.4.jar
> {quote}
> So, we may have a conflict between slf4j and slf4j-api, which both use the same bundle names, but expose packages differently.
> Unclear which IS project is causing this problem as I thought we'd fixed both SY and TD already.
> * https://issues.jboss.org/browse/SWITCHYARD-2976
> * https://issues.jboss.org/browse/TEIIDDES-2999
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23567) Integration tests global refactoring
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23567?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23567:
----------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.3.AM2)
> Integration tests global refactoring
> ------------------------------------
>
> Key: JBIDE-23567
> URL: https://issues.jboss.org/browse/JBIDE-23567
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Reporter: Jeff MAURY
> Labels: integration-test, integration_tests
> Fix For: 4.4.3.Final
>
>
> We should done some work on integration tests so that we can rely on them to improve our code quality and reduce the technical debt.
> A sprint will be dedicated.
> Here are the tasks we should work on:
> * run tests from Maven and document how to run them if specific steps are required
> * If failure, fix the failed tests
> * Refactor / move tests to the components repository
> * Fix/make sure tests are run in PR check
> This huge task should be done component per component. Sub-tasks JIRA will be created for each component.
> You can use this document as a starting point:[https://docs.google.com/document/d/1bl8pJ2aW65UpyGpr3qxoAUREDWL26N...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ]
Pavol Srna edited comment on JBIDE-21895 at 2/6/17 5:05 AM:
------------------------------------------------------------
Hi [~adietish], thanks for the above improvements.
I'm not suggesting any changes to the tooling atm, I'm just trying different paths a user may follow and validate them.
What I ment with 'UX is not flawless' is that I see paths that are not clear unless you know openshift internals.
For example - at the beginning I didn't know that I'm about to delete the service. I hit the delete button and the tooling said "You are about to delete the "nodejs" Openshift resource". Could it say "nodejs service"? Maybe?
Then I tried for example this scenario: 1) Scale nodejs pod to 0, delete service. 2) create the same service from template (i know I left some resources behind), but the tooling shows me this window: !os-resources-empty.png|thumbnail!
I know I did something stupid, but looking at the dialogs I'm not sure in which state I'm. Is it an error state? Looks like nothing has been created (which is probably true).
Maybe we should do a Usability testing session and identify problematic places.
was (Author: psrna):
Hi [~adietish], thanks for the above improvements.
I'm not suggesting any changes to the tooling atm, I'm just trying different paths a user may follow and validate them.
What I ment with 'UX is not flawless' is that I see paths that are not clear unless you know openshift internals.
For example - at the beginning I didn't know that I'm about to delete the service. I hit the delete button and the tooling said "You are about to delete the "nodejs" Openshift resource". Could it say "nodejs service"? Maybe?
Then I tried for example this scenario: 1) Scale nodejs pod to 0, delete service. 2) create the same service from template (i know I left some resources behind), but the tooling shows me this window: !os-resources-empty.jpg|thumbnail!
I know I did something stupid, but looking at the dialogs I'm not sure in which state I'm. Is it an error state? Looks like nothing has been created (which is probably true).
Maybe we should do a Usability testing session and identify problematic places.
> Application wizard: Resource name collisions after deleting and recreating the application
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21895
> URL: https://issues.jboss.org/browse/JBIDE-21895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Pavol Srna
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.3.Final
>
> Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png, os-resources-empty.png
>
>
> 1) Create e.g. node application in a openshift project
> 2) Right click from project explorer -> Delete the application
> 3) repeat step 1)
> Result:
> !Screen Shot 2016-03-17 at 16.19.05.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-21895:
------------------------------------
Hi [~adietish], thanks for the above improvements.
I'm not suggesting any changes to the tooling atm, I'm just trying different paths a user may follow and validate them.
What I ment with 'UX is not flawless' is that I see paths that are not clear unless you know openshift internals.
For example - at the beginning I didn't know that I'm about to delete the service. I hit the delete button and the tooling said "You are about to delete the "nodejs" Openshift resource". Could it say "nodejs service"? Maybe?
Then I tried for example this scenario: 1) Scale nodejs pod to 0, delete service. 2) create the same service from template (i know I left some resources behind), but the tooling shows me this window: !os-resources-empty.jpg|thumbnail!
I know I did something stupid, but looking at the dialogs I'm not sure in which state I'm. Is it an error state? Looks like nothing has been created (which is probably true).
Maybe we should do a Usability testing session and identify problematic places.
> Application wizard: Resource name collisions after deleting and recreating the application
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21895
> URL: https://issues.jboss.org/browse/JBIDE-21895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Pavol Srna
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.3.Final
>
> Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png
>
>
> 1) Create e.g. node application in a openshift project
> 2) Right click from project explorer -> Delete the application
> 3) repeat step 1)
> Result:
> !Screen Shot 2016-03-17 at 16.19.05.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-21895:
-------------------------------
Attachment: os-resources-empty.png
> Application wizard: Resource name collisions after deleting and recreating the application
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21895
> URL: https://issues.jboss.org/browse/JBIDE-21895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Pavol Srna
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.3.Final
>
> Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png, os-resources-empty.png
>
>
> 1) Create e.g. node application in a openshift project
> 2) Right click from project explorer -> Delete the application
> 3) repeat step 1)
> Result:
> !Screen Shot 2016-03-17 at 16.19.05.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month