November 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2691) Incomplete build path for Spring Web Project when Spring plugins are installed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2691?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2691: ---------------------------------- According to https://issuetracker.springsource.com/browse/STS-3602, which is closed *Won't Fix*, this problem still exists w/ SpringIDE 3.4 (included in JBDS 7.1.0.CR1 version of Central). > Incomplete build path for Spring Web Project when Spring plugins are installed > ------------------------------------------------------------------------------ > > Key: JBDS-2691 > URL: https://issues.jboss.org/browse/JBDS-2691 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies, central, upstream > Affects Versions: 7.0.0.CR1 > Environment: JBDS 7.0.0.CR1a, L64 > Reporter: Jiri Peterka > Assignee: Fred Bricon > Fix For: 8.0.0.GA > > Attachments: build-path-is-incomplete.png > > > Build path is incomplete. Cannot find class file for javax/servlet/ServletContext -- 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-2690) Internal problem when spring project from jboss central is used

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2690?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-2690: ------------------------------------ Jirka - can you retest this with: SpringIDE 3.4 - from Central's CR1 site Thanks! > Internal problem when spring project from jboss central is used > --------------------------------------------------------------- > > Key: JBDS-2690 > URL: https://issues.jboss.org/browse/JBDS-2690 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies, upstream > Affects Versions: 7.0.0.CR1 > Environment: JBDS 7.0.0.CR1a, L64 > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 7.1.x, 8.0.x > > > I have this error when Spring 3.2 or Spring 3.3 is installed: > {code} > java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2521) > at java.lang.Class.getDeclaredMethods(Class.java:1845) > at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:159) > at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:106) > at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:87) > at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:257) > at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:73) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:748) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:741) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:625) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:584) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:450) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 23 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] (JBIDE-10861) "use existing" project is not setting selection based on current selection for start of wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10861?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-10861: ----------------------------------- Assignee: Fred Bricon (was: Xavier Coulon) > "use existing" project is not setting selection based on current selection for start of wizard > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-10861 > URL: https://issues.jboss.org/browse/JBIDE-10861 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.2.0.Alpha1 > > > rght click existing project -> new openshift app -> type in details, on the project config page that existing project should be preselected when "unchecking" create new project.. -- 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-10861) "use existing" project is not setting selection based on current selection for start of wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10861?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-10861: -------------------------------- Fix Version/s: 4.1.1.CR1 (was: 4.2.0.Alpha1) > "use existing" project is not setting selection based on current selection for start of wizard > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-10861 > URL: https://issues.jboss.org/browse/JBIDE-10861 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.1.1.CR1 > > > rght click existing project -> new openshift app -> type in details, on the project config page that existing project should be preselected when "unchecking" create new project.. -- 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16082?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16082: ---------------------------------------- The general approach for those issues is that those components specify a version range that excludes the Luna version and higher in their MANIFEST.MF. > 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

[JBoss JIRA] (JBIDE-12274) BrowserSim borks on jquery mobile (RHEL 6.1)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12274?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated JBIDE-12274: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=966571, https://bugzilla.redhat.com/show_bug.cgi?id=1033151 > BrowserSim borks on jquery mobile (RHEL 6.1) > -------------------------------------------- > > Key: JBIDE-12274 > URL: https://issues.jboss.org/browse/JBIDE-12274 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 3.3.0.CR1 > Environment: RHEL 6.1 > JBoss Developer Studio 5.0.0.CR1 > Reporter: Gabriel De Repentigny > Assignee: Yahor Radtsevich > Labels: upstream > Fix For: 4.0.0.Alpha1, 4.1.x > > Attachments: jQMrefsRemoved.png, midori-browsersim.png, midori-browsersim.png, python-tabbed-browser.png, Screenshot-BrowserSim .png, windows-7_Safari-5.1.2-7534.52.7.png > > > I'm walking through the JBoss Way Ticket Monster lab. JDS's BrowserSim borks while trying to render mobile.html (pasted below) which is part of the tutorial. > The problem seems to be with the jquery mobile js file. If you take that include out, it renders (sans-mobile styling). > {code:xml} > <!DOCTYPE html> > <html> > <head> > <title>jQuery Mobile Template</title> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> > <meta name="viewport" content="width=device-width, initial-scale=1" /> > <link rel="stylesheet" > href="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.css" /> > <script type="text/javascript" > src="http://code.jquery.com/jquery-1.7.1.min.js"></script> > <script type="text/javascript" > src="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.js"></script> > <script type="text/javascript"> > $(document).on("pageinit", "#page1", function(event){ > alert("Ready To Go"); > }); > $.getJSON("rest/events", function(events) { > // console.log("returned are " + results); > var listOfEvents = $("#listOfItems"); > listOfEvents.empty(); > $.each(events, function(index, event) { > // console.log(event.name); > listOfEvents.append("<li><a href=’#’>" + event.name + "</a>"); > }); > listOfEvents.listview("refresh"); > }); > </script> > </head> > <body> > <div data-role="page" id="page1"> > <div data-role="header"> > <h1>jQuery Mobile</h1> > </div> > <div data-role="content"> > <ul id="listOfItems" data-role="listview" data-inset="true" > data-filter="true"> > <li><a href="">One</a></li> > <li><a href="">Two</a></li> > <li><a href="">Three</a></li> > </ul> > </div> > <div data-role="footer"> > <h4>www.jboss.org/developer</h4> > </div> > </div> > </body> > </html> > {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] (JBIDE-16032) java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16032?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-16032: ------------------------------------------- Assignee: Koen Aers (was: Max Rydahl Andersen) looks simple enough. +1 info: you don't need to null check when also doing instanceof. http://stackoverflow.com/questions/2950319/is-null-check-needed-before-ca... > java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences > --------------------------------------------------------------------- > > Key: JBIDE-16032 > URL: https://issues.jboss.org/browse/JBIDE-16032 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Labels: respin-a > Fix For: 4.1.1.CR1 > > Attachments: forge-preferences.png > > > Stacktrace: > {code} > java.lang.ArrayIndexOutOfBoundsException: 0 > at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage$6.run(ForgeInstallationsPreferencePage.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage.performOk(ForgeInstallationsPreferencePage.java:290) > at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:965) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) > at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:945) > at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:448) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:171) > at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233) > 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.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.jface.window.Window.runEventLoop(Window.java:826) > at org.eclipse.jface.window.Window.open(Window.java:802) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) > at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > 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) > {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] (JBIDE-16082) Prevent JBoss Tools 4.1 and JBDS 7.x from installing into Luna due to platform/API incompatibilities

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16082?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16082: ------------------------------- Description: 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. was: We already know that components like Arquillian, Forge, Server, and Hibernate will 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 will 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. *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. > 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

[JBoss JIRA] (JBIDE-16085) Prevent Server in JBT 4.1 from installing into Luna due to platform/API incompatibilities

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16085?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16085: ------------------------------- Component/s: server (was: hibernate) > Prevent Server in JBT 4.1 from installing into Luna due to platform/API incompatibilities > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16085 > URL: https://issues.jboss.org/browse/JBIDE-16085 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.1.1.CR1 > Reporter: Nick Boldt > Labels: respin-a > Fix For: 4.1.1.CR1 > > > See JBIDE-16082. Need to prevent this component from installing into Luna since it's not compatible / requires platform/API deps that have changed. -- 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-16086) Prevent Arquillian in JBT 4.1 from installing into Luna due to platform/API incompatibilities

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-16086: ---------------------------------- Summary: Prevent Arquillian in JBT 4.1 from installing into Luna due to platform/API incompatibilities Key: JBIDE-16086 URL: https://issues.jboss.org/browse/JBIDE-16086 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Affects Versions: 4.1.1.CR1 Reporter: Nick Boldt Fix For: 4.1.1.CR1 See JBIDE-16082. Need to prevent this component from installing into Luna since it's not compatible / requires platform/API deps that have changed. -- 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