September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18128: --------------------------------------------- You haven't said what is not working - for me the deployment look complete and the jsp is working. How do I trigger the class not found exception ? I'm not changing anything in this - I'm just using maven import on the project. I'm testing with latest nightly yes. > Jboss Eclipse Luna plugin doesn't deploy all .class > --------------------------------------------------- > > Key: JBIDE-18128 > URL: https://issues.jboss.org/browse/JBIDE-18128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > Attachments: 2014-09-04 error.png, 2014-09-04 output.txt, jboss-test.zip, TestJboss-2014-09-03.zip > > > The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException. > I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random. > For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean > As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1. > I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18268) Error while validating credentials in download EAP 6.3 dialog

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18268?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-18268: ------------------------------------ Summary: Error while validating credentials in download EAP 6.3 dialog (was: Error while validating credentials in Download Runtime dialog) > Error while validating credentials in download EAP 6.3 dialog > ------------------------------------------------------------- > > Key: JBIDE-18268 > URL: https://issues.jboss.org/browse/JBIDE-18268 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.CR1 > > > After validation of valid credentials, the following error message appears > {code} > " An error occurred while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 404" > {code} > I was able to reproduce this issue only with one of mine jboss.org accounts. > It looks like a regression of [https://issues.jboss.org/browse/JBIDE-17453|JBIDE-17453] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18260) cannot open properties pages for a launch because of tern NPE'ing

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18260?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18260: --------------------------------------------- Yeah this is pretty critical - not being able to see what ones launch is actually doing is pretty crucial. [~vrubezhny] looking at the PR this seem to fix the NPE, but why is tern properties even activated on a launch configuration ? Should that not be fixed too ? > cannot open properties pages for a launch because of tern NPE'ing > ----------------------------------------------------------------- > > Key: JBIDE-18260 > URL: https://issues.jboss.org/browse/JBIDE-18260 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.2.0.CR1 > > > I launch JBoss, then go under Debug to find the process to see the parameters and I get a blank page saying there are invalid values. > In error log is this: > {code} > java.lang.NullPointerException > at tern.eclipse.ide.ui.properties.TernModulesPropertyPage.createContents(TernModulesPropertyPage.java:62) > at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:233) > at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1537) > at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:1289) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178) > at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1281) > at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:699) > at org.eclipse.jface.preference.PreferenceDialog$9$1.run(PreferenceDialog.java:730) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:725) > at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178) > at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873) > at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1708) > at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1093) > at org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1083) > at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:757) > at org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:390) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:385) > at org.eclipse.jface.window.Window.create(Window.java:435) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101) > at org.eclipse.ui.internal.dialogs.PropertyDialog.createDialogOn(PropertyDialog.java:83) > at org.eclipse.ui.dialogs.PropertyDialogAction.createDialog(PropertyDialogAction.java:177) > at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:519) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > 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:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18268) Error while validating credentials in Download Runtime dialog

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-18268: --------------------------------------- Summary: Error while validating credentials in Download Runtime dialog Key: JBIDE-18268 URL: https://issues.jboss.org/browse/JBIDE-18268 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.2.0.CR1 Reporter: Radoslav Rábara Priority: Blocker Fix For: 4.2.0.CR1 After validation of valid credentials, the following error message appears {code} " An error occurred while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 404" {code} I was able to reproduce this issue only with one of mine jboss.org accounts. It looks like a regression of [https://issues.jboss.org/browse/JBIDE-17453|JBIDE-17453] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18256) Missing quickfixes for HttpMethod without Target and Retention annotations

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18256?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18256: ---------------------------------- Issue Type: Bug (was: Feature Request) > Missing quickfixes for HttpMethod without Target and Retention annotations > -------------------------------------------------------------------------- > > Key: JBIDE-18256 > URL: https://issues.jboss.org/browse/JBIDE-18256 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Labels: respin-a > Fix For: 4.2.0.CR1 > > Attachments: JBIDE-18256.jpg > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18256) Missing quickfixes for HttpMethod without Target and Retention annotations

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18256?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18256: ---------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.3.0.Alpha1) (was: 4.2.1.Final) > Missing quickfixes for HttpMethod without Target and Retention annotations > -------------------------------------------------------------------------- > > Key: JBIDE-18256 > URL: https://issues.jboss.org/browse/JBIDE-18256 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Labels: respin-a > Fix For: 4.2.0.CR1 > > Attachments: JBIDE-18256.jpg > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-293) Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-293?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-293: ------------------------------------------- awesome! > Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters > ----------------------------------------------------------------------------------------------------- > > Key: JBTIS-293 > URL: https://issues.jboss.org/browse/JBTIS-293 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Affects Versions: 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.2.0.Alpha2, 8.0.0.Alpha2 > > > If I run eclipse/jbdevstudio -clean (purging the OSGi cache) I don't get this error. > SESSION 2014-07-30 09:22:59.386 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.7.0_60-ea > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > !ENTRY org.fusesource.ide.branding 4 0 2014-07-30 09:23:05.987 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.branding [975] > Unresolved requirement: Require-Bundle: org.fusesource.ide.camel.model > -> Bundle-SymbolicName: org.fusesource.ide.camel.model; bundle-version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true" > org.fusesource.ide.camel.model [977] > No resolution report for the bundle. Bundle was not resolved because of a uses contraint violation. > org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] because it is exposed to package 'javax.xml.bind.annotation.adapters' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains. > Chain 1: > org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] > require: (osgi.wiring.bundle=org.eclipse.core.runtime) > | > provide: osgi.wiring.bundle: org.eclipse.core.runtime > org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"] > Chain 2: > org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] > import: (osgi.wiring.package=org.fusesource.camel.tooling.util) > | > export: osgi.wiring.package=org.fusesource.camel.tooling.util; uses:=org.apache.camel.model > io.fabric8.camel-tooling-util [osgi.identity; osgi.identity="io.fabric8.camel-tooling-util"; type="osgi.bundle"; version:Version="1.0.0.redhat-379"] > import: (&(osgi.wiring.package=org.apache.camel.model)(&(version>=2.12.0)(!(version>=3.0.0)))) > | > export: osgi.wiring.package=org.apache.camel.model; uses:=javax.xml.bind.annotation.adapters > org.apache.camel.camel-core [osgi.identity; osgi.identity="org.apache.camel.camel-core"; type="osgi.bundle"; version:Version="2.12.0.redhat-610379"] > import: (osgi.wiring.package=javax.xml.bind.annotation.adapters) > | > export: osgi.wiring.package: javax.xml.bind.annotation.adapters > javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] > at org.eclipse.osgi.container.Module.start(Module.java:434) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17260) Review what we track via usage component

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17260?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-17260. ------------------------------ I made myself a list of what was added in 4.2.0. Hope it's complete: Immediately reported events: server creation server - new - <servername> server creation via runtime detection server - detect - <servername> install from central centra - install - <name> forge forge - start - <version> examples examples - create - <exampleName> Daily reported events: VPE editor vpe - editor - <source | visual-vpe | visual-vpv> VPE preview vpe - preview - open VPE browsersim vpe - browsersim - <javafx | webkit> wizard finish (for example new package wizard) jbt - finishWizard - <wizardName> cordovasim aerogear - cordovasim - <javafx | webkit> ws tester ws - wstester - <method> > Review what we track via usage component > ---------------------------------------- > > Key: JBIDE-17260 > URL: https://issues.jboss.org/browse/JBIDE-17260 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: usage > Reporter: Alexey Kazakov > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.0.CR1 > > > We have introduced a few new events in JBT 4.2.0.Beta1 (server creation, central downloading) and a generic tracker of all used wizards in 4.2.0.Beta2. We should review if data collected is useful/too much/too little. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18249) Missing icon for AngularJS on Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18249?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18249: --------------------------------------------- +1 and just to say for GA this kind of thing is critical. polish matters. > Missing icon for AngularJS on Central > ------------------------------------- > > Key: JBIDE-18249 > URL: https://issues.jboss.org/browse/JBIDE-18249 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.2.0.CR1 > Reporter: Mickael Istria > Assignee: Denis Golovin > Labels: respin-a > Fix For: 4.2.0.CR1 > > > AngulaJS connector on Central is missing its icon. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17670) Web Service Tester: JAX-WS request doesn't contain definition of SOAPAction

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17670?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17670: --------------------------------------------- Sorry - I missed the call out to me ;/ I'm not a WS expert but as I read it there is no way of fixing this reliably when running on Java 7 but it works when running Java 6 or Java 8, correct ? If that is the case then I would say because we are days away from closing CR1 now is not the time to have "fun" adding dynamic loading of JAX-WS library when running on Java 7 but not on others or similar trickery and thus for JBDS 8 say users can use Java 8 to run this and we can look at fixing this in a update after JBDS 8 is released - BUT: Do we know that running with Java 8 actually fixes the issue ? And does this affect *all* soa-p interactions ? Is java 7 that broken it cannot do any soa-p calls ? > Web Service Tester: JAX-WS request doesn't contain definition of SOAPAction > --------------------------------------------------------------------------- > > Key: JBIDE-17670 > URL: https://issues.jboss.org/browse/JBIDE-17670 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Priority: Critical > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 September 2014