June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22178) [thym] Installed plugins don't show up in Config Editor UI

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22178?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22178: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > [thym] Installed plugins don't show up in Config Editor UI > ---------------------------------------------------------- > > Key: JBIDE-22178 > URL: https://issues.jboss.org/browse/JBIDE-22178 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Angel Misevski > Fix For: 4.4.x > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=491757 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22508) compile failed in org.jboss.tools.wtp.server.launchbar

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22508?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22508: ----------------------------------- Component/s: target-platform > compile failed in org.jboss.tools.wtp.server.launchbar > -------------------------------------------------------- > > Key: JBIDE-22508 > URL: https://issues.jboss.org/browse/JBIDE-22508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > {code} > 02:32:22 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.25.0:compile (default-compile) on project org.jboss.tools.wtp.server.launchbar: Compilation failure: Compilation failure: > 02:32:22 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/wtp/plugins/org.jboss.tools.wtp.server.launchbar/src/org/jboss/tools/wtp/server/launchbar/ModuleObjectProvider.java:[325] > 02:32:22 [ERROR] boolean enabled = store.getBoolean(Activator.PREF_ENABLE_LAUNCHBAR); > 02:32:22 [ERROR] ^^^^^^^^^^^^^^^^^^^^^ > 02:32:22 [ERROR] PREF_ENABLE_LAUNCHBAR cannot be resolved or is not a field > {code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22508) compile failed in org.jboss.tools.wtp.server.launchbar

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22508?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22508: ---------------------------------------- We need to update our TP to include this new plugin. We should include at least org.eclipse.launchbar feature ( https://git.eclipse.org/c/cdt/org.eclipse.launchbar.git/tree/features) instead of selected plugins: {code} <unit id="org.eclipse.launchbar.core" version="2.0.0.201605241457"/> <unit id="org.eclipse.launchbar.ui" version="2.0.0.201605241457"/> {code} Not sure aboute org.eclipse.launchbar.remote. [~rob.stryker]? > compile failed in org.jboss.tools.wtp.server.launchbar > -------------------------------------------------------- > > Key: JBIDE-22508 > URL: https://issues.jboss.org/browse/JBIDE-22508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > {code} > 02:32:22 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.25.0:compile (default-compile) on project org.jboss.tools.wtp.server.launchbar: Compilation failure: Compilation failure: > 02:32:22 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/wtp/plugins/org.jboss.tools.wtp.server.launchbar/src/org/jboss/tools/wtp/server/launchbar/ModuleObjectProvider.java:[325] > 02:32:22 [ERROR] boolean enabled = store.getBoolean(Activator.PREF_ENABLE_LAUNCHBAR); > 02:32:22 [ERROR] ^^^^^^^^^^^^^^^^^^^^^ > 02:32:22 [ERROR] PREF_ENABLE_LAUNCHBAR cannot be resolved or is not a field > {code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21850) Maven project has wrong context root set up after import

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21850?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21850: ------------------------------------- We need to test :-) > Maven project has wrong context root set up after import > -------------------------------------------------------- > > Key: JBIDE-21850 > URL: https://issues.jboss.org/browse/JBIDE-21850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > > Importing maven project (in my case "servlet-security" from EAP quickstarts) via easymport has wrong context root (right click on project->Properties->Web Project Settings) configured. > Name of project is servlet-security, but web context root is jboss-servlet-security > This results into 404 when this project gets deployed to server. IDE opens url http://localhost:8080/jboss-servlet-security, but correct url is http://localhost:8080/servlet-security. > Note, that this does not happen when importing this project as existing maven project (not using easymport). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21850) Maven project has wrong context root set up after import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21850?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21850: ---------------------------------------- Ok, and do you think fix for JBIDE-20687 fixes this issue then? > Maven project has wrong context root set up after import > -------------------------------------------------------- > > Key: JBIDE-21850 > URL: https://issues.jboss.org/browse/JBIDE-21850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > > Importing maven project (in my case "servlet-security" from EAP quickstarts) via easymport has wrong context root (right click on project->Properties->Web Project Settings) configured. > Name of project is servlet-security, but web context root is jboss-servlet-security > This results into 404 when this project gets deployed to server. IDE opens url http://localhost:8080/jboss-servlet-security, but correct url is http://localhost:8080/servlet-security. > Note, that this does not happen when importing this project as existing maven project (not using easymport). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22508) compile failed in org.jboss.tools.wtp.server.launchbar

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22508?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22508: ---------------------------------------- Activator.PREF_ENABLE_LAUNCHBAR migrated from org.eclipse.launchbar.ui to a new plugin org.eclipse.launchbar.ui.controls See https://git.eclipse.org/r/#/c/72301/5/bundles/org.eclipse.launchbar.ui.co... > compile failed in org.jboss.tools.wtp.server.launchbar > -------------------------------------------------------- > > Key: JBIDE-22508 > URL: https://issues.jboss.org/browse/JBIDE-22508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > {code} > 02:32:22 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.25.0:compile (default-compile) on project org.jboss.tools.wtp.server.launchbar: Compilation failure: Compilation failure: > 02:32:22 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/wtp/plugins/org.jboss.tools.wtp.server.launchbar/src/org/jboss/tools/wtp/server/launchbar/ModuleObjectProvider.java:[325] > 02:32:22 [ERROR] boolean enabled = store.getBoolean(Activator.PREF_ENABLE_LAUNCHBAR); > 02:32:22 [ERROR] ^^^^^^^^^^^^^^^^^^^^^ > 02:32:22 [ERROR] PREF_ENABLE_LAUNCHBAR cannot be resolved or is not a field > {code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22301) NPE in new OS application from eclipse project with no remote git reference.

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22301?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22301: ----------------------------------------------- [~mlabuda], the only relevant change is fix JBIDE-22420 applied on May, 25, but it could not what I found in PR 1205. Could you please compare the two builds doing the same steps in the wizard? > NPE in new OS application from eclipse project with no remote git reference. > ---------------------------------------------------------------------------- > > Key: JBIDE-22301 > URL: https://issues.jboss.org/browse/JBIDE-22301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: JBDS 10.0.0.Alpha1 > Reporter: Radim Hopp > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha2 > > > Trying to finish new openshift application wizard using existing aplication from workspace without remote git repository fails with NPE: > {noformat:title=Unhandled event loop exception} > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.performFinish(NewApplicationWizard.java:194) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > 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:4494) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270) > at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > 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:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:491) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:425) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:477) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609) > at org.eclipse.equinox.launcher.Main.run(Main.java:1516) > at org.eclipse.equinox.launcher.Main.main(Main.java:1489) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21850) Maven project has wrong context root set up after import

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21850?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21850: ------------------------------------- no we're trying to follow maven's conventions, and strive to get the same behavior between eclipse and CLI. See JBIDE-20687 > Maven project has wrong context root set up after import > -------------------------------------------------------- > > Key: JBIDE-21850 > URL: https://issues.jboss.org/browse/JBIDE-21850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > > Importing maven project (in my case "servlet-security" from EAP quickstarts) via easymport has wrong context root (right click on project->Properties->Web Project Settings) configured. > Name of project is servlet-security, but web context root is jboss-servlet-security > This results into 404 when this project gets deployed to server. IDE opens url http://localhost:8080/jboss-servlet-security, but correct url is http://localhost:8080/servlet-security. > Note, that this does not happen when importing this project as existing maven project (not using easymport). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22490) For JBIDE 4.4.0.Final: Prepare for Final/GA [Forge]

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22490?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-22490. ----------------------------------- Resolution: Done Done. Thank you for the heads-up [~akazakov], you rock! :) > For JBIDE 4.4.0.Final: Prepare for Final/GA [Forge] > --------------------------------------------------- > > Key: JBIDE-22490 > URL: https://issues.jboss.org/browse/JBIDE-22490 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.4.0.Final > > > For JBIDE 4.4.0.Final [Forge]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA > [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch > 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.x > git push origin jbosstools-4.4.x > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!) > * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch > 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22462) Upgrade Forge Runtime to 3.2.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22462?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-22462. ------------------------------------- Resolution: Done > Upgrade Forge Runtime to 3.2.1.Final > ------------------------------------ > > Key: JBIDE-22462 > URL: https://issues.jboss.org/browse/JBIDE-22462 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.4.0.Alpha2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.4.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016