[JBoss JIRA] (JBIDE-16512) Some dialogs (and wizards) do not have title bar
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16512?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16512:
-------------------------------------
Summary: Some dialogs (and wizards) do not have title bar (was: OpenShift Shells: Some shells (and wizards) do not have title bar)
> Some dialogs (and wizards) do not have title bar
> ------------------------------------------------
>
> Key: JBIDE-16512
> URL: https://issues.jboss.org/browse/JBIDE-16512
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.2.x
>
>
> On Fedora with GNOME many shells (wizards) do not have Title bar and that's the reason they are not dragable / moveable. Before 4.2.0 there was not almost any of the title bars, but with 4.2.0 there is seen improvement.
> Specifically these shells do not have title bar:
> - Port forwarding (shell opened from application context menu)
> - Edit enviroment variables (shell opened from application context menu)
> - Import application (wizard opened from application context menu)
> - New connection (shell opened from OpenShift explorer view context menu or by click on tool bar button Connect to Openshift)
> - Edit connection (shell opened from context menu of connection)
> - New domain (shell opened from context menu of connection)
> - Edit domain (shell opened from context menu of domain)
> - Manage domains (shell opened from context menu of connection)
> - New application (wizard open from context menu of connection / domain or File - New - OpenShift Application
> Few examples of correct shells:
> - Tail Files (shell opened from application context menu)
> - Details (shell opened from application context menu)
> - Create server adapted (shell opened from application context menu)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17496) Central installation fails if done right after Eclipse start
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17496?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-17496:
----------------------------------------
I could reproduce the "Connector status" dialog and underlying NullPointerExceptions. However, I could not get the error message about Findbugs being not available.
I'll focus on the NPE with this ticket. If you can reproduce the issue with FindBugs, please report that in another Jira.
> Central installation fails if done right after Eclipse start
> ------------------------------------------------------------
>
> Key: JBIDE-17496
> URL: https://issues.jboss.org/browse/JBIDE-17496
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2a B106
> Reporter: Martin Malina
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-b
> Fix For: 4.2.0.Beta2
>
> Attachments: connector-error.png, problems-occurred.png
>
>
> When you try to install something from Central as soon as JBDS starts for the first time, you can get errors.
> I can reproduce some sort of errors every time (I tried 4 or 5 times), but only on a completely fresh install of JBDS/JBT (no central repo data cached).
> It looks like there is a race condition.
> Several times when I tried to install Findbugs, I got:
> {quote}
> The following connectors are not available: FindBugs
> Proceed with the installation anyways?
> {quote}
> Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
> !connector-error.png!
> If I proceed anyway, the install dialog is empty.
> If I click that I don't want to install, I get this:
> {code}
> Problems occurred while performing installation: The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> {code}
> !problems-occurred.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-15635) Null Pointer when code assumes runtime type cannot be null
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15635?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-15635.
---------------------------------
I can't really reproduce any NPE.
I installed Glassfish tools on vanilla Eclipse Kepler SR2. Then I added a Glassfish server & runtime.
Then I used the same workspace with JBDS 8.0.0.Beta2a B106 without installing Glassfish tools.
There are some obvious errors, e.g. when I try to open the server editor, but no NPE.
Feel free to reopen if you still encounter NPEs anywhere.
> Null Pointer when code assumes runtime type cannot be null
> ----------------------------------------------------------
>
> Key: JBIDE-15635
> URL: https://issues.jboss.org/browse/JBIDE-15635
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Mac OSX 10.8.5
> Oracle JDK 1.7.0_40
> JBoss Developer Studio
> Version: 7.0.1.GA
> Build id: GA-v20130930-2238-B7
> Build date: 20130930-2238
> Reporter: Cojan van Ballegooijen
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.Beta2
>
> Attachments: jbosstools-diagnostics-20131008232745.zip, Screen Shot 2013-10-08 at 2.22.05 PM.png
>
>
> - Installed JBoss Developer 7.0.0GA using
> - Upgraded to 7.0.1GA
> - Starting JBoss Developer Studio shows the following error window
> An internal error occurred during: "Refreshing JBoss Tutorials...".
> java.lang.NullPointerException
> - The error mentioned before also occurs when doing a refresh inside JBoss Central in the Start from a sample "portlet"
> - Starting a new Java EE Web project results in the following error
> An error has occurred. See error log for more details.
> java.lang.NullPointerException
> No error log is created in ~/workspace, tried to find *.log file in JBoss Developer Studio installation directory, no log files.
> Found .log in ~/workspace/.metadata
> !SESSION 2013-10-08 16:14:47.792 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_40
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
> Framework arguments: -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -showlocation
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -consoleLog -showlocation
> !ENTRY org.eclipse.core.net 1 0 2013-10-08 16:14:52.252
> !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences
> !ENTRY org.eclipse.jface 2 0 2013-10-08 16:14:52.626
> !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation.
> !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626
> !MESSAGE A conflict occurred for ALT+COMMAND+Z:
> Binding(ALT+COMMAND+Z,
> ParameterizedCommand(Command(org.jboss.tools.cdi.ui.open.namedBean,Open CDI Named Bean,
> Open CDI Named Bean,
> Category(org.eclipse.ui.category.navigate,Navigate,null,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@54158353,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,,system)
> Binding(ALT+COMMAND+Z,
> ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.surround.with.quickMenu,Surround With Quick Menu,
> Shows the Surround With quick menu,
> Category(org.eclipse.jdt.ui.category.source,Source,Java Source Actions,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@5060e945,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,cocoa,system)
> !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626
> !MESSAGE A conflict occurred for COMMAND+SHIFT+F10:
> Binding(COMMAND+SHIFT+F10,
> ParameterizedCommand(Command(org.jboss.tools.common.ui.RegisterAsService,Register As Service,
> Adds class name to META-INF/services/%serviceType% file after service type is selected in the dialog from types extended and implemented by the class.,
> Category(org.eclipse.ui.category.file,File,null,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@a72da3d,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,,system)
> Binding(COMMAND+SHIFT+F10,
> ParameterizedCommand(Command(org.eclipse.ui.window.showSystemMenu,Show System Menu,
> Show the system menu,
> Category(org.eclipse.ui.category.window,Window,null,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7a55e026,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,cocoa,system)
> !ENTRY org.eclipse.core.jobs 4 2 2013-10-08 16:15:04.413
> !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:158)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:248)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130)
> at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:796)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17503) VPE: Visual Preview of VPE is not refreshed when changes to CSS file are saved
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17503?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-17503:
--------------------------------
Assignee: Konstantin Marmalyukov
> VPE: Visual Preview of VPE is not refreshed when changes to CSS file are saved
> ------------------------------------------------------------------------------
>
> Key: JBIDE-17503
> URL: https://issues.jboss.org/browse/JBIDE-17503
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS Beta2-v20140601-0744-B106
> Linux 64bit
> Java Sun JDK 1.7.0_51
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta3
>
>
> Visual Preview of VPE is not refreshed when changes to CSS file are saved.
> 1. Import HTML 5 project from JBoss Central
> 2. Open index.html with JBoss HTML editor
> 3. Open Preview tab of VPE
> 4. Open related screen.css file edit .member-foot class background-color attribute and save
> 5. Open visual part of index.html in VPE
> ERROR: Footer doesn't have updated Footer background color
> 7. Add some changes to source of index.html and save
> ASSERT: Background color of footer is changed in visual part of VPE
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17083) JBIDE-16919 Visual Preview: Navigation from source to view works poorly
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17083?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-17083:
-------------------------------------
{quote}
Lets use prefixes like VPE and Visual Preview for Jiras where it's important to distinguish between these two components WDYT?
{quote}
Great idea. And if issue coupled with both it would be nice to have *VPE / Visual Preview prefix*
> JBIDE-16919 Visual Preview: Navigation from source to view works poorly
> -----------------------------------------------------------------------
>
> Key: JBIDE-17083
> URL: https://issues.jboss.org/browse/JBIDE-17083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta1
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.2.0.Beta2
>
>
> Navigation from source to view works really poorly:
> - selection & scrolling on the visual part very often doesn't work at all;
> - selection & scrolling requires double click (need single click).
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17288) org.jboss.tools.wtp.runtimes.tomcat.tests.TomcatDetectionTest.testTomcatDetection has been failing for 28 builds
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17288?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17288.
---------------------------------
This is now being watched in JBIDE-17468. Closing this JIRA.
> org.jboss.tools.wtp.runtimes.tomcat.tests.TomcatDetectionTest.testTomcatDetection has been failing for 28 builds
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17288
> URL: https://issues.jboss.org/browse/JBIDE-17288
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection, server
> Affects Versions: 4.2.0.Beta2
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.2.0.Beta2
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/493/testReport/org.jboss.tools.wtp.runtimes.tomcat.tests/TomcatDetectionTest/testTomcatDetection/}
> Error Message
> expected:<3> but was:<2>
> Stacktrace
> java.lang.AssertionError: expected:<3> but was:<2>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.jboss.tools.wtp.runtimes.tomcat.tests.TomcatDetectionTest.testTomcatDetection(TomcatDetectionTest.java:64)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:72)
> at java.lang.Thread.run(Thread.java:662)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17083) JBIDE-16919 Visual Preview: Navigation from source to view works poorly
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17083?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-17083:
-------------------------------------
I think it's covered within this issue JBIDE-17454
Would be nice to have separate component but not sure if it really make sense from user point of view it should be the same so I expect that many errors will occur for both components. Lets use prefixes like VPE and Visual Preview for Jiras where it's important to distinguish between these two components WDYT?
> JBIDE-16919 Visual Preview: Navigation from source to view works poorly
> -----------------------------------------------------------------------
>
> Key: JBIDE-17083
> URL: https://issues.jboss.org/browse/JBIDE-17083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta1
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.2.0.Beta2
>
>
> Navigation from source to view works really poorly:
> - selection & scrolling on the visual part very often doesn't work at all;
> - selection & scrolling requires double click (need single click).
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months