May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22308) Generate p2diff together when generating TP site

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22308?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-22308. ------------------------------------ Resolution: Done Please avoid reopening issue since it messes up tracking. The work item for this issue was done as part of previous sprint, what you report is actually a new blocker issue for the current sprint, it needs to be tracked separately. > Generate p2diff together when generating TP site > ------------------------------------------------ > > Key: JBIDE-22308 > URL: https://issues.jboss.org/browse/JBIDE-22308 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.3.1.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha3 > > > In the "multiple2repo" profile, add the necessary build steps to always generate the p2diff report. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process can include snapshots artifacts

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22446: ---------------------------------- Summary: Release process can include snapshots artifacts Key: JBIDE-22446 URL: https://issues.jboss.org/browse/JBIDE-22446 Project: Tools (JBoss Tools) Issue Type: Release Components: openshift Affects Versions: 4.4.0.Alpha2 Reporter: Jeff MAURY Fix For: 4.4.x 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22308) Generate p2diff together when generating TP site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22308?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22308: ------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Generate p2diff together when generating TP site > ------------------------------------------------ > > Key: JBIDE-22308 > URL: https://issues.jboss.org/browse/JBIDE-22308 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.3.1.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha3 > > > In the "multiple2repo" profile, add the necessary build steps to always generate the p2diff report. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22198) Sometimes validation for required parameter in Template Parameters wizard page when creating an application is not available

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22198?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-22198: ----------------------------------------- Sorry but I'm still not able to reproduce > Sometimes validation for required parameter in Template Parameters wizard page when creating an application is not available > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22198 > URL: https://issues.jboss.org/browse/JBIDE-22198 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Aurélien Pupier > Fix For: 4.4.0.Alpha3 > > Attachments: screenshot-1.png > > > Having a validation, forbidding to go to next page and click finish will provide more guidance to user and avoid him an error dialog when clicking finish -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-219) Node.js application children processes can not be killed from eclipse console [EBZ#494592]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-219: --------------------------------------- Summary: Node.js application children processes can not be killed from eclipse console [EBZ#494592] Key: ERT-219 URL: https://issues.jboss.org/browse/ERT-219 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot When running a simple Node.js application like: var child_process = require('child_process'); child_process.exec('ping www.google.com -t', function (err, stdout, stderr){ if (err) { console.log("child processes failed with error code: " + err.code); } console.log(stdout); }); If you terminate the running process the "ping www.google.com -t" child process is still running even when the parent process is already killed. This happens with one or more children processes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18951) jboss-web_8_0.xsd in AS XML catalog reported as "containing errors" by Luna

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18951?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-18951: ---------------------------------- Attachment: xsd-details.png OK, the details window isn't exactly user friendly, so this is as much as I could get: [^xsd-details.png] > jboss-web_8_0.xsd in AS XML catalog reported as "containing errors" by Luna > --------------------------------------------------------------------------- > > Key: JBIDE-18951 > URL: https://issues.jboss.org/browse/JBIDE-18951 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Final > Environment: W7 Pro SP1 > eclipse.buildId=4.4.1.M20140925-0400 > org.jboss.tools.as.catalog (3.0.0.Final-v20141016-1911-B95) "JBoss AS XML Catalog Entries" > Reporter: Jordan Glassman > Assignee: Rob Stryker > Attachments: Capture4.PNG, xsd-details.png > > > In a jboss-web.xml file, a namespace declaration like: > {code} <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" version="8.0" > >{code} > Gives eclipse error: > {quote}Referenced file contains errors (jar:file:/C:/eclipse/plugins/org.jboss.tools.as.catalog_3.0.0.Final-v20141016-1911-B95.jar!/schema/xsd/jboss-web_8_0.xsd). > For more information, right click on the message in the Problems View and select "Show Details..."{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22445) NPE when finishing New server wizard (OS3 adapter)

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-22445: ---------------------------------- Summary: NPE when finishing New server wizard (OS3 adapter) Key: JBIDE-22445 URL: https://issues.jboss.org/browse/JBIDE-22445 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha2 Reporter: Radim Hopp I'm getting NPE when finishing New Server Wizard of Openshift 3 server adapter. mlabuda was also able to reproduce this bug. {noformat} java.lang.NullPointerException at org.eclipse.wst.server.ui.internal.wizard.TaskWizardPage.update(TaskWizardPage.java:126) at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardFragment$ServerSettingsWizardPageWrapper.setPageComplete(ServerSettingsWizardFragment.java:200) at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage.setComplete(ServerSettingsWizardPage.java:189) at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage$1.setComplete(ServerSettingsWizardPage.java:207) at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.handleComplete(FormPresenterSupport.java:243) at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.handleStatusChanged(FormPresenterSupport.java:232) at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.statusProviderChanged(FormPresenterSupport.java:200) at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.access$2(FormPresenterSupport.java:190) at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport$4.handleValueChange(FormPresenterSupport.java:158) at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:70) at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117) at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:82) at org.eclipse.core.databinding.observable.value.ComputedValue.makeDirty(ComputedValue.java:240) at org.eclipse.core.databinding.observable.value.ComputedValue$PrivateInterface.handleChange(ComputedValue.java:183) at org.eclipse.core.databinding.observable.ChangeEvent.dispatch(ChangeEvent.java:42) at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117) at org.eclipse.core.databinding.observable.AbstractObservable.fireChange(AbstractObservable.java:71) at org.eclipse.core.databinding.observable.list.ObservableList.fireListChange(ObservableList.java:81) at org.eclipse.core.databinding.observable.list.WritableList.remove(WritableList.java:235) at org.eclipse.core.databinding.DataBindingContext.removeValidationStatusProvider(DataBindingContext.java:489) at org.eclipse.core.databinding.DataBindingContext.removeBinding(DataBindingContext.java:476) at org.eclipse.core.databinding.Binding.dispose(Binding.java:135) at org.eclipse.core.databinding.ValueBinding.dispose(ValueBinding.java:269) at org.eclipse.core.databinding.DataBindingContext.dispose(DataBindingContext.java:367) at org.jboss.tools.openshift.internal.common.ui.utils.DataBindingUtils.dispose(DataBindingUtils.java:107) at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$1.widgetDisposed(AbstractOpenShiftWizardPage.java:79) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:124) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1345) at org.eclipse.swt.widgets.Widget.release(Widget.java:1153) at org.eclipse.swt.widgets.Control.release(Control.java:3989) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:479) at org.eclipse.swt.widgets.Shell.dispose(Shell.java:2660) at org.eclipse.jface.window.Window.close(Window.java:330) at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:989) at org.eclipse.jface.wizard.WizardDialog.hardClose(WizardDialog.java:853) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:798) 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:249) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) at org.eclipse.jface.window.Window.open(Window.java:794) at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) at org.eclipse.jface.window.Window.open(Window.java:794) at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) at org.eclipse.jface.window.Window.open(Window.java:794) at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) 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:148) 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:673) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) at org.eclipse.equinox.launcher.Main.run(Main.java:1519) at org.eclipse.equinox.launcher.Main.main(Main.java:1492) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20711) Changing deploy-name in component xml file will not take effect

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20711?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20711: --------------------------------------- [~rob.stryker], I tried this in JBDS 10.0.0.Alpha2 on Mac. And I can't reproduce. I changed the deploy-name in .settings/org.eclipse.wst.common.component and then refreshed the project in project explorer. And then I opened the Add/Remove dialog on WildFly and it said properly TestProject(RobsTest). And so I deployed it and it correctly deployed RobsTest.war as /RobsTest > Changing deploy-name in component xml file will not take effect > --------------------------------------------------------------- > > Key: JBIDE-20711 > URL: https://issues.jboss.org/browse/JBIDE-20711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.x > > > Steps to replicate: > 1) Create a dynamic web project TestProject > 2) Create a server > 3) Add/Remove action in servers view. You will see the module name is TestProject > 4) Open the component.xml file in .settings folder and change deploy-name to some new value (RobsTest) > 5) Add/Remove, note module name didn't change > 6) Publish deployment, note its still deploying as TestProject > 7) Close project, then re-open it > 8) Add/Remove action, note the module now reads TestProject (RobsTest) (or similar) > 9) Publish, note module is deployed as RobsTest.war -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21197) [cdk] Ensure adbinfo is run in the background, not in a console

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21197?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21197. --------------------------------- Verified. > [cdk] Ensure adbinfo is run in the background, not in a console > --------------------------------------------------------------- > > Key: JBIDE-21197 > URL: https://issues.jboss.org/browse/JBIDE-21197 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > The adbinfo should not be run or visible in a console. It is clobbering the existing console from vagrant up, and so should be run in the background only. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21163) cdk server adapter dumps out adbinfo to console

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21163?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21163. --------------------------------- Verified in JBDS 10.0.0.Alpha2 > cdk server adapter dumps out adbinfo to console > ----------------------------------------------- > > Key: JBIDE-21163 > URL: https://issues.jboss.org/browse/JBIDE-21163 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1, 4.4.0.Alpha1 > > > is it intended that if the cdk is running the console shows up with dump that contains: > {quote} > # Set the following environment variables to enable access to the > # docker daemon running inside of the vagrant virtual machine: > export DOCKER_HOST=tcp://10.1.2.2:2376 > export DOCKER_CERT_PATH=/Users/max/code/cdk/openshift-vagrant/cdk-v2/.vagrant/machines/default/virtualbox/.docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_MACHINE_NAME=9dc5acb > # run following command to configure your shell: > # eval "$(vagrant adbinfo)" > {quote} > it is a bit confusing it pops up with no info and gets to be in front of everything. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 May 2016