[JBoss JIRA] (JBIDE-23049) Error in org.jboss.tools.common.mylyn after installing JBossTools in Eclipse Neon.1 RC2
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23049?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23049:
------------------------------------
This is caused by the Bugzilla Mylyn connector daemon being absent. Installing it removes the messages. But I tried on Devstudio 10.1.0.GA, it has not Mylyn connectors and I can't see the message. Checked the Mylyn code and it does not seem to have been modified. Maybe related to bundle start ordering (which may cause the message not to be logged). Worth trying on Neon.0
> Error in org.jboss.tools.common.mylyn after installing JBossTools in Eclipse Neon.1 RC2
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23049
> URL: https://issues.jboss.org/browse/JBIDE-23049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.4.1.Final
> Environment: Eclipse SDK
> Version: Neon.1 (4.6.1)
> Build id: M20160824-0059
> JBoss Tools from update site:
> http://download.jboss.org/jbosstools/neon/snapshots/updates/
> org.jboss.tools.common.mylyn:
> 3.8.1.v20160607-2053
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Fix For: 4.4.2.AM1
>
>
> An error is shown in error log after installing JBoss Tools in Eclipse Neon.1 RC2:
> {code:java}
> Unexpected error while loading repository template extensions
> Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'bugzilla'
> {code}
> Stacktrace:
> {code:java}
> An exception stack trace is not available.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22999) Red Hat Central Rebranding
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22999?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22999:
-------------------------------------
Will the issue re: icons in JBIDE-22382 be addressed here? Or not?
> Red Hat Central Rebranding
> --------------------------
>
> Key: JBIDE-22999
> URL: https://issues.jboss.org/browse/JBIDE-22999
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Fix For: 4.4.x
>
> Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png, tools_rebrand_r1v2.png, tools_rebrand_r1v3.png
>
>
> Quoting [~james.cobb], from JBIDE-22382
> {quote}
> I've pulled in the branding fro RHD into this IDE panel.
> 1. I've opted to use colors verses an grey monotones
> 2. I've used Red Hat icons from the icon set
> Thoughts?
> {quote}
> !tools_rebrand.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23050) Exception in Tools.findFirstValidVMInstall
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23050?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23050:
-------------------------------------
The first call to this method was always causing a small one-time cycle and always logging an error. The loading of IVMInstalls would cause a property listener to attempt the same call again.
The workflow has been cleaned up to only add listeners after the workspace and Tools class have properly initialized.
Messaging has also been changed to be more clear and up-to-date, as it referenced a non-existent preference page.
> Exception in Tools.findFirstValidVMInstall
> ------------------------------------------
>
> Key: JBIDE-23050
> URL: https://issues.jboss.org/browse/JBIDE-23050
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.4.0.Alpha1
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: <no message>
> {noformat}
> java.lang.Exception: null
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:267)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:424)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:409)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:125)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:100)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:93)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:80)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:71)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.propertyChange(RemoteDebugActivator.java:248)
> at org.eclipse.core.runtime.Preferences$1.run(Preferences.java:510)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.runtime.Preferences.firePropertyChangeEvent(Preferences.java:513)
> at org.eclipse.core.internal.preferences.legacy.PreferenceForwarder.preferenceChange(PreferenceForwarder.java:116)
> at org.eclipse.core.internal.preferences.EclipsePreferences$2.run(EclipsePreferences.java:848)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.preferences.EclipsePreferences.firePreferenceEvent(EclipsePreferences.java:851)
> at org.eclipse.core.internal.preferences.EclipsePreferences.put(EclipsePreferences.java:863)
> at org.eclipse.jdt.launching.JavaRuntime.initializeVMs(JavaRuntime.java:2769)
> at org.eclipse.jdt.launching.JavaRuntime.getVMInstallTypes(JavaRuntime.java:539)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getAllVMInstalls(Tools.java:183)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getAllCompatibleInstalls(Tools.java:214)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:257)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:424)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:409)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:125)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:100)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:93)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:80)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:71)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(null:-1)
> at java.util.TimerThread.run(null:-1)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.0.v20150405-1723 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 |
> | org.eclipse.jdt.core | 3.12.0.v20160516-2131 | 3.12.0.v20160516-2131 |
> | org.eclipse.jdt.debug.ui | 3.7.101.v20160203-1236 | 3.7.200.v20160423-1519 |
> | org.eclipse.jdt.launching | 3.8.0.v20150527-0946 | 3.8.100.v20160505-0636 |
> | org.eclipse.jdt.ui | 3.12.0.v20160525-1829 | 3.12.0.v20160525-1829 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.m2e.core | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.core.ui | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.jdt | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.pde.core | 3.11.0.v20160510-1223 | 3.11.0.v20160510-1223 |
> | org.eclipse.pde.ui | 3.9.0.v20160525-1830 | 3.9.0.v20160525-1830 |
> | org.eclipse.swt | 3.104.0.v20150528-0211 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.common.jdt.debug | 3.7.0.CR1-v20150915-2036-B30 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.jdt.debug.ui | 3.7.0.CR1-v20150915-2036-B30 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.jmx.jvmmonitor.tools | 1.7.1.Final-v20160409-0826-B118 | 1.8.0.Final-v20160614-2020-B9 |
> Operating Systems:
> | Linux | 2.6.32.22 | 4.6.4.fc24 |
> | MacOSX | 10.11.5 | 10.11.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57001066e4b08ccb7b...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23050) Exception in Tools.findFirstValidVMInstall
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23050?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-23050.
---------------------------------
Resolution: Done
Fixed
> Exception in Tools.findFirstValidVMInstall
> ------------------------------------------
>
> Key: JBIDE-23050
> URL: https://issues.jboss.org/browse/JBIDE-23050
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.4.0.Alpha1
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: <no message>
> {noformat}
> java.lang.Exception: null
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:267)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:424)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:409)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:125)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:100)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:93)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:80)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:71)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.propertyChange(RemoteDebugActivator.java:248)
> at org.eclipse.core.runtime.Preferences$1.run(Preferences.java:510)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.runtime.Preferences.firePropertyChangeEvent(Preferences.java:513)
> at org.eclipse.core.internal.preferences.legacy.PreferenceForwarder.preferenceChange(PreferenceForwarder.java:116)
> at org.eclipse.core.internal.preferences.EclipsePreferences$2.run(EclipsePreferences.java:848)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.preferences.EclipsePreferences.firePreferenceEvent(EclipsePreferences.java:851)
> at org.eclipse.core.internal.preferences.EclipsePreferences.put(EclipsePreferences.java:863)
> at org.eclipse.jdt.launching.JavaRuntime.initializeVMs(JavaRuntime.java:2769)
> at org.eclipse.jdt.launching.JavaRuntime.getVMInstallTypes(JavaRuntime.java:539)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getAllVMInstalls(Tools.java:183)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getAllCompatibleInstalls(Tools.java:214)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:257)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:424)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:409)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:125)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:100)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:93)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:80)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:71)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(null:-1)
> at java.util.TimerThread.run(null:-1)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.0.v20150405-1723 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 |
> | org.eclipse.jdt.core | 3.12.0.v20160516-2131 | 3.12.0.v20160516-2131 |
> | org.eclipse.jdt.debug.ui | 3.7.101.v20160203-1236 | 3.7.200.v20160423-1519 |
> | org.eclipse.jdt.launching | 3.8.0.v20150527-0946 | 3.8.100.v20160505-0636 |
> | org.eclipse.jdt.ui | 3.12.0.v20160525-1829 | 3.12.0.v20160525-1829 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.m2e.core | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.core.ui | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.jdt | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.pde.core | 3.11.0.v20160510-1223 | 3.11.0.v20160510-1223 |
> | org.eclipse.pde.ui | 3.9.0.v20160525-1830 | 3.9.0.v20160525-1830 |
> | org.eclipse.swt | 3.104.0.v20150528-0211 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.common.jdt.debug | 3.7.0.CR1-v20150915-2036-B30 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.jdt.debug.ui | 3.7.0.CR1-v20150915-2036-B30 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.jmx.jvmmonitor.tools | 1.7.1.Final-v20160409-0826-B118 | 1.8.0.Final-v20160614-2020-B9 |
> Operating Systems:
> | Linux | 2.6.32.22 | 4.6.4.fc24 |
> | MacOSX | 10.11.5 | 10.11.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57001066e4b08ccb7b...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22879) JavaEE jars files are built with another java version than used for compilation
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22879?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22879:
-------------------------------------
Unfortunately, this will remain targeted to later, since it is an upstream bug. Please see the linked bugzilla if you wish to provide further input there.
It's worth noting, however, that this bug is almost entirely cosmetic. We recognize that people may depend on the manifest flag for debugging purposes, however, exporting and publishing of projects is generally not intended for production purposes. These are development tools, meant to speed up rapid development and testing on various application servers.
For real deployments, it's suggested to use your actual maven build for repeatable and accurate results.
> JavaEE jars files are built with another java version than used for compilation
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22879
> URL: https://issues.jboss.org/browse/JBIDE-22879
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Final, 4.4.0.Final
> Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime.
> Reporter: Mikhail Kalkov
> Assignee: Rob Stryker
> Fix For: LATER
>
> Attachments: test-projects.zip
>
>
> I have installed system-wide JRE 8 in order to run all java applications with it. At the same time, out target platform is still based on Java 7 and that's why I've also downloaded JDK 7 and set JAVA_HOME path to it.
> When I build test-ejb project from attached zip file on command line, maven both compiles and packages it with JDK 7 obtained from JAVA_HOME. When I build the same project with JBoss Developer Studio which was configured via Window > Preferences > Java > Installed JREs to use JDK 7 by default, class files get version 51 (java 7) but Build-Jdk stanza in MANIFEST.MF is set to 1.8.0_102 instead of 1.7. I've also observed that test-ear project is also packaged with Java 8 instead of Java 7.
> This is not a big issue but is a bit worrying since for example jar tool from JDK 8 may contains bugfixes not present in JDK 7. This also makes me think that other tools may be fetched from wrong JDK version. Finally, I'm not even sure whether this is a JBoss Tools, Eclipse WTP or Eclipse M2E issue but it is clearly present in the latest stock version of JBoss Developer Studio.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months