[JBoss JIRA] (JBIDE-18587) Error when opening a java file that is not in the project build path
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18587?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-18587:
-------------------------------------
Assignee: Snjezana Peco
> Error when opening a java file that is not in the project build path
> --------------------------------------------------------------------
>
> Key: JBIDE-18587
> URL: https://issues.jboss.org/browse/JBIDE-18587
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Snjezana Peco
>
> I had the following error in the Error Logs when opening a Java file that was not in the build path:
> {code}
> Java Model Exception: Java Model Status [src/test/generated/com/sample [in sample is not on its project's build path]
> at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:544)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
> at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
> at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
> at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1173)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:557)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:294)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:280)
> at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:235)
> at org.eclipse.jdt.internal.core.JavaElement.getChildrenOfType(JavaElement.java:249)
> at org.eclipse.jdt.internal.core.CompilationUnit.getTypes(CompilationUnit.java:920)
> at org.eclipse.jdt.internal.core.CompilationUnit.getAllTypes(CompilationUnit.java:605)
> at org.jboss.tools.arquillian.ui.internal.commands.ArquillianPropertyTester.test(ArquillianPropertyTester.java:53)
> at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68)
> at org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:21)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:189)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:72)
> at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:199)
> at org.eclipse.ui.internal.WorkbenchWindow$8.run(WorkbenchWindow.java:699)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3983)
> at org.eclipse.swt.widgets.Display.observerProc(Display.java:3573)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4989)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5367)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1101)
> at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2044)
> at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1093)
> at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2563)
> at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2012)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5627)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2105)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2329)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5691)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5128)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5277)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655)
> 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.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18846:
-------------------------------
Component/s: build
website
> create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18846
> URL: https://issues.jboss.org/browse/JBIDE-18846
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, website
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as:
> builds (nightly, staging, dev, stable)
> updates (nightly, staging, dev, stable)
> Jenkins jobs
> discovery sites (nightly, staging, dev, stable)
> target platforms
> etc.
> And for each component, we can list:
> build
> update
> Jenkins job
> etc.
> The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html
> Unsure whether generated HTML (via script) or simple .adoc is better for this.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18846:
-------------------------------
Fix Version/s: 4.3.0.Alpha1
> create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18846
> URL: https://issues.jboss.org/browse/JBIDE-18846
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, website
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as:
> builds (nightly, staging, dev, stable)
> updates (nightly, staging, dev, stable)
> Jenkins jobs
> discovery sites (nightly, staging, dev, stable)
> target platforms
> etc.
> And for each component, we can list:
> build
> update
> Jenkins job
> etc.
> The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html
> Unsure whether generated HTML (via script) or simple .adoc is better for this.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18849) Logged exceptions when running man command in Forge console
by George Gastaldi (JIRA)
George Gastaldi created JBIDE-18849:
---------------------------------------
Summary: Logged exceptions when running man command in Forge console
Key: JBIDE-18849
URL: https://issues.jboss.org/browse/JBIDE-18849
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.2.0.Final
Reporter: George Gastaldi
Fix For: 4.2.x
{code}
!ENTRY org.jboss.tools.forge.aesh.core 4 1 2014-11-28 16:15:11.954
!MESSAGE Error logged from Aesh Core Plugin:
!STACK 0
java.lang.Throwable: Unimplemented command: SHOW_CURSOR
at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:18)
at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:22)
at org.jboss.tools.aesh.core.internal.io.DocumentInputOutputHandler.handleCommand(DocumentInputOutputHandler.java:41)
at org.jboss.tools.aesh.core.internal.io.CommandFilter.filterOutput(CommandFilter.java:50)
at org.jboss.tools.aesh.core.internal.io.AeshOutputStream.write(AeshOutputStream.java:27)
at java.io.PrintStream.write(PrintStream.java:480)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
at java.io.PrintStream.write(PrintStream.java:527)
at java.io.PrintStream.print(PrintStream.java:669)
at org.jboss.aesh.console.man.AeshFileDisplayer.afterAttach(AeshFileDisplayer.java:97)
at org.jboss.aesh.console.man.Man.execute(Man.java:88)
at org.jboss.forge.addon.shell.ui.AeshUICommand.execute(AeshUICommand.java:88)
at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90)
at org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:82)
at org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:325)
at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:40)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
!ENTRY org.jboss.tools.forge.aesh.core 4 1 2014-11-28 16:15:15.314
!MESSAGE Error logged from Aesh Core Plugin:
!STACK 0
java.lang.Throwable: Unimplemented command: HIDE_CURSOR
at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:18)
at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:22)
at org.jboss.tools.aesh.core.internal.io.DocumentInputOutputHandler.handleCommand(DocumentInputOutputHandler.java:41)
at org.jboss.tools.aesh.core.internal.io.CommandFilter.filterOutput(CommandFilter.java:50)
at org.jboss.tools.aesh.core.internal.io.AeshOutputStream.write(AeshOutputStream.java:27)
at java.io.PrintStream.write(PrintStream.java:480)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
at java.io.PrintStream.write(PrintStream.java:527)
at java.io.PrintStream.print(PrintStream.java:669)
at org.jboss.aesh.console.man.AeshFileDisplayer.afterDetach(AeshFileDisplayer.java:111)
at org.jboss.aesh.console.man.AeshFileDisplayer.processOperation(AeshFileDisplayer.java:138)
at org.jboss.aesh.console.man.AeshFileDisplayer.processInput(AeshFileDisplayer.java:120)
at org.jboss.aesh.console.man.AeshFileDisplayer.afterAttach(AeshFileDisplayer.java:104)
at org.jboss.aesh.console.man.Man.execute(Man.java:88)
at org.jboss.forge.addon.shell.ui.AeshUICommand.execute(AeshUICommand.java:88)
at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90)
at org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:82)
at org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:325)
at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:40)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18513) [rse-mgmt server] Servers still require access to remote runtime even when no runtime needed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18513?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18513:
-------------------------------------
In case you can't tell by visual, the new additions are
1) A label indicating whether it is mandatory, and
2) validation (error images next to the text fields) disabled if the field is not mandatory.
As currently hard-coded, the remote runtime is not required if:
1) your server is in rse+mgmt mode
2) you have marked it as externally-managed
So, if a user goes 'back' to the profile page, and changes the selection of externally managed, and then 'forward' again, the composite will update appropriately, change the label, and disable the validation on those fields.
> [rse-mgmt server] Servers still require access to remote runtime even when no runtime needed
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-18513
> URL: https://issues.jboss.org/browse/JBIDE-18513
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 4.2.1.Final
>
> Attachments: noRemoteRuntime.png
>
>
> We removed the need for having access to local runtime when using a remote server but we still require additional access to the remote runtime (via ssh or similar) even though our server should be able to deploy to a server that is running in management mode + externally managed.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months