[JBoss JIRA] (JBIDE-20979) Not able to resize the preferences window in JDBS 6
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20979?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20979:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Not able to resize the preferences window in JDBS 6
> ---------------------------------------------------
>
> Key: JBIDE-20979
> URL: https://issues.jboss.org/browse/JBIDE-20979
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.Final
> Environment: Fedora 17, Fedora 19,
> jdbs 6.0.0.GA, build id: GA-v20121206-1855-B186, build date: 20121206-1855
> Reporter: Sande Gilda
> Assignee: Snjezana Peco
> Fix For: 4.6.x
>
> Attachments: JDBS6-01.png, JDBS6-02.png, JDBS6-03.png, JDBS6-04.png
>
>
> To recreate:
> Start JDBS.
> Choose menu: Window --> Preferences
> Grab a side edge to drag it wider, but it snaps down to a narrow vertical bar.
> When I hover over the edges, I get the arrow resize icon, but I can't resize it.
> At this point, I have to kill the 2 processes: one jbdevstudio and one java (for jbds and the popup window.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21869:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Priority: Minor
> Fix For: 4.6.x
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21857:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Hot code replacement doesn't work on OpenShift
> ----------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.6.x
>
> Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21719:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.6.x
>
> Attachments: JBossPerspective_PropertiesMayBeWider.png, jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22145:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> nio WatchService possibly causing errors / locking files on windows
> -------------------------------------------------------------------
>
> Key: JBIDE-22145
> URL: https://issues.jboss.org/browse/JBIDE-22145
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Environment: - Windows 7 x64
> - jdk1.8.0_77 (32-bit)
> - Eclipse Mars.2 (32-bit)
> - JBoss Tools 4.3.0.FINAL
> - Wildfly 10.0.0.FINAL
> Reporter: Tobias van den Berg
> Assignee: Thomas Mäder
> Priority: Critical
> Fix For: 4.6.x
>
> Attachments: FSWatcherHang.txt, FailureWatchModify1.PML, FileWatchError.zip, Logfile.PML, OkWatchModify1.PML
>
>
> The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0:
> "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor."
> The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error.
> I've tried/tested the following:
> - Checked/updated Windows file permisions for the wildfly directory
> - Take ownership of the wildfly directory (recursively)
> - Disabled Windows User Account Control (UAC)
> - Run Eclipse as Admin
> Relates to:
> - JBIDE-18697
> - JBIDE-17545
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22075:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Confusing error message when trying to attach remote debugger to OS app run in debug mode
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: debugging, openshift_v3
> Fix For: 4.6.x
>
> Attachments: debug-button-toolbar.png, error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, launch-debug-no-error.mov, remote-debugger-already-launched.png
>
>
> If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically.
> If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message
> When I am trying to run remote debugging of an application on OpenShift I get following error
> !!error-in-launching-remote-debugger.png! !
> {code}
> Failed to connect to remote VM
> com.sun.jdi.connect.spi.ClosedConnectionException
> at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
> at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
> at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *Steps to reproduce:*
> ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace.
> EXEC: Select "Restart in Debug" in context menu of server adapter.
> ASSERT: Server adapter is in state debugging ("[Debugging, Started]").
> EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging.
> RESULT: Error is shown.
> EXPECTED RESULT: The error message should tell you that there already is an instance running.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-21983) RuntimeException when trying to see Docker containers/images
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21983?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21983:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> RuntimeException when trying to see Docker containers/images
> ------------------------------------------------------------
>
> Key: JBIDE-21983
> URL: https://issues.jboss.org/browse/JBIDE-21983
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.6.x
>
>
> 1. CDK sever adapter -> Show In -> Docker Explorer
> 2. Unfold Containers or Images of the rhel-ose CDK Server:
> {code}
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered
> at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:152)
> at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120)
> at javax.ws.rs.core.UriBuilder.newInstance(UriBuilder.java:95)
> at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:106)
> at org.glassfish.jersey.client.JerseyWebTarget.<init>(JerseyWebTarget.java:82)
> at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:192)
> at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:70)
> at com.spotify.docker.client.DefaultDockerClient.resource(DefaultDockerClient.java:1051)
> at com.spotify.docker.client.DefaultDockerClient.listImages(DefaultDockerClient.java:320)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:787)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$5.run(DockerExplorerContentProvider.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered
> at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:122)
> at javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:225)
> at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:135)
> ... 12 more
> Caused by: java.lang.IllegalStateException: No generator was provided and there is no default generator registered
> at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.internalCreate(ServiceLocatorFactoryImpl.java:266)
> at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.create(ServiceLocatorFactoryImpl.java:247)
> at org.glassfish.jersey.internal.inject.Injections._createLocator(Injections.java:138)
> at org.glassfish.jersey.internal.inject.Injections.createLocator(Injections.java:109)
> at org.glassfish.jersey.internal.RuntimeDelegateImpl.<init>(RuntimeDelegateImpl.java:61)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:118)
> ... 14 more
> {code}
> Upstream issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=493904
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-21969) Show in Browser: route chooser should allow to user to choose route permanently
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21969?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21969:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Show in Browser: route chooser should allow to user to choose route permanently
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21969
> URL: https://issues.jboss.org/browse/JBIDE-21969
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.x
>
> Attachments: route-chooser.png
>
>
> steps to reproduce:
> # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace
> # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project)
> # EXEC: launch New OpenShift 3 Server Adapter wizard
> # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected)
> # EXEC: create the adapter by picking service, local project etc.
> # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser
> # ASSERT: Route chooser shows up (since there are several routes available)
> Result:
> There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project)
> !route-chooser.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22382:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Use different icons for EAP server and Red Hat Central
> ------------------------------------------------------
>
> Key: JBIDE-22382
> URL: https://issues.jboss.org/browse/JBIDE-22382
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Priority: Minor
> Fix For: 4.6.x
>
> Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png
>
>
> If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months