September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-15978) Properties view: URL for embedded cartridges is empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15978?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15978: ------------------------------------- Estimated Difficulty: Low (was: Medium) > Properties view: URL for embedded cartridges is empty > ----------------------------------------------------- > > Key: JBIDE-15978 > URL: https://issues.jboss.org/browse/JBIDE-15978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Labels: properties > Fix For: 4.3.x > > Attachments: empty-url-property.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15978) Properties view: URL for embedded cartridges is empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15978?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15978: ------------------------------------- Labels: properties (was: ) > Properties view: URL for embedded cartridges is empty > ----------------------------------------------------- > > Key: JBIDE-15978 > URL: https://issues.jboss.org/browse/JBIDE-15978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Labels: properties > Fix For: 4.3.x > > Attachments: empty-url-property.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16767) Application wizard, embed wizard: Support "Deploy Now" urls for "code anything"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16767?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16767: ------------------------------------- Summary: Application wizard, embed wizard: Support "Deploy Now" urls for "code anything" (was: Application wizard, embed wizard: Support Deploy Now urls for "code anything") > Application wizard, embed wizard: Support "Deploy Now" urls for "code anything" > ------------------------------------------------------------------------------- > > Key: JBIDE-16767 > URL: https://issues.jboss.org/browse/JBIDE-16767 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Priority: Minor > Labels: application_wizard, embed_wizard > Fix For: 4.3.x > > Attachments: wildfly8-quickstart-deploy-now.png > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > OpenShift have a notion of Deploy Now urls. > Example: https://openshift.redhat.com/app/console/application_type/quickstart!16766 as found on https://www.openshift.com/quickstarts/wildfly-8 > It would be nice if the url field in Code Anything could detect these and use it as its starting point as an alternative to knowing the exact git repo location. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16714) Embed wizard, Application wizard: Embed same cartridge with different version should show warning

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16714?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16714: ------------------------------------- Estimated Difficulty: Low (was: Medium) > Embed wizard, Application wizard: Embed same cartridge with different version should show warning > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-16714 > URL: https://issues.jboss.org/browse/JBIDE-16714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, embed_wizard > Fix For: 4.3.x > > > Nowadays, when on OpenShift Online are available multiple cartridges differentiated only by version (e.g. PostgreSQL 8.4 and 9.2) there should be some kind of warning about embedding both (what could happen accidentally or by ignorance...). > How it works now? If user choose 2 cartridges of the same type, then just the first one is embedded and while trying to embed second cartridge user get error that application has already embedded that kind of cartridge (that they cannot coexist). > I suggest to have similar dialog as in embedding e.g. Jenkins cartridge to application without having Jenkins Application (server) etc. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16767) Application wizard, embed wizard: Support Deploy Now urls for "code anything"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16767?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16767: ------------------------------------- Summary: Application wizard, embed wizard: Support Deploy Now urls for "code anything" (was: Support Deploy Now urls for "code anything") > Application wizard, embed wizard: Support Deploy Now urls for "code anything" > ----------------------------------------------------------------------------- > > Key: JBIDE-16767 > URL: https://issues.jboss.org/browse/JBIDE-16767 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Priority: Minor > Labels: application_wizard, embed_wizard > Fix For: 4.3.x > > Attachments: wildfly8-quickstart-deploy-now.png > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > OpenShift have a notion of Deploy Now urls. > Example: https://openshift.redhat.com/app/console/application_type/quickstart!16766 as found on https://www.openshift.com/quickstarts/wildfly-8 > It would be nice if the url field in Code Anything could detect these and use it as its starting point as an alternative to knowing the exact git repo location. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16597) Server Adapter Editor: Open launch configuration cause error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16597?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16597: ------------------------------------------ copied from JBIDE-16042: {quote} The link is created by WTP. To avoid the current error there are actually 2 possible solutions: * create empty custom launch config tabs * remove launchConfigId from serverType in the plugin.xml in our core plugin {quote} > Server Adapter Editor: Open launch configuration cause error > ------------------------------------------------------------ > > Key: JBIDE-16597 > URL: https://issues.jboss.org/browse/JBIDE-16597 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Marián Labuda > Priority: Minor > Labels: server_adapter_editor > Fix For: 4.3.x > > Attachments: open_launch_config1.png, open_launch_config2.png, open_launch_config3.png > > Original Estimate: 1 day > Remaining Estimate: 1 day > > In OpenShift server adapter settings is Open launch configuration link. Throws error after click on it. See attached images and error log: > {code:title=.log} > !ENTRY org.eclipse.ui 4 0 2014-02-17 13:45:08.437 > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.NullPointerException > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleApplyPressed(LaunchConfigurationTabGroupViewer.java:1401) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$3.widgetSelected(LaunchConfigurationTabGroupViewer.java:308) > 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:4423) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1154) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:213) > at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:661) > at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:638) > at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart$9.linkActivated(OverviewEditorPart.java:594) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) > at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226) > 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 was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16596) Server Adapter Editor: Timeouts and publishing fields are too small

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16596?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16596: ------------------------------------- Estimated Difficulty: Medium > Server Adapter Editor: Timeouts and publishing fields are too small > ------------------------------------------------------------------- > > Key: JBIDE-16596 > URL: https://issues.jboss.org/browse/JBIDE-16596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Marián Labuda > Priority: Minor > Labels: server_adapter_editor > Fix For: 4.3.x > > Attachments: small_field.png > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > In Server View double click on any OpenShift server adapter to open adapter settings. There are 2 fields for timeout settings and one for publishing which are too small. See attached image. It is impossible to see values (just only through hoovering). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3140) Ship tern eclipse and integration feature (jst.jsdt) by default in JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3140?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-3140: --------------------------------- Component/s: jsp/jsf/xml/html source editing > Ship tern eclipse and integration feature (jst.jsdt) by default in JBDS > ----------------------------------------------------------------------- > > Key: JBDS-3140 > URL: https://issues.jboss.org/browse/JBDS-3140 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jsp/jsf/xml/html source editing, p2-product, updatesite > Reporter: Mickael Istria > Priority: Blocker > > We want tern and our integration feature (org.jboss.tools.jst.jsdt.feature) to be included in JBDS by default. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16042) Server Editor: "Open launch configuration" errors

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16042?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-16042. -------------------------------------- Assignee: Andre Dietisheim Fix Version/s: 4.2.0.CR1 (was: 4.2.x) Resolution: Duplicate Issue > Server Editor: "Open launch configuration" errors > ------------------------------------------------- > > Key: JBIDE-16042 > URL: https://issues.jboss.org/browse/JBIDE-16042 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: server_adapter_editor > Fix For: 4.2.0.CR1 > > Attachments: open-launch-config-error.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16597) Server Adapter: Open launch configuration cause error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16597?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16597: ------------------------------------- Summary: Server Adapter: Open launch configuration cause error (was: OpenShift Server Adapter: Open launch configuration cause error) > Server Adapter: Open launch configuration cause error > ----------------------------------------------------- > > Key: JBIDE-16597 > URL: https://issues.jboss.org/browse/JBIDE-16597 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Marián Labuda > Priority: Minor > Labels: server_adapter_editor > Fix For: 4.3.x > > Attachments: open_launch_config1.png, open_launch_config2.png, open_launch_config3.png > > Original Estimate: 1 day > Remaining Estimate: 1 day > > In OpenShift server adapter settings is Open launch configuration link. Throws error after click on it. See attached images and error log: > {code:title=.log} > !ENTRY org.eclipse.ui 4 0 2014-02-17 13:45:08.437 > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.NullPointerException > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleApplyPressed(LaunchConfigurationTabGroupViewer.java:1401) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$3.widgetSelected(LaunchConfigurationTabGroupViewer.java:308) > 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:4423) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1154) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:213) > at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:661) > at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:638) > at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart$9.linkActivated(OverviewEditorPart.java:594) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) > at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226) > 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 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