February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16307) Update Mylyn tests to run on both Luna and Kepler

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16307?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-16307: ---------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.1.x) > Update Mylyn tests to run on both Luna and Kepler > ------------------------------------------------- > > Key: JBIDE-16307 > URL: https://issues.jboss.org/browse/JBIDE-16307 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.1.x > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.1.2.CR1 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16307) Update Mylyn tests to run on both Luna and Kepler

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16307?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-16307. --------------------------------- Resolution: Done > Update Mylyn tests to run on both Luna and Kepler > ------------------------------------------------- > > Key: JBIDE-16307 > URL: https://issues.jboss.org/browse/JBIDE-16307 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.1.x > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.1.2.CR1 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15623) An icon for "Report error" dialog and menu

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15623?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15623. ------------------------------- Verified with JBT 4.2.0.Alpha1-v20131211-0609-B32 > An icon for "Report error" dialog and menu > ------------------------------------------ > > Key: JBIDE-15623 > URL: https://issues.jboss.org/browse/JBIDE-15623 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Daniel Azarov > Fix For: 4.2.0.Alpha1 > > Attachments: Menu.png, NewMenu.png, NewMenu.png, NewReportProblems.png, ReportProblems.png, ReportProblemWizBan.png, report_problem.png, report_problem.png > > > The "Report Error" menu should have an icon, such as a bug, and something that looks like a small explosion (see http://www.colourbox.com/preview/2953774-167726-pop-art-comic-style-explo... ). This icon should be put in menu, and could also be used in dialog. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15575) Creation of foundation.ui to hold TaskWizard framework

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15575?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15575. ------------------------------- Verified with JBT 4.2.0.Alpha1-v20131211-0609-B32 > Creation of foundation.ui to hold TaskWizard framework > ------------------------------------------------------ > > Key: JBIDE-15575 > URL: https://issues.jboss.org/browse/JBIDE-15575 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Creation of a foundation.ui is required for a few reasons: > 1) runtimes should not depend on common. A foundation.ui is needed for that > 2) Hold taskwizard, a framework from wtp internals which is very very useful and many have expressed interest in using. Runtimes will be using this framework very soon and others will convert in the future. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2730) Faster download of updatesite content via akamai

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2730?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2730: ------------------------------- CDW qa_ack: + (was: ?) > Faster download of updatesite content via akamai > ------------------------------------------------ > > Key: JBDS-2730 > URL: https://issues.jboss.org/browse/JBDS-2730 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, updatesite > Reporter: Burr Sutter > Assignee: Mickael Istria > Fix For: 8.0.x > > > The updatesite used by marketplace should be behind akamai for smoother/faster download. > Investigate using akamai/download.jboss.org backed storage. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15263) Create Datasource Dialog/Wizard usability

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15263?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15263. ------------------------------- Verified with JBT 4.2.0.Alpha1-v20131211-0609-B32 > Create Datasource Dialog/Wizard usability > ----------------------------------------- > > Key: JBIDE-15263 > URL: https://issues.jboss.org/browse/JBIDE-15263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: common/jst/core > Affects Versions: 4.1.0.Beta2 > Reporter: Burr Sutter > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha1 > > Attachments: 2013-07-19_1034.png > > > The current Create Datasource dialog has a few usability "gotchas": > 1) It is located under the "JBoss Tools Web" category - when it is more appropriate to be under the "JBoss Tools" category, closer to the Forge wizards - where you need it. > 2) It defaults to AS5, not AS7 - it should default to EAP6/AS7 > 3) It defaults to register in persistence.xml - it is unclear to me how cleanly this injects into the current persistence.xml provided by the Forge wizards, I tend to uncheck it to be safe - then manually tweak up the persistence.xml to reference the same resource. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15151) NullPointerException reported in Eclipse Error view after using "Materialize Library..." on uninitialized classpath container

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15151?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15151. ------------------------------- Verified with JBT 4.2.0.Alpha1-v20131211-0609-B32 > NullPointerException reported in Eclipse Error view after using "Materialize Library..." on uninitialized classpath container > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15151 > URL: https://issues.jboss.org/browse/JBIDE-15151 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, maven > Reporter: Denis Golovin > Assignee: Fred Bricon > Fix For: 4.2.0.Alpha1 > > Attachments: JBIDE-15363.ogv > > > {code} > org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > Caused by: java.lang.NullPointerException > at org.jboss.tools.common.jdt.ui.buildpath.dialog.MaterializeLibraryDialog.<init>(MaterializeLibraryDialog.java:102) > at org.jboss.tools.common.jdt.ui.buildpath.handlers.MaterializeLibraryHandler.execute(MaterializeLibraryHandler.java:80) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > ... 37 more{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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2890) Correct XCode Bundle ID in Hybrid Mobile Tools (JBDS 8)

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2890?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2890: ------------------------------- CDW qa_ack: + > Correct XCode Bundle ID in Hybrid Mobile Tools (JBDS 8) > ------------------------------------------------------- > > Key: JBDS-2890 > URL: https://issues.jboss.org/browse/JBDS-2890 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 8.0.0.Alpha1 > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 8.0.0.Alpha2 > > > Export to native iOS project is not properly setting the bundle id, which should come from the widget id in the cordova config.xml - this bundle id is critical as iOS needs it to be unique and it your provisioning profiles have to reference it. > See JBIDE-16413 (JBDS 8.0.0) -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16430) NPE when starting LiveReload server

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16430?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-16430: --------------------------------------- @vpakan, I could not reproduce the issue, although I found another source of NPE (JBIDE-16435) Please, let me know if you can reproduce the issue again (on another Linux box) Thanks > NPE when starting LiveReload server > ----------------------------------- > > Key: JBIDE-16430 > URL: https://issues.jboss.org/browse/JBIDE-16430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.2.0.Alpha1 > Environment: Linux 64bit > Java Sun 1.7..0_4_x64 > JBT 4.2.0.Alpha1-v20131211-0609-B32 > eclipse-standard-luna-M5-linux-gtk-x86_64 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.2.0.Alpha2 > > > 1. Create LiveReload server with default values > 2. Start LiveReload server > ERROR: > {noformat} > !ENTRY org.eclipse.wst.server.core 4 0 2014-02-04 10:54:55.290 > !MESSAGE Could not publish to the server. > !STACK 0 > java.lang.NullPointerException > at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3154) > at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53){noformat} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14848) Two "Open CSS Dialog..." actions on toolbar

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14848?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-14848. ----------------------------------- Verified in JBDS 8.0.0 Alpha1-v20131212-0740-B25 > Two "Open CSS Dialog..." actions on toolbar > ------------------------------------------- > > Key: JBIDE-14848 > URL: https://issues.jboss.org/browse/JBIDE-14848 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.1.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.2.0.Alpha1 > > Attachments: OpenCSSDialog1.png, OpenCSSDialog2.png, scr.png > > > JBoss Perspective. Open any *.css file. There are two "Open CSS Dialog..." actions: > !scr.png! -- 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, 5 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 February 2014