May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14638) Freezing Behavior in ECFTransport locks Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14638?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-14638: ------------------------------------- * Go offline. * Open central * Close central immediately Randomly (maybe 20% of the time), one update job (buzz or tutorial) will be stuck, blocking Eclipse (See JBIDE-14593): !https://issues.jboss.org/secure/attachment/12362695/12362695_scr.png! > Freezing Behavior in ECFTransport locks Central > ----------------------------------------------- > > Key: JBIDE-14638 > URL: https://issues.jboss.org/browse/JBIDE-14638 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.1.0.Beta1 > > > Regression in behavior causes lockup of eclipse and inability to shut down. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14547) Page is refreshed only after first change is saved

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14547?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-14547. ------------------------------- Verified with JBDS 7.0.0 Beta1-v20130526-0839-B241 > Page is refreshed only after first change is saved > -------------------------------------------------- > > Key: JBIDE-14547 > URL: https://issues.jboss.org/browse/JBIDE-14547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Beta1 > Environment: Linux 64bit, JBDS 7.0.0 Beta1-v20130519-0601-B206 Java Sun JDK 1.6 > mmurray used Java 1.7.0_13 > Reporter: Vlado Pakan > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: respin-a > Fix For: 4.1.0.Beta1 > > Attachments: liveReload.ogg > > > 1. Import HTML5 Project via JBoss Central > 2. Create test.html page in this project > 3. Open test.html page in JBDS and in Chrome with LiveReload extension installed > 4. Add and start LiveReolad server in JBDS > 5. Enable LiveReload in Chrome > ASSERT: LiveReload is connected in Chrome > 6. Make changes to test.html and save them > ASSERT: Changes are displayed in Chrome > 7. Make another changes to test.html and save them > ERROR: No changes displayed in Chrome > 8. Restart LiveReload Server > 9. Make another changes to test.html and save them > ASSERT: Changes are displayed in Chrome > 10. Make another changes to test.html and save them > ERROR: No changes displayed in Chrome -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14599) <!doctype html> vs <!DOCTYPE html>

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14599?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-14599. ------------------------------- Verified with JBDS 7.0.0 Beta1-v20130526-0839-B241 > <!doctype html> vs <!DOCTYPE html> > ---------------------------------- > > Key: JBIDE-14599 > URL: https://issues.jboss.org/browse/JBIDE-14599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Burr Sutter > Assignee: Alexey Kazakov > Priority: Critical > Labels: respin-a > Fix For: 4.1.0.Beta1 > > > The lowercase version of <!doctype html> does not enable/display the jQuery Mobile Palette while the uppercase version does. > It would appear that "doctype" is case insensitive > http://www.w3.org/html/wg/drafts/html/master/syntax.html#the-doctype > What is the more correct thing to do here? > At this time, the html5 scaffold generates the lowercase version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14638) Freezing Behavior in ECFTransport locks Central

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14638?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-14638: ------------------------------------- Could you verify and close this Jira or provide steps to verify please. > Freezing Behavior in ECFTransport locks Central > ----------------------------------------------- > > Key: JBIDE-14638 > URL: https://issues.jboss.org/browse/JBIDE-14638 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.1.0.Beta1 > > > Regression in behavior causes lockup of eclipse and inability to shut down. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14538) BrowserSim/HTML Editor - JQueryMobileHyperlinkDetectorTest JUnit fails

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14538?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-14538. ------------------------------- Verified on Jenkins > BrowserSim/HTML Editor - JQueryMobileHyperlinkDetectorTest JUnit fails > ---------------------------------------------------------------------- > > Key: JBIDE-14538 > URL: https://issues.jboss.org/browse/JBIDE-14538 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Beta1 > Reporter: Yahor Radtsevich > Assignee: Daniel Azarov > Labels: respin-a > Fix For: 4.1.0.Beta1 > > > https://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.1.keple... > org.jboss.tools.test.util.ProjectImportTestSetup.org.jboss.tools.vpe.browsersim.eclipse.test.JQueryMobileHyperlinkDetectorTest > {code} > java.lang.NullPointerException > at org.eclipse.core.internal.runtime.Activator.getURLConverter(Activator.java:321) > at org.eclipse.core.runtime.FileLocator.resolve(FileLocator.java:227) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:84) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:70) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:61) > at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:213) > at org.jboss.tools.test.util.ProjectImportTestSetup.importProjects(ProjectImportTestSetup.java:57) > at org.jboss.tools.test.util.ProjectImportTestSetup.setUp(ProjectImportTestSetup.java:77) > at junit.extensions.TestSetup$1.protect(TestSetup.java:22) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) > 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:85) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3692) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > 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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14549) Deploying archive via drag&drop triggers server start

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14549?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič edited comment on JBIDE-14549 at 5/27/13 5:21 AM: -------------------------------------------------------------------- Rob, and why when I drag & drop e.g dynamic web project into the servers view, server's start is not initiated? was (Author: jjankovi): Rob, and why when I drag & drop e.g dynamic web project into the servers view, start's server is not initiated? > Deploying archive via drag&drop triggers server start > ----------------------------------------------------- > > Key: JBIDE-14549 > URL: https://issues.jboss.org/browse/JBIDE-14549 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.0.Beta2 > > > If archive is deployed with Publish dialog, server is (correctly) not started. However, drag&drop archive under server in servers view cause server starting. > There is another bug. When user wants to drag&drop whole project into the server, server's starting process is also initiated, but should be not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14549) Deploying archive via drag&drop triggers server start

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14549?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-14549. --------------------------------- Resolution: Rejected The drag-and-drop into the servers view is now, and alwyas has been, a way of invoking the 'run on server' action. This involves starting the server. This is not a bug. This is by design, and it is an upstream decision. > Deploying archive via drag&drop triggers server start > ----------------------------------------------------- > > Key: JBIDE-14549 > URL: https://issues.jboss.org/browse/JBIDE-14549 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.0.Beta2 > > > If archive is deployed with Publish dialog, server is (correctly) not started. However, drag&drop archive under server in servers view cause server starting. > There is another bug. When user wants to drag&drop whole project into the server, server's starting process is also initiated, but should be not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14619) Server's editor is horizontally scrolled back

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14619?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-14619: ------------------------------------- I've been trying to figure out this bug for about 2 years now ;) I've experienced basically EVERY day, and I have NEVER been able to find a solution. So, this bug is basically a help-wanted situation. > Server's editor is horizontally scrolled back > ---------------------------------------------- > > Key: JBIDE-14619 > URL: https://issues.jboss.org/browse/JBIDE-14619 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.0.Beta2 > > > When server's editor doesn't fit to one window (e.g Runtime Environment name is too long) there is a horizontal scroll at the bottom for user to be able to manage all provided configuration settings. > When I move to the right part of editor and click on any widget (text, combobox ...) editor is scrolled back to the initial view. > This is happening only for the first time after editor's opening. > Reproducing steps are captured in [screencast|http://www.youtube.com/watch?v=Kzy_2le2ivg&feature=youtu.be] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14648) Portal Examples - JPP/GateIn requirement is fulfilled after adding EAP runtime

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-14648: ---------------------------------------- Summary: Portal Examples - JPP/GateIn requirement is fulfilled after adding EAP runtime Key: JBIDE-14648 URL: https://issues.jboss.org/browse/JBIDE-14648 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.1.0.Beta1 Reporter: Rastislav Wagner Assignee: Peter Palaga Fix For: 4.1.0.Beta2 All portal examples (enterprise and community ones) have requirement to GateIn or JPP runtime. After adding EAP runtime, GateIn/JPP runtime is fulfilled which is wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14619) Server's editor is horizontally scrolled back

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14619?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-14619: -------------------------------- Fix Version/s: LATER (was: 4.1.0.Beta2) > Server's editor is horizontally scrolled back > ---------------------------------------------- > > Key: JBIDE-14619 > URL: https://issues.jboss.org/browse/JBIDE-14619 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: LATER > > > When server's editor doesn't fit to one window (e.g Runtime Environment name is too long) there is a horizontal scroll at the bottom for user to be able to manage all provided configuration settings. > When I move to the right part of editor and click on any widget (text, combobox ...) editor is scrolled back to the initial view. > This is happening only for the first time after editor's opening. > Reproducing steps are captured in [screencast|http://www.youtube.com/watch?v=Kzy_2le2ivg&feature=youtu.be] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2013