December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19974) Cannot detect running boot2docker on OS X

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19974?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19974. --------------------------------- OK, it works for me now in jboss-devstudio-9.1.0.Beta1-v20151212-0638-B189-installer-standalone.jar . I would like to point out though that it's still far from ideal. It relies on DOCKER variables set up in your .bash_profile which typically is not the case. And also, it will not recognize if the docker machine is actually running or not. But the scope of this JIRA was fixed. > Cannot detect running boot2docker on OS X > ----------------------------------------- > > Key: JBIDE-19974 > URL: https://issues.jboss.org/browse/JBIDE-19974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.3.1.Beta1 > > > In Docker Explorer, when I want to create my first connection, I click on the link to create a connection, the dialog is opened and I get this in my Error View: > bash: no job control in this shell > An exception stack trace is not available. > Another warning is generated also: > Could not find default settings to connect to a local Docker daemon > An exception stack trace is not available. > I'm on OS X and have boot2docker running. By default, boot2docker will not add the DOCKER variables to .bash_profile, it will only instruct me to set them up like this: > export DOCKER_HOST=tcp://192.168.59.103:2376 > export DOCKER_CERT_PATH=/Users/rasp/.boot2docker/certs/boot2docker-vm > export DOCKER_TLS_VERIFY=1 > With the way the script in the Docker Tooling works (env | grep DOCKER), it cannot detect the variables unless they are in .bash_profile. > But even if I added them there (and a new Terminal window has these variables), Eclipse still can't detect the running Docker instance. > So something is wrong. > I logged an upstream bug here: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=469624 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20923) Wrong archetype is picked for unreleased EAP (7)

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20923?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-20923. ------------------------------ Verified in JBDS 9.1.0.Beta1-v20151212-0638-B189 > Wrong archetype is picked for unreleased EAP (7) > ------------------------------------------------ > > Key: JBIDE-20923 > URL: https://issues.jboss.org/browse/JBIDE-20923 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > When EAP 7 is selected as target runtime when creating project from archetype (EAR Project for example), version org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final is selected (JBoss AS 7.1 archetype). > Instead of this, either last released EAP version (currently 6.4) archetype should be selected, or the "most compatible" (at this time probably WFLY 8.2 archetype) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21317) EA enablement status is not propagated to first page of Central

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-21317: ---------------------------------- Summary: EA enablement status is not propagated to first page of Central Key: JBIDE-21317 URL: https://issues.jboss.org/browse/JBIDE-21317 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.3.1.Beta1 Environment: JBDS 9.1.0.Beta1-v20151212-0638-B189 Reporter: Radim Hopp See steps to Reproduce. Note, that this was working in JBDS 9.0.0.GA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21316) Creating artifact for non-batch project results in NPE

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-21316: ---------------------------------------- Summary: Creating artifact for non-batch project results in NPE Key: JBIDE-21316 URL: https://issues.jboss.org/browse/JBIDE-21316 Project: Tools (JBoss Tools) Issue Type: Bug Components: batch Affects Versions: 4.3.1.Beta1 Reporter: Rastislav Wagner Fix For: 4.3.1.Beta2 {code} java.lang.NullPointerException at org.jboss.tools.batch.internal.core.impl.PreferredPackageManager.savePreferredPackage(PreferredPackageManager.java:95) at org.jboss.tools.batch.ui.internal.wizard.NewBatchArtifactWizard.performFinish(NewBatchArtifactWizard.java:116) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) 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:4481) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) 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:56) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) 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:493) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160) 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:4481) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) 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:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) 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:669) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) at org.eclipse.equinox.launcher.Main.run(Main.java:1515) at org.eclipse.equinox.launcher.Main.main(Main.java:1488) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21315) CDK: Missing PATH for vagrant and VBoxManage on Mac

by Martin Malina (JIRA)

Martin Malina created JBIDE-21315: ------------------------------------- Summary: CDK: Missing PATH for vagrant and VBoxManage on Mac Key: JBIDE-21315 URL: https://issues.jboss.org/browse/JBIDE-21315 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Martin Malina Assignee: Rob Stryker It seems there is no JIRA to track this specifically yet. The problem is that CDK tooling relies on PATH to find vagrant. And the "vagrant up" command in turn depends on PATH to find e.g. VBoxManage. On Mac, when you start your Eclipse / JBDS as an app by double-clicking an icon on your Desktop or in Finder, the Eclipse instance will have no PATH env variable. One workaround is to start your Eclipse from command line by going inside the package: {code} cd Eclipse.app/Contents/MacOS ./eclipse {code} But this is definitely not the recommended way to start Eclipse - I'm not sure if eclipse.ini is located properly in this case. But at least PATH is correct then. There is actually one more workaround. To add your PATH to the Environment tab in Launch config. That works for me. So that might be a potential solution to this problem - have a predefined PATH for each OS in case there is none defined in the Eclipse process. Previous related JIRAs: JBIDE-21175 [CDK] Require better logic to find vagrant.exe / vagrant command JBIDE-21172 CDK server in Starting state and cannot be stopped with wrong path to vagrant -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21179) Upgrade Forge Runtime to 3.0.0.Alpha3

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21179?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21179. ------------------------------ 4.3.0.Beta1 B189 build contains forge 3.0.0.Alpha3. Closing. I'll file separate issues if found > Upgrade Forge Runtime to 3.0.0.Alpha3 > ------------------------------------- > > Key: JBIDE-21179 > URL: https://issues.jboss.org/browse/JBIDE-21179 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21314) Cannot deploy mvn module of an existing git-based application to OpenShift 3 server

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21314?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21314: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Cannot deploy mvn module of an existing git-based application to OpenShift 3 server > ----------------------------------------------------------------------------------- > > Key: JBIDE-21314 > URL: https://issues.jboss.org/browse/JBIDE-21314 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: application_wizard.png > > > If a git-based project it maven module and it has some parent (like eap quickstarts available at https://github.com/jboss-developer/jboss-eap-quickstarts) it is not possible to deploy such a project. There is an error in New OpenShift Application wizard telling that a project is not git project, although it is. There was similar issue with OpenShift 2 and with deploying projects which did not have .git folder in itself but it was in parent. See following screenshot: > !application_wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21152) Cannot deploy mvn module of an existing git-based application to OpenShift 3 server

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21152?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21152: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Cannot deploy mvn module of an existing git-based application to OpenShift 3 server > ----------------------------------------------------------------------------------- > > Key: JBIDE-21152 > URL: https://issues.jboss.org/browse/JBIDE-21152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: application_wizard.png > > > If a git-based project it maven module and it has some parent (like eap quickstarts available at https://github.com/jboss-developer/jboss-eap-quickstarts) it is not possible to deploy such a project. There is an error in New OpenShift Application wizard telling that a project is not git project, although it is. There was similar issue with OpenShift 2 and with deploying projects which did not have .git folder in itself but it was in parent. See following screenshot: > !application_wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21152) Cannot deploy mvn module of an existing git-based application to OpenShift 3 server

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21152?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21152. --------------------------------- Resolution: Done > Cannot deploy mvn module of an existing git-based application to OpenShift 3 server > ----------------------------------------------------------------------------------- > > Key: JBIDE-21152 > URL: https://issues.jboss.org/browse/JBIDE-21152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: application_wizard.png > > > If a git-based project it maven module and it has some parent (like eap quickstarts available at https://github.com/jboss-developer/jboss-eap-quickstarts) it is not possible to deploy such a project. There is an error in New OpenShift Application wizard telling that a project is not git project, although it is. There was similar issue with OpenShift 2 and with deploying projects which did not have .git folder in itself but it was in parent. See following screenshot: > !application_wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21152) Cannot deploy mvn module of an existing git-based application to OpenShift 3 server

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21152?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21152. --------------------------------- Verified in JBDS 9.1.0.Beta1 build ID B189 > Cannot deploy mvn module of an existing git-based application to OpenShift 3 server > ----------------------------------------------------------------------------------- > > Key: JBIDE-21152 > URL: https://issues.jboss.org/browse/JBIDE-21152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: application_wizard.png > > > If a git-based project it maven module and it has some parent (like eap quickstarts available at https://github.com/jboss-developer/jboss-eap-quickstarts) it is not possible to deploy such a project. There is an error in New OpenShift Application wizard telling that a project is not git project, although it is. There was similar issue with OpenShift 2 and with deploying projects which did not have .git folder in itself but it was in parent. See following screenshot: > !application_wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 December 2015