October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3201) Start and Stop OSE Application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3201?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-3201: ---------------------------------------- [~jbride] Fully agree, we should offer this and we already planned to have this in JBIDE-11903 > Start and Stop OSE Application > ------------------------------ > > Key: JBDS-3201 > URL: https://issues.jboss.org/browse/JBDS-3201 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.0.0.GA > Reporter: Jeff Bride > Assignee: Max Rydahl Andersen > > Hello. > Currently, the OSE plugin of JBDS appears to only allow a restart of an application. > Requesting additional options to explicitly stop and start an application as well. > thanks! > jeff -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18572) NPE while calling a diff between 2 versions of a JS file

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18572?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-18572: --------------------------------------- [~kmarmaliykov], I'm running JBoss Tools on MacOSX 10.9 64bits. > NPE while calling a diff between 2 versions of a JS file > -------------------------------------------------------- > > Key: JBIDE-18572 > URL: https://issues.jboss.org/browse/JBIDE-18572 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.CR1 > Reporter: Xavier Coulon > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.2.1.Final > > > Not sure if the error is related {{summarry}}, but here's the stacktrace: > I did compare my current JS file with the first version in my history, which was an empty file, then I called the diff with the next version and I got this error. I kept having this error when comparing the current version with any other version of the file (if that can help to reproduce/identify the problem) > {code} > java.lang.NullPointerException > at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:572) > at org.jboss.tools.vpe.preview.editor.VpvEditor.access$0(VpvEditor.java:551) > at org.jboss.tools.vpe.preview.editor.VpvEditor$EditorListener.partInputChanged(VpvEditor.java:674) > at org.eclipse.ui.internal.WorkbenchPage$28.run(WorkbenchPage.java:5151) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.WorkbenchPage.firePartInputChanged(WorkbenchPage.java:5148) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$4.propertyChanged(CompatibilityPart.java:369) > at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:132) > at org.eclipse.compare.internal.CompareEditor.doSetInput(CompareEditor.java:313) > at org.eclipse.compare.internal.CompareEditor.setInput(CompareEditor.java:254) > at org.eclipse.compare.internal.CompareUIPlugin$1.run(CompareUIPlugin.java:546) > at org.eclipse.compare.internal.CompareUIPlugin.syncExec(CompareUIPlugin.java:1413) > at org.eclipse.compare.internal.CompareUIPlugin.internalOpenEditor(CompareUIPlugin.java:567) > at org.eclipse.compare.internal.CompareUIPlugin.openEditorInBackground(CompareUIPlugin.java:537) > at org.eclipse.compare.internal.CompareUIPlugin.openCompareEditor(CompareUIPlugin.java:526) > at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:199) > at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:180) > at org.eclipse.team.internal.ui.actions.CompareRevisionAction.openInCompare(CompareRevisionAction.java:139) > at org.eclipse.team.internal.ui.actions.CompareRevisionAction.run(CompareRevisionAction.java:102) > at org.eclipse.team.internal.ui.history.LocalHistoryPage$9.open(LocalHistoryPage.java:414) > at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) > at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:853) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178) > at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:850) > at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1142) > at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1249) > at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278) > at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > 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: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:484) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18685) Sometimes the internal browser shows cached outdated content when using Show In Web Browser

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18685?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18685: -------------------------------- Fix Version/s: 4.2.1.Final > Sometimes the internal browser shows cached outdated content when using Show In Web Browser > ------------------------------------------------------------------------------------------- > > Key: JBIDE-18685 > URL: https://issues.jboss.org/browse/JBIDE-18685 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.1.Final > > > Sometimes "Show in web browser" on a server in Server View results in wrong content being shown. When you start EAP 6, open the home page in web browser, then stop EAP, start AS7, open the home page again (using Show In) and the browser will still show EAP's home page. > [~ljelinko] discovered this bug on Linux and I was able to reproduce it on OS X. > I understand that this might be a problem in Eclipse itself, that's up to you, Rob, to investigate :) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18697) Error deploying exploded war on windows; fs / copy error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18697?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-18697 at 10/27/14 4:31 AM: --------------------------------------------------------------- I think we should consider updating the error message to include file permissions. How's this sound? {code} PublishRenameFailure=Error renaming {0} to {1}. \n\nThis may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.\n\nYou may adjust these settings in the server editor. {code} was (Author: rob.stryker): I think we should consider updating the error message to include file permissions. How's this sound? PublishRenameFailure=Error renaming {0} to {1}. \n\nThis may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.\n\nYou may adjust these settings in the server editor. > Error deploying exploded war on windows; fs / copy error > -------------------------------------------------------- > > Key: JBIDE-18697 > URL: https://issues.jboss.org/browse/JBIDE-18697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Rob Stryker > Fix For: 4.2.1.Final > > > https://developer.jboss.org/message/907562 > A user has reported that on windows, deploying a simple exploded war has failed with a copy error. This should be investigated -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18697) Error deploying exploded war on windows; fs / copy error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18697?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18697: -------------------------------- Fix Version/s: 4.2.1.Final > Error deploying exploded war on windows; fs / copy error > -------------------------------------------------------- > > Key: JBIDE-18697 > URL: https://issues.jboss.org/browse/JBIDE-18697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Rob Stryker > Fix For: 4.2.1.Final > > > https://developer.jboss.org/message/907562 > A user has reported that on windows, deploying a simple exploded war has failed with a copy error. This should be investigated -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18697) Error deploying exploded war on windows; fs / copy error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18697?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18697: ------------------------------------- I think we should consider updating the error message to include file permissions. How's this sound? PublishRenameFailure=Error renaming {0} to {1}. \n\nThis may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.\n\nYou may adjust these settings in the server editor. > Error deploying exploded war on windows; fs / copy error > -------------------------------------------------------- > > Key: JBIDE-18697 > URL: https://issues.jboss.org/browse/JBIDE-18697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Rob Stryker > > https://developer.jboss.org/message/907562 > A user has reported that on windows, deploying a simple exploded war has failed with a copy error. This should be investigated -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3183) Usage website does not contain ws tester reporting

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-3183?page=com.atlassian.jira.plugin.... ] Radim Hopp closed JBDS-3183. ---------------------------- Resolution: Done > Usage website does not contain ws tester reporting > -------------------------------------------------- > > Key: JBDS-3183 > URL: https://issues.jboss.org/browse/JBDS-3183 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: usage, website > Affects Versions: 8.0.0.CR2 > Reporter: Radim Hopp > Assignee: Radim Hopp > Priority: Minor > Fix For: 8.0.0.GA > > > Usage website is missing info about Web Service Tester usage reporting. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3183) Usage website does not contain ws tester reporting

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3183?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3183: ----------------------------- CDW release: ? > Usage website does not contain ws tester reporting > -------------------------------------------------- > > Key: JBDS-3183 > URL: https://issues.jboss.org/browse/JBDS-3183 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: usage, website > Affects Versions: 8.0.0.CR2 > Reporter: Radim Hopp > Assignee: Radim Hopp > Priority: Minor > Fix For: 8.0.0.GA > > > Usage website is missing info about Web Service Tester usage reporting. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3183) Usage website does not contain ws tester reporting

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-3183?page=com.atlassian.jira.plugin.... ] Radim Hopp updated JBDS-3183: ----------------------------- CDW qa_ack: + (was: ?) Status: New (was: New) > Usage website does not contain ws tester reporting > -------------------------------------------------- > > Key: JBDS-3183 > URL: https://issues.jboss.org/browse/JBDS-3183 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: usage, website > Affects Versions: 8.0.0.CR2 > Reporter: Radim Hopp > Assignee: Radim Hopp > Priority: Minor > Fix For: 8.0.0.GA > > > Usage website is missing info about Web Service Tester usage reporting. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3183) Usage website does not contain ws tester reporting

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-3183?page=com.atlassian.jira.plugin.... ] Radim Hopp updated JBDS-3183: ----------------------------- Fix Version/s: 8.0.0.GA > Usage website does not contain ws tester reporting > -------------------------------------------------- > > Key: JBDS-3183 > URL: https://issues.jboss.org/browse/JBDS-3183 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: usage, website > Affects Versions: 8.0.0.CR2 > Reporter: Radim Hopp > Assignee: Radim Hopp > Priority: Minor > Fix For: 8.0.0.GA > > > Usage website is missing info about Web Service Tester usage reporting. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 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