October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-512) OpenShift How To: Manage Existing Applications

by Aakanksha Singh (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-512?page=com.atlassian.jira.plug... ] Aakanksha Singh commented on TOOLSDOC-512: ------------------------------------------ Hi Supriya. 1. in Procedure "Deploying an Existing Workspace Application to OpenShift Online" Step9: In the New OpenShift Application wizard, click Finish. - When I click Finish I get the following error, "In the New OpenShift Application wizard, click Finish. [1]Error Message: "Could not create application aakanksha Could not request https://openshift.redhat.com/broker/rest/domain/aakanksha/applications?in...: haproxy-1.4 cannot be added to existing applications. It is automatically added when you create a scaling application." - Baed on this error, I went back into the wizaef to choose the Make scaling check-box. and faced another error. [2]Error message "Could not request https://openshift.redhat.com/broker/rest/domain/aakanksha/applications?in...: The cartridge 'diy-0.1' does not support being made scalable." After this above error, [2], I went back and removed the make scaling check-box and this time the procedure worked. I am sharing it incase these can be useful for troubleshooting tips. PS: I always get stuck with errors, so it is nothing to do with your steps I guess :) 2. Did you Know, second Point. The Open shift is located under Windows->Preference->JBoss Tools->Openshift . The JBoss Tools is missing in the step. > OpenShift How To: Manage Existing Applications > ---------------------------------------------- > > Key: TOOLSDOC-512 > URL: https://issues.jboss.org/browse/TOOLSDOC-512 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide - OpenShift Tools > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Final > > > Article 3: > Deploy an Existing Workspace Application > Introductory paragraphs > In the New OpenShift Application wizard, click Use my existing OpenShift application and then click Browse to look for the application > Detailed steps > Import a Running Application to a Workspace > Introductory paragraphs > Click File > Import. Expand OpenShift and click Existing OpenShift Application and then click Next > Detailed steps -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-546) Update JBDS GSG for 8.0

by Aakanksha Singh (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-546?page=com.atlassian.jira.plug... ] Aakanksha Singh commented on TOOLSDOC-546: ------------------------------------------ Michelle, Peer-reviewed the doc. The procedure steps worked as listed in the doc. No issues faced. > Update JBDS GSG for 8.0 > ----------------------- > > Key: TOOLSDOC-546 > URL: https://issues.jboss.org/browse/TOOLSDOC-546 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Getting Started Guide > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18532) NPE in VPV Editor

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18532?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-18532: ------------------------------------------- Fix Version/s: 4.3.0.Alpha1 > NPE in VPV Editor > ----------------- > > Key: JBIDE-18532 > URL: https://issues.jboss.org/browse/JBIDE-18532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.CR1 > Reporter: Victor Rubezhny > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha1 > > > NullPointerException occurs when switching from VPV Editor to HTML Editor. > It looks like VPV Editor doesn't clean up some resources (like listeners) when it's closed. > {code} > !ENTRY org.eclipse.wst.sse.core 4 4 2014-10-08 03:45:40.608 > !MESSAGE > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.vpe.preview.editor.VpvEditor$10.documentChanged(VpvEditor.java:723) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireDocumentChanged(BasicStructuredDocument.java:460) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1184) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1964) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.eclipse.jface.text.projection.ProjectionTextStore.replace(ProjectionTextStore.java:111) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1184) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210) > at org.eclipse.jface.text.projection.ProjectionDocument.replace(ProjectionDocument.java:629) > at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:248) > at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7268) > at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8111) > at org.eclipse.swt.custom.StyledText.doContent(StyledText.java:2481) > at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:5955) > at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5986) > at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5663) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397) > at org.eclipse.swt.widgets.Widget.sendIMKeyEvent(Widget.java:1474) > at org.eclipse.swt.widgets.Control.gtk_commit(Control.java:3043) > at org.eclipse.swt.widgets.Canvas.gtk_commit(Canvas.java:163) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2079) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700) > at org.eclipse.swt.internal.gtk.OS._gtk_im_context_filter_keypress(Native Method) > at org.eclipse.swt.internal.gtk.OS.gtk_im_context_filter_keypress(OS.java:8499) > at org.eclipse.swt.widgets.Control.filterKey(Control.java:2386) > at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3262) > at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:777) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2098) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700) > at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) > at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9074) > at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253) > at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) > at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2473) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18656) On opening Fuse Integration perspective, JMX components not found, so JMX Navigator wasn't created

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18656?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-18656: ------------------------------------------- At the moment, there is no Fuse tooling for JBDS 8.0.0.CR1. We have to wait for JBDS-IS 8.0.0.Beta1 (next week). > On opening Fuse Integration perspective, JMX components not found, so JMX Navigator wasn't created > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-18656 > URL: https://issues.jboss.org/browse/JBIDE-18656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Environment: OSX 10.9.4; JBDS 8.0.0.Beta3; Fuse Tooling 7.3.0.v20141013-2306-H321-MASTER; java version 1.7.0_25 > Reporter: Jane Murphey > Attachments: FT7.3.0_20141013_JMXfail.png, jbosstools-diagnostics-20141016165457.zip > > > After creating a new Fuse project, tried to open the Fuse Integration perspective. See attached graphic. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18656) On opening Fuse Integration perspective, JMX components not found, so JMX Navigator wasn't created

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18656?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-18656: ------------------------------------------- I think this is related to JBIDE-17631 which is fixed in JBDS 8.0.0.CR1 > On opening Fuse Integration perspective, JMX components not found, so JMX Navigator wasn't created > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-18656 > URL: https://issues.jboss.org/browse/JBIDE-18656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Environment: OSX 10.9.4; JBDS 8.0.0.Beta3; Fuse Tooling 7.3.0.v20141013-2306-H321-MASTER; java version 1.7.0_25 > Reporter: Jane Murphey > Attachments: FT7.3.0_20141013_JMXfail.png, jbosstools-diagnostics-20141016165457.zip > > > After creating a new Fuse project, tried to open the Fuse Integration perspective. See attached graphic. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18657) Broken build when adding N&N for unreleased version

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18657?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-18657: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) Please try this PR. For now, the N&N for 4.2.0.CR2 appears in /documentation/whatsnew, but there's no download page yet for this version. This is the original behaviour that I restored. Should we already show an empty download page (ie, with a message saying that it's coming soon, etc.) for the upcoming 4.2.0.CR2 so that both download and N&N pages exist ? WDYT ? > Broken build when adding N&N for unreleased version > --------------------------------------------------- > > Key: JBIDE-18657 > URL: https://issues.jboss.org/browse/JBIDE-18657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.CR1 > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18657) Broken build when adding N&N for unreleased version

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-18657: ------------------------------------- Summary: Broken build when adding N&N for unreleased version Key: JBIDE-18657 URL: https://issues.jboss.org/browse/JBIDE-18657 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Affects Versions: 4.2.0.CR1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.2.0.CR2 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18655) Project location should be set to "workspace" in Forge Project New wizard by default

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18655?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-18655. ------------------------------- Resolution: Rejected > Project location should be set to "workspace" in Forge Project New wizard by default > ------------------------------------------------------------------------------------ > > Key: JBIDE-18655 > URL: https://issues.jboss.org/browse/JBIDE-18655 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR2 > Reporter: Pavol Srna > > Current implementation is that "Project Location" is set to forge current selection. Which is set for the first project to "workspace", but for any other subsequent project to "forge current_selection" > But it doesn't make much sense unless we want nested projects. *Is there a use case for nested projects?* I don't thinks so. Thus I would set "Project Location" to "workspace" by default. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18655) Project location should be set to "workspace" in Forge Project New wizard by default

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18655?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-18655: --------------------------------- Assignee: Koen Aers > Project location should be set to "workspace" in Forge Project New wizard by default > ------------------------------------------------------------------------------------ > > Key: JBIDE-18655 > URL: https://issues.jboss.org/browse/JBIDE-18655 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR2 > Reporter: Pavol Srna > Assignee: Koen Aers > > Current implementation is that "Project Location" is set to forge current selection. Which is set for the first project to "workspace", but for any other subsequent project to "forge current_selection" > But it doesn't make much sense unless we want nested projects. *Is there a use case for nested projects?* I don't thinks so. Thus I would set "Project Location" to "workspace" by default. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18655) Project location should be set to "workspace" in Forge Project New wizard by default

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18655?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-18655: ------------------------------------ Ok - then please reject this jira ;-) > Project location should be set to "workspace" in Forge Project New wizard by default > ------------------------------------------------------------------------------------ > > Key: JBIDE-18655 > URL: https://issues.jboss.org/browse/JBIDE-18655 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR2 > Reporter: Pavol Srna > > Current implementation is that "Project Location" is set to forge current selection. Which is set for the first project to "workspace", but for any other subsequent project to "forge current_selection" > But it doesn't make much sense unless we want nested projects. *Is there a use case for nested projects?* I don't thinks so. Thus I would set "Project Location" to "workspace" by default. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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