November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16093: ---------------------------------- Priority: Blocker (was: Major) > NPEs when compiling wildfly codebase > ------------------------------------ > > Key: JBIDE-16093 > URL: https://issues.jboss.org/browse/JBIDE-16093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Snjezana Peco > Priority: Blocker > Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png > > > When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian. > !npes-building-wildfly.png! > !npes-building-wildfly-2.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

[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16093: -------------------------------- Priority: Critical (was: Blocker) > NPEs when compiling wildfly codebase > ------------------------------------ > > Key: JBIDE-16093 > URL: https://issues.jboss.org/browse/JBIDE-16093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Snjezana Peco > Priority: Critical > Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png > > > When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian. > !npes-building-wildfly.png! > !npes-building-wildfly-2.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

[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16093: ---------------------------------- Fix Version/s: 4.1.1.CR1 4.2.0.Alpha1 > NPEs when compiling wildfly codebase > ------------------------------------ > > Key: JBIDE-16093 > URL: https://issues.jboss.org/browse/JBIDE-16093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png > > > When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian. > !npes-building-wildfly.png! > !npes-building-wildfly-2.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

[JBoss JIRA] (JBIDE-16056) CLONE - JSF Portlet deployment error on JPP 6

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16056?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16056: --------------------------------------- Max, Will I apply this PR? > CLONE - JSF Portlet deployment error on JPP 6 > --------------------------------------------- > > Key: JBIDE-16056 > URL: https://issues.jboss.org/browse/JBIDE-16056 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Priority: Optional > Labels: respin-a > Fix For: 4.1.1.CR1 > > > Deploying of JSF Portal Project with JSF Portlet ends with error on JPP 6. -- 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-16087) The command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy fails when executed via a cheatsheet

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16087?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16087: ------------------------------------- Snjeza: you'd still need to inject a server or look one up somehow, so the defaultHandler won't be enough by itself > The command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy fails when executed via a cheatsheet > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16087 > URL: https://issues.jboss.org/browse/JBIDE-16087 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Vineet Reynolds > Fix For: 4.2.x > > > When I embed the following command in an Eclipse cheatsheet for JDF-497 : > {noformat} > <command > required="false" > serialization="org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy"/> > {noformat} > it fails with the following error: > {noformat} > !ENTRY org.eclipse.ui.cheatsheets 4 0 2013-11-21 22:50:34.494 > !MESSAGE The command did not complete successfully. > !STACK 0 > org.eclipse.core.commands.NotHandledException: There is no handler to execute for command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:512) > 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.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420) > at org.eclipse.ui.internal.cheatsheets.CommandRunner.executeCommand(CommandRunner.java:81) > at org.eclipse.ui.internal.cheatsheets.data.CheatSheetCommand.execute(CheatSheetCommand.java:44) > at org.eclipse.ui.internal.cheatsheets.views.CoreItem.runExecutable(CoreItem.java:506) > at org.eclipse.ui.internal.cheatsheets.views.CoreItem.runExecutable(CoreItem.java:501) > at org.eclipse.ui.internal.cheatsheets.views.CheatSheetViewer.runPerformExecutable(CheatSheetViewer.java:1046) > at org.eclipse.ui.internal.cheatsheets.views.CoreItem$1.linkActivated(CoreItem.java:89) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) > at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) > at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) > 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:606) > 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) > {noformat} > I'm not sure if this command is available for use in a cheatsheet, but I thought I'd report it. -- 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-16056) CLONE - JSF Portlet deployment error on JPP 6

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16056?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16056: --------------------------------------- The richfaces libraries will be removed/replaced only if a user adds his own richfaces libraries to the JSF Portlet wizard page. > CLONE - JSF Portlet deployment error on JPP 6 > --------------------------------------------- > > Key: JBIDE-16056 > URL: https://issues.jboss.org/browse/JBIDE-16056 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Priority: Optional > Labels: respin-a > Fix For: 4.1.1.CR1 > > > Deploying of JSF Portal Project with JSF Portlet ends with error on JPP 6. -- 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-16056) CLONE - JSF Portlet deployment error on JPP 6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16056?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16056: --------------------------------------------- [~nickboldt] this issue is not a blocker - if [~snjeza] gets it in its fine, if not we will just wait thus start the respin if not ready. > CLONE - JSF Portlet deployment error on JPP 6 > --------------------------------------------- > > Key: JBIDE-16056 > URL: https://issues.jboss.org/browse/JBIDE-16056 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Priority: Optional > Labels: respin-a > Fix For: 4.1.1.CR1 > > > Deploying of JSF Portal Project with JSF Portlet ends with error on JPP 6. -- 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-16056) CLONE - JSF Portlet deployment error on JPP 6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16056?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16056: ---------------------------------------- Priority: Optional (was: Blocker) > CLONE - JSF Portlet deployment error on JPP 6 > --------------------------------------------- > > Key: JBIDE-16056 > URL: https://issues.jboss.org/browse/JBIDE-16056 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Priority: Optional > Labels: respin-a > Fix For: 4.1.1.CR1 > > > Deploying of JSF Portal Project with JSF Portlet ends with error on JPP 6. -- 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-16056) CLONE - JSF Portlet deployment error on JPP 6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16056?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16056: --------------------------------------------- [~snjeza] lets put this in just because it is now there because we have it and its "as bad/good" as we had before. *But* we should create a jira to start winding this feature down and not have to keep maintaining it because there is simple too many moving factors here and removing files in a facet without warnings is just a really bad thing to start doing. Also are you sure the richfaces libraries are not compatible if you use the latest versions from WFK/Seam ? We really should reach out to wfk/richfaces team before doing such changes in tools if it is actually already handled on the runtime side....and if it is nothandled there that incompatbility sounds like a bug we should get reported. > CLONE - JSF Portlet deployment error on JPP 6 > --------------------------------------------- > > Key: JBIDE-16056 > URL: https://issues.jboss.org/browse/JBIDE-16056 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Priority: Blocker > Labels: respin-a > Fix For: 4.1.1.CR1 > > > Deploying of JSF Portal Project with JSF Portlet ends with error on JPP 6. -- 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-16082) Prevent JBoss Tools 4.1 and JBDS 7.x from installing into Luna due to platform/API incompatibilities

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16082?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16082: --------------------------------------------- [~phantomjinx] this change does sound like breaking eclipses api policy thus I suggest you raise it towards the oda project since they simply might have missed that they changed it without proper deprecation instead of removal. > Prevent JBoss Tools 4.1 and JBDS 7.x from installing into Luna due to platform/API incompatibilities > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-16082 > URL: https://issues.jboss.org/browse/JBIDE-16082 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, forge, hibernate, server, testing-tools > Affects Versions: 4.1.1.CR1 > Reporter: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.1.1.CR1 > > > We already know (from JBIDE-15639) that components like Arquillian, Forge, Server, and Hibernate will not compile with Luna dependencies due to the fact that the upstream projects on which they depend have changed in incompatible ways. > Therefore, JBT 4.2 / JBDS 8 is being built to *ONLY work with Luna*. > But the converse should be true, too: we don't want users installing JBT 4.1 / JBDS 7.x onto Luna and ending up with something that *doesn't work*, even if it can be installed that way. > *Solution:* > Update manifest.mf files to PREVENT installing key parts of JBT 4.1 / JBDS 7.x into Luna, so that no user will hit this problem. -- 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 November 2013