June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14803) eclipse CSS outling resulting in Null pointer exception

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14803?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14803: --------------------------------------------- its hard to reproduce. I think it was on M7 yes. > eclipse CSS outling resulting in Null pointer exception > ------------------------------------------------------- > > Key: JBIDE-14803 > URL: https://issues.jboss.org/browse/JBIDE-14803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Reporter: Max Rydahl Andersen > > EXECUTE: open screen.css from kitchensink mobile. > EXECUTE: double click on #members.row in outline > asssert: screen.css editor higlights members.row > what happens: multiple errors + dialogs logged with: > java.lang.NullPointerException > at org.eclipse.wst.sse.ui.internal.contentoutline.ConfigurableContentOutlinePage$5.getShowInContext(ConfigurableContentOutlinePage.java:444) > at org.eclipse.ui.internal.services.WorkbenchSourceProvider.getContext(WorkbenchSourceProvider.java:418) > at org.eclipse.ui.internal.services.WorkbenchSourceProvider.updateActivePart(WorkbenchSourceProvider.java:484) > at org.eclipse.ui.internal.services.WorkbenchSourceProvider.updateActivePart(WorkbenchSourceProvider.java:445) > at org.eclipse.ui.internal.services.WorkbenchSourceProvider.getCurrentState(WorkbenchSourceProvider.java:134) > at org.eclipse.ui.internal.services.WorkbenchSourceProvider$6.handleEvent(WorkbenchSourceProvider.java:684) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1080) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4163) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1470) > at org.eclipse.swt.widgets.Shell.windowDidBecomeKey(Shell.java:2157) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5602) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:214) > at org.eclipse.swt.widgets.Widget.becomeKeyWindow(Widget.java:366) > at org.eclipse.swt.widgets.Shell.becomeKeyWindow(Shell.java:523) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5426) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSWindow.close(NSWindow.java:54) > at org.eclipse.swt.widgets.Shell.destroyWidget(Shell.java:797) > at org.eclipse.swt.widgets.Widget.release(Widget.java:1318) > at org.eclipse.swt.widgets.Control.release(Control.java:2848) > at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671) > at org.eclipse.jface.window.Window.close(Window.java:336) > at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:994) > at org.eclipse.ui.internal.statushandlers.InternalDialog.close(InternalDialog.java:710) > at org.eclipse.jface.dialogs.Dialog.okPressed(Dialog.java:955) > at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476) > at org.eclipse.ui.internal.statushandlers.InternalDialog.buttonPressed(InternalDialog.java:190) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4164) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4010) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3649) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > 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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > 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) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2636) rebrand devstudio.jboss.com pages with "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2636?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2636: ------------------------------------------- [~nickboldt] that is not the approved font nor can we use the red hat shadow man logo like that. lets not update that without help from brand/design team. > rebrand devstudio.jboss.com pages with "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-2636 > URL: https://issues.jboss.org/browse/JBDS-2636 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: updatesite > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 7.0.0.Beta2 > > > New requirement from MW management. Rebrand the pages to state "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio". > Similar changes should happen on jboss.org/tools pages which mention JBDS as well. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14791) cannot rename deployed modules in AS7 server adapter

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14791?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14791: --------------------------------------------- [~rob.stryker] that workflow is horribly complex for a basic rename. why can't we just fix it or at least put some info in the editor that you need to undeploy before being able to rename. > cannot rename deployed modules in AS7 server adapter > ---------------------------------------------------- > > Key: JBIDE-14791 > URL: https://issues.jboss.org/browse/JBIDE-14791 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.0.Beta2 > > Attachments: deployments-greyed-out.png > > > The as7 server adapter seem not to allow one to rename deployed modules. > i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in / -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14791) cannot rename deployed modules in AS7 server adapter

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14791?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14791: ---------------------------------------- Assignee: Rob Stryker (was: Max Rydahl Andersen) > cannot rename deployed modules in AS7 server adapter > ---------------------------------------------------- > > Key: JBIDE-14791 > URL: https://issues.jboss.org/browse/JBIDE-14791 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.0.Beta2 > > Attachments: deployments-greyed-out.png > > > The as7 server adapter seem not to allow one to rename deployed modules. > i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in / -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14079) Weinre in browsersim slow/not-informative

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14079?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14079: --------------------------------------------- nothing to do with holywars - even if we had locally running weinre the default, switching to a remote one (for allowing remote connections) it would still be good to not have it show up with blank white page. > Weinre in browsersim slow/not-informative > ----------------------------------------- > > Key: JBIDE-14079 > URL: https://issues.jboss.org/browse/JBIDE-14079 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Priority: Minor > Fix For: 4.1.0.Beta2 > > > BrowerSim weinre seems to load *very* slowly and there is just a big white dialog shown while it do so. > I initially thought it was broken but after 4-5 attempts it suddenly showed up. > Problem is users has no idea what is actually going on. > Could we: > A) show a progress monitor (even a fake one would be useful) > B) show what url the dialog is visiting (that gives a hint it is waiting) > C) have a link/info button explaining you can configure weinre in preferences > Ca) have a dialog pop up on initial start of weinre explaining it will inject weinre and go to client url X which can be configured in the preferences...and then a "Do not ask me again" checkbox for future usage. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14294) Make it easy to start using livereload

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14294?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-14294: --------------------------------------- With regards with what has beeb done so far, the simplest options is to create/start the LiveReload server if it is missing or stopped (with a dialog to confirm) when the user wants to open a file or a server module with LR Also, if she wants to use QR Code (assuming she wants to try with a real device), warn her that Remote Connection will be enabled (if disabled) > Make it easy to start using livereload > -------------------------------------- > > Key: JBIDE-14294 > URL: https://issues.jboss.org/browse/JBIDE-14294 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.1.0.Beta2 > > > We need to find a good way to have livereload enabled without too much manual configuration. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14763) GateIn 3.6 goes to stacks.yaml

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14763?page=com.atlassian.jira.plugi... ] Peter Palaga commented on JBIDE-14763: -------------------------------------- Hi Rob and Max, please see my proposal here: https://github.com/ppalaga/jdf-stack/tree/JDF-367 I have not sent a PR yet, I am waiting for a green light from you. Esp. I was not sure how I should set runtime-type here https://github.com/ppalaga/jdf-stack/blob/JDF-367/stacks.yaml#L1514 and wtp-runtime-type here https://github.com/ppalaga/jdf-stack/blob/JDF-367/stacks.yaml#L1516 > GateIn 3.6 goes to stacks.yaml > ------------------------------ > > Key: JBIDE-14763 > URL: https://issues.jboss.org/browse/JBIDE-14763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, server > Reporter: Peter Palaga > Assignee: Rob Stryker > Priority: Blocker > > It should be checked which consequences will it have for JBoss Tools if GateIn 3.6 appears in {{stacks.yaml}}. Filling this as recommended by [~maxandersen]. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14616) Remove <relativePath/> to parent pom

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14616?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-14616: ------------------------------------------ https://github.com/jbosstools/jbosstools-xulrunner/pull/7 applied in jbosstools-xulrunner/master https://github.com/jbosstools/jbosstools-vpe/pull/100 applied in jbosstools-vpe/master > Remove <relativePath/> to parent pom > ------------------------------------ > > Key: JBIDE-14616 > URL: https://issues.jboss.org/browse/JBIDE-14616 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Beta2 > > > Having a relativePath to parent pom in each component makes that often, on development machine, build resolves parent pom to the relative one (which my not be correctly sync'd) instead of the one which is published on Nexus. > This introduce confusion and may result in different build output between CI and local. Therefore, we should remove the <relativePath/> from all components. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14837) seam tools needs to use new downloadRuntimeProvider extension point

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14837?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-14837: ------------------------------------- I'd just like to note that I built it locally and it works with no errors. > seam tools needs to use new downloadRuntimeProvider extension point > ------------------------------------------------------------------- > > Key: JBIDE-14837 > URL: https://issues.jboss.org/browse/JBIDE-14837 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: Seam 2 > Affects Versions: 4.1.0.Beta2 > Reporter: Rob Stryker > Assignee: Denis Golovin > Fix For: 4.1.0.Beta2 > > > Seam tools is still using deprecated downloadRuntime extension point instead of impl which pulls from stacks. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14842) Include optional dependencies in pom.xml at surefire level

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-14842: ------------------------------------- Summary: Include optional dependencies in pom.xml at surefire level Key: JBIDE-14842 URL: https://issues.jboss.org/browse/JBIDE-14842 Project: Tools (JBoss Tools) Issue Type: Task Components: Webservices Affects Versions: 4.1.0.Beta1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.1.0.CR1 running tests during a tycho build on MacOSX requires an optional/platform specific bundle (o.e.jdt.launching.macosx) that is currently defined in a profile. Problem is that this profile includes *all* optional dependencies, not only this one, while other profiles (ie, platform) include no optional dependency at all. Solution: configure this optional dependency at the surefire level and for macosx only -- 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, 10 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 June 2013