January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19074) For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [VPE]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19074?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-19074. ------------------------------------------ Resolution: Done VPE is 3.7.0 now > For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [VPE] > ------------------------------------------------------------------------------- > > Key: JBIDE-19074 > URL: https://issues.jboss.org/browse/JBIDE-19074 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Alpha1 > > > For JBIDE 4.3.0.Alpha1 [VPE]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19091) Cordovasim: Livereload stop working after pressing 'Refresh' button from the Platform toolbar

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19091?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19091: -------------------------------- Workaround Description: Reinit livereload (disable and enable again) > Cordovasim: Livereload stop working after pressing 'Refresh' button from the Platform toolbar > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-19091 > URL: https://issues.jboss.org/browse/JBIDE-19091 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.2.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > > Both SWT and JavaFX are affected. > Stack trace for javaFx web engine: > {code} > Exception in thread "JavaFX Application Thread" org.eclipse.swt.SWTException: Widget is disposed > at org.eclipse.swt.SWT.error(SWT.java:4441) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.SWT.error(SWT.java:4327) > at org.eclipse.swt.widgets.Widget.error(Widget.java:476) > at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:348) > at org.eclipse.swt.widgets.Control.forceFocus(Control.java:1075) > at org.jboss.tools.vpe.cordovasim.events.RippleInjector.inject(RippleInjector.java:68) > at org.jboss.tools.vpe.cordovasim.events.RippleInjector.access$1(RippleInjector.java:55) > at org.jboss.tools.vpe.cordovasim.events.RippleInjector$1.run(RippleInjector.java:44) > at com.sun.javafx.application.PlatformImpl$6$1.run(PlatformImpl.java:301) > at com.sun.javafx.application.PlatformImpl$6$1.run(PlatformImpl.java:298) > at java.security.AccessController.doPrivileged(Native Method) > at com.sun.javafx.application.PlatformImpl$6.run(PlatformImpl.java:298) > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) > at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:114) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:91) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17315) Investigate org.eclipse.jst.server.core.serverProfilers ext.pt.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17315?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17315. --------------------------------- Assignee: Rob Stryker Resolution: Rejected The extension point doesn't seem useful for us. We don't need the agent jar to properly profile the server (which we can do via simple jmx requests for the most part, unless we need instrumentation). We also don't need to customize any launch args or do anything else. Basically, jvmmonitor provides it all 100% for free. > Investigate org.eclipse.jst.server.core.serverProfilers ext.pt. > --------------------------------------------------------------- > > Key: JBIDE-17315 > URL: https://issues.jboss.org/browse/JBIDE-17315 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx, server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha1 > > > The extension point provided in upstream WTP for declaring server profilers is called org.eclipse.jst.server.core.serverProfilers. > The primary function of the implementation class org.eclipse.jst.server.core.ServerProfilerDelegate is adding arguments to launches in order to enable the proper agent. > If used with other profilers, arguments may need to be appended to the launch in order to enable the profiling. > If used via JVM Monitor, though, no real arguments are required, as JVM Monitor can install its agent directly without any changes on the part of the launch. > However, if we assume that JBIDE-17313 is solved and we can detect the duplicates, we could prevent the agent from being installed. We would be preventing the auto-detector from being added to the view. On our server startup, then, and only when profiling is enabled, we would connect the underlying jvmmonitor's agent and allow profiling. > This could be accomplished via a custom attribute on the launch configuration which could be flipped by the user via a radio / check button to enable or disable the profiler. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19093) Server adapter jmx integration properties view updating too fast, ignoring setting

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19093?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-19093: ----------------------------------- Assignee: Rob Stryker Resolution: Done pushed to master > Server adapter jmx integration properties view updating too fast, ignoring setting > ---------------------------------------------------------------------------------- > > Key: JBIDE-19093 > URL: https://issues.jboss.org/browse/JBIDE-19093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha1 > > > When starting a WF 8.2 (or other) server, the new process will appear in two spots in the JMX view: detected processes, and servers. When selecting the entry under 'servers', right-click, click connect, and open properties view, you can browse jmx tree or get memory usage stats. > The various charts are updating 500ms apart. If you check window -> preferences -> jvm monitor, you'll see the setting is 5000 ms, not 500. This specific jmx node is not respecting the global setting. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19093) Server adapter jmx integration properties view updating too fast, ignoring setting

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19093?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19093: -------------------------------- Fix Version/s: 4.3.0.Alpha1 > Server adapter jmx integration properties view updating too fast, ignoring setting > ---------------------------------------------------------------------------------- > > Key: JBIDE-19093 > URL: https://issues.jboss.org/browse/JBIDE-19093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, server > Reporter: Rob Stryker > Fix For: 4.3.0.Alpha1 > > > When starting a WF 8.2 (or other) server, the new process will appear in two spots in the JMX view: detected processes, and servers. When selecting the entry under 'servers', right-click, click connect, and open properties view, you can browse jmx tree or get memory usage stats. > The various charts are updating 500ms apart. If you check window -> preferences -> jvm monitor, you'll see the setting is 5000 ms, not 500. This specific jmx node is not respecting the global setting. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17666) memory usage keeps growing even on processes that does nothing

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17666?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17666. --------------------------------- Assignee: Rob Stryker Resolution: Rejected I've compared the memory usage in the properties view vs how it behaves in the web UI. http://localhost:9990/console/App.html#vm They're identical. Memory usage for wf8.2 goes up to around 150mb slowly as the server starts up services and things. It takes a few minutes. After around 5 or 10 minutes, the server does a garbage collection and moves back down to about 50mb. The eclipse UI is not attaching the agent, and so is just executing various jmx requests to update the histograms. I did find another small bug which I'll open a new jira for. https://issues.jboss.org/browse/JBIDE-19093 > memory usage keeps growing even on processes that does nothing > -------------------------------------------------------------- > > Key: JBIDE-17666 > URL: https://issues.jboss.org/browse/JBIDE-17666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.x > > > I noticed that when enabling the timeline graphs the memory usage just seem to constantly increase with every poll. even for apps that does nothing. > Seems like we are not freeing memory in the agent or something ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19093) Server adapter jmx integration properties view updating too fast, ignoring setting

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-19093: ----------------------------------- Summary: Server adapter jmx integration properties view updating too fast, ignoring setting Key: JBIDE-19093 URL: https://issues.jboss.org/browse/JBIDE-19093 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx, server Reporter: Rob Stryker When starting a WF 8.2 (or other) server, the new process will appear in two spots in the JMX view: detected processes, and servers. When selecting the entry under 'servers', right-click, click connect, and open properties view, you can browse jmx tree or get memory usage stats. The various charts are updating 500ms apart. If you check window -> preferences -> jvm monitor, you'll see the setting is 5000 ms, not 500. This specific jmx node is not respecting the global setting. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19042) Cannot login via Openshift Explorer on Openshift "Can not verify User"

by Stylianos Koussouris (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19042?page=com.atlassian.jira.plugi... ] Stylianos Koussouris resolved JBIDE-19042. ------------------------------------------ Release Notes Text: Tried it on 8.0.0 and woks, closing Resolution: Done > Cannot login via Openshift Explorer on Openshift "Can not verify User" > ---------------------------------------------------------------------- > > Key: JBIDE-19042 > URL: https://issues.jboss.org/browse/JBIDE-19042 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.x, 4.2.x > Environment: Win7, jdk7, Openshift Online > Reporter: Stylianos Koussouris > Assignee: Andre Dietisheim > Priority: Critical > Attachments: CannotVerifyUser.JPG > > > Trying to connect via Openshift explorer to Openshift Online, the credentials are correct and working from the Web UI, I receive > Unknown error, can not verify user > and in the log > !ENTRY org.jboss.tools.openshift.express.ui 4 4 2015-01-15 15:01:37.848 > !MESSAGE > !STACK 0 > java.lang.NullPointerException > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:113) > at com.openshift.internal.client.RestService.request(RestService.java:151) > at com.openshift.internal.client.RestService.request(RestService.java:107) > at com.openshift.internal.client.RestService.request(RestService.java:100) > at com.openshift.internal.client.RestService.request(RestService.java:81) > at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:134) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:103) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199) > at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:252) > at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPage$ConnectJob.run(ConnectionWizardPage.java:474) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Similar Issue reported: https://forums.openshift.com/unknown-error-can-not-verify-user -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19090) jbosstools-maven-plugins requires Java 7 but compiles to Java 8 requirement?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19090?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19090: --------------------------------------------- opened JBIDE-19092 since we cannot use software with such license if that is really what it states. sorry. > jbosstools-maven-plugins requires Java 7 but compiles to Java 8 requirement? > ---------------------------------------------------------------------------- > > Key: JBIDE-19090 > URL: https://issues.jboss.org/browse/JBIDE-19090 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > Parent pom compilation is now failing if run with JDK 7 (but works w/ JDK 8): > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build.parent_master/419/} > [8mha:AAAAYB+LCAAAAAAAAP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEuhYV5Rf55ZekOlc7RKnPKH7IxMBQUcQgBdWQnJ9XnJ+TqucMoUEKGSCAEaSwAACsNFCqYAAAAA== > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site (generate-full-site) on project > parent: Execution generate-full-site of goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site failed: An API > incompatibility was encountered while executing org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site: > java.lang.UnsupportedClassVersionError: org/json/JSONObject : Unsupported major.minor version 52.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19092) jbosstools-maven-plugins uses non-opensource json library

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-19092: ------------------------------------------- Summary: jbosstools-maven-plugins uses non-opensource json library Key: JBIDE-19092 URL: https://issues.jboss.org/browse/JBIDE-19092 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Max Rydahl Andersen Priority: Critical if JBIDE-19090 is correct the maven plugins uses json library that is under a non-opensource license and thus we need to upgrade to a library version that has proper license or move to different library. i.e. dmr has basic read/write of json support and used in many places of jbosstools - would that work ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015