[JBoss JIRA] (JBTIS-990) JBTIS TP update - JBT 4.61.0/ 4.4.2
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-990?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-990:
-----------------------------
Description:
*Reason:* Update to 4.61.0/ 4.4.0 parent pom
*Project page/sources:*
*Version:* 4.61.0.Final-SNAPSHOT
*License and owner:* EPL
*Original p2 repo:* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:* Devstudio IS
*Include in JBDS:* Yes (DevstudioIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
target-platform.p2diff:
< org.jboss.tools.maven.jsf [1.3.1.20160831-1005]
< org.jboss.tools.maven.jpa [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.feature.feature.jar [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jsf.feature.feature.jar [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jaxrs.feature.feature.jar [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jpa.feature.feature.jar [1.3.1.20160831-1005]
< org.maven.ide.eclipse.wtp [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jaxrs.feature.feature.group [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jaxrs [1.3.1.20160831-1005]
< org.jboss.tools.maven.jaxrs [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jsf.feature.feature.group [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jpa.feature.feature.group [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.overlay.ui [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.overlay [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jpa [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jsf [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.feature.feature.group [1.3.1.20160831-1005]
> org.eclipse.birt.report.data.oda.jdbc.ui [4.6.0.v201602022206]
> org.eclipse.birt.data.oda.mongodb.ui [4.6.0.v201602022206]
> org.eclipse.birt.core [4.6.0.v201602022206]
> org.eclipse.birt.report.data.bidi.utils.ui [4.6.0.v201602022206]
> org.eclipse.birt.report.data.oda.hive.ui [4.6.0.v201602022206]
> org.eclipse.birt.report.data.oda.jdbc [4.6.0.v201602022206]
> org.apache.poi [3.9.0.v201405241750]
> org.eclipse.birt.report.data.oda.hive [4.6.0.v201602022206]
> org.eclipse.birt.report.data.bidi.utils [4.6.0.v201602022206]
> org.eclipse.core.runtime.compatibility [3.2.300.v20150423-0821]
> org.eclipse.birt.data.oda.mongodb [4.6.0.v201602022206]
> org.eclipse.orbit.mongodb [2.10.1.v20130422-1135]
=== Summary ===
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.0.Fi... contains 18 unique IUs
file:/home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 12 unique IUs
target-platform-ea.p2diff:
< org.jboss.tools.maven.jsf [1.3.1.20160831-1005]
< org.jboss.tools.maven.jpa [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.feature.feature.jar [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jsf.feature.feature.jar [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jaxrs.feature.feature.jar [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jpa.feature.feature.jar [1.3.1.20160831-1005]
< org.maven.ide.eclipse.wtp [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jaxrs.feature.feature.group [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jaxrs [1.3.1.20160831-1005]
< org.jboss.tools.maven.jaxrs [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jsf.feature.feature.group [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jpa.feature.feature.group [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.overlay.ui [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.overlay [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jpa [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.jsf [1.3.1.20160831-1005]
< org.eclipse.m2e.wtp.feature.feature.group [1.3.1.20160831-1005]
=== Summary ===
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.0.Fi... contains 18 unique IUs
file:/home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 0 unique IUs
{code}
was:
*Reason:* Update to 4.61.0/ 4.4.0 parent pom
*Project page/sources:*
*Version:* 4.61.0.Final-SNAPSHOT
*License and owner:* EPL
*Original p2 repo:* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:* Devstudio IS
*Include in JBDS:* Yes (DevstudioIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
{code}
> JBTIS TP update - JBT 4.61.0/ 4.4.2
> -----------------------------------
>
> Key: JBTIS-990
> URL: https://issues.jboss.org/browse/JBTIS-990
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> *Reason:* Update to 4.61.0/ 4.4.0 parent pom
> *Project page/sources:*
> *Version:* 4.61.0.Final-SNAPSHOT
> *License and owner:* EPL
> *Original p2 repo:* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* Devstudio IS
> *Include in JBDS:* Yes (DevstudioIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> target-platform.p2diff:
> < org.jboss.tools.maven.jsf [1.3.1.20160831-1005]
> < org.jboss.tools.maven.jpa [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa.feature.feature.jar [1.3.1.20160831-1005]
> < org.maven.ide.eclipse.wtp [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs [1.3.1.20160831-1005]
> < org.jboss.tools.maven.jaxrs [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.overlay.ui [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.overlay [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.feature.feature.group [1.3.1.20160831-1005]
> > org.eclipse.birt.report.data.oda.jdbc.ui [4.6.0.v201602022206]
> > org.eclipse.birt.data.oda.mongodb.ui [4.6.0.v201602022206]
> > org.eclipse.birt.core [4.6.0.v201602022206]
> > org.eclipse.birt.report.data.bidi.utils.ui [4.6.0.v201602022206]
> > org.eclipse.birt.report.data.oda.hive.ui [4.6.0.v201602022206]
> > org.eclipse.birt.report.data.oda.jdbc [4.6.0.v201602022206]
> > org.apache.poi [3.9.0.v201405241750]
> > org.eclipse.birt.report.data.oda.hive [4.6.0.v201602022206]
> > org.eclipse.birt.report.data.bidi.utils [4.6.0.v201602022206]
> > org.eclipse.core.runtime.compatibility [3.2.300.v20150423-0821]
> > org.eclipse.birt.data.oda.mongodb [4.6.0.v201602022206]
> > org.eclipse.orbit.mongodb [2.10.1.v20130422-1135]
> === Summary ===
> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.0.Fi... contains 18 unique IUs
> file:/home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 12 unique IUs
> target-platform-ea.p2diff:
> < org.jboss.tools.maven.jsf [1.3.1.20160831-1005]
> < org.jboss.tools.maven.jpa [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa.feature.feature.jar [1.3.1.20160831-1005]
> < org.maven.ide.eclipse.wtp [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs [1.3.1.20160831-1005]
> < org.jboss.tools.maven.jaxrs [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.overlay.ui [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.overlay [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.feature.feature.group [1.3.1.20160831-1005]
> === Summary ===
> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.0.Fi... contains 18 unique IUs
> file:/home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 0 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23502) Integration tests: ConnectionPropertiesTest cannot be run individually in JBT
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23502?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23502:
-------------------------------------
Labels: integration_tests properties (was: )
> Integration tests: ConnectionPropertiesTest cannot be run individually in JBT
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23502
> URL: https://issues.jboss.org/browse/JBIDE-23502
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Labels: integration_tests, properties
>
> ConnectionPropertiesTest cannot be run individually. It requires the default connection to exist.
> Furhtermore it will fail if run in JBT (not in Devstudio) because the bot test wont find any content in the Properties view. This is because JBT by default has the OpenShift Explorer and the properties view sitting in the same stacked view. In this setup there's no selection in the explorer that can be displayed in the Properties view.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23502) Integration tests: ConnectionPropertiesTest cannot be run individually in JBT
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-23502:
----------------------------------------
Summary: Integration tests: ConnectionPropertiesTest cannot be run individually in JBT
Key: JBIDE-23502
URL: https://issues.jboss.org/browse/JBIDE-23502
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.2.AM3
Reporter: Andre Dietisheim
ConnectionPropertiesTest cannot be run individually. It requires the default connection to exist.
Furhtermore it will fail if run in JBT (not in Devstudio) because the bot test wont find any content in the Properties view. This is because JBT by default has the OpenShift Explorer and the properties view sitting in the same stacked view. In this setup there's no selection in the explorer that can be displayed in the Properties view.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4180) ClassNotFoundException thrown on devstudio start up
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4180?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4180:
--------------------------------------
cc: [~mhusnain], [~supriya.bharadwaj].
> ClassNotFoundException thrown on devstudio start up
> ---------------------------------------------------
>
> Key: JBDS-4180
> URL: https://issues.jboss.org/browse/JBDS-4180
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: foundation, upstream
> Affects Versions: 10.2.0.GA
> Environment: Fedora 24,
> openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Fix For: 10.x
>
>
> When starting latest DevStudio 10.2.0.GA (build ID GA-v20161116-0039-B6472) I get following error in console output
> {code}
> SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> Noop constructor
> java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.validateClassPathAndLibraryPath(Tools.java:365)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:115)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73)
> 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(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:525)
> 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(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {code}
> problem is with openjdk version. With the lates 1.8.0_111 it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-22810:
------------------------------------
That is not related to platforms. On my Win10 machine, I had immediatly the problem with DevStudio 10.2.0.AM3 and had to close some windows/perspectives on my dev env. So I think it is more related to the environment than the platform
> OpenShift Explorer: empty at start
> ----------------------------------
>
> Key: JBIDE-22810
> URL: https://issues.jboss.org/browse/JBIDE-22810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Environment: windows
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v3, windows
> Fix For: 4.4.2.Final
>
> Attachments: EmptyViewAtStart.png
>
>
> When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections.
> I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4180) ClassNotFoundException thrown on devstudio start up
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4180?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov edited comment on JBDS-4180 at 11/21/16 11:07 AM:
-----------------------------------------------------------------
I looked closer at it. Well, once I updated on my Fedora 24 openjdk, I was not able to reproduce with latest available openjdk from fedora repos and there was no way back because the openjdk 1.8.0_102 was from previous Fedora (I was upgrading Fedora) and openjdk has not been updated. So it is really edge case and I think it would be good enough to have it documented in some form. This includes JBDS-4179 as well as JBDS-4181
was (Author: mlabuda):
I looked closer at it. Well, once I updated on my Fedora 24 openjdk, I was not able to reproduce with latest available openjdk from fedora repos and there was no way back because the openjdk 1.8.0_102 was from previous Fedora (I was upgrading Fedora) and openjdk has not been updated. So it is really edge case and I think it would be good enough to have it documented in some form. This includes JBIDE-4179 as well as JBIDE-4181
> ClassNotFoundException thrown on devstudio start up
> ---------------------------------------------------
>
> Key: JBDS-4180
> URL: https://issues.jboss.org/browse/JBDS-4180
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: foundation, upstream
> Affects Versions: 10.2.0.GA
> Environment: Fedora 24,
> openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Fix For: 10.x
>
>
> When starting latest DevStudio 10.2.0.GA (build ID GA-v20161116-0039-B6472) I get following error in console output
> {code}
> SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> Noop constructor
> java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.validateClassPathAndLibraryPath(Tools.java:365)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:115)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73)
> 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(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:525)
> 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(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {code}
> problem is with openjdk version. With the lates 1.8.0_111 it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23184) Add Capability to Watch Projects
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23184?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23184:
------------------------------------------
What is the status of this issue? As far as I can see [~mlabuda] found an issue where projects that are added or removed outside Eclipse wont trigger changes in Eclipse automatically. Is there anything else I am missing? If not, I suggest that we resolve this and open a new separate issue for this.
> Add Capability to Watch Projects
> --------------------------------
>
> Key: JBIDE-23184
> URL: https://issues.jboss.org/browse/JBIDE-23184
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Jeff Cantrill
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.2.AM3
>
>
> Origin now allows watching of projects for adds and delete. Add capability to watch projects. Need to take into consideration how one might use the latest code against an older server version since older servers did not support project watch
> $ curl -k -H "Authorization: Bearer LU3A1EyTOdnRhkLqe8Gqkgk850eTNlljz18NwLA-108" https://192.168.1.13:8443/oapi/v1/projects?watch=true&&resourceVersion=
> {"type":"ADDED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","uid":"41f418fc-7ea3-11e6-803b-507b9dfa4ab3","resourceVersion":"942","creationTimestamp":"2016-09-19T19:57:13Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/requester":"developer","openshift.io/sa.scc.mcs":"s0:c7,c4","openshift.io/sa.scc.supplemental-groups":"1000050000/10000","openshift.io/sa.scc.uid-range":"1000050000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}}
> {"type":"DELETED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","creationTimestamp":null},"spec":{},"status":{}}}
> openshift-origin PR that made it available: https://github.com/openshift/origin/pull/6828
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22810:
------------------------------------------
[~jeffmaury] +1 for extension points, that's was the plan for quite some time now, but wasnt urgent enough to get priority over other issues.
But then I dont see how - if this is the cause - should behave differently on different platforms?
> OpenShift Explorer: empty at start
> ----------------------------------
>
> Key: JBIDE-22810
> URL: https://issues.jboss.org/browse/JBIDE-22810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Environment: windows
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v3, windows
> Fix For: 4.4.2.Final
>
> Attachments: EmptyViewAtStart.png
>
>
> When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections.
> I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4183) Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4183?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4183:
------------------------------------
I tried to verified this ticket in 10.2-0.20161121.0756. I am able to install *Maven Integration for Eclipse JDT APT (m2e-apt)* and restart eclipse without errors.
I also tried to verify this as Nick wrote in his guide but I have had problems here. Shoud this fix only solves problem with "Maven Integration for Eclipse JDT APT"? Is expected that I can't go throught all ten steps of Nick's guide without errors?
There are results of my attempt to do it as Nick wrote:
# install from latest rpm (/) (10.2-0.20161121.0756)
# Help > Install New > https://devstudio.redhat.com/10.0/snapshots/updates/ NOT from STABLE or Central (/)
# uncheck "group items by category" (/)
# select cordovasim feature (v20161115 or newer) (/)
# restart when prompted (/)
*no errors in the log*
# ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins
{code:java}
[lvalach@localhost ldd]$ ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins
total 1392
-rw-rw-r--. 1 lvalach lvalach 42200 Nov 21 13:17 org.eclipse.jetty.rewrite_9.3.9.v20160517.jar
-rw-rw-r--. 1 lvalach lvalach 216212 Nov 21 13:17 org.eclipse.thym.core_2.1.0.201611071511.jar
-rw-rw-r--. 1 lvalach lvalach 73577 Nov 21 13:17 org.jboss.tools.cordovasim_3.8.2.v20160920-1359.jar
-rw-rw-r--. 1 lvalach lvalach 86891 Nov 21 13:17 org.jboss.tools.cordovasim.eclipse_3.8.2.v20161115-2204.jar
-rw-rw-r--. 1 lvalach lvalach 996680 Nov 21 13:17 org.jboss.tools.cordovasim.ripple_3.8.2.v20160920-1359.jar
{code}
Should not see anything from java.servlet(.api)(/), org.apache.httpcomponents.httpclient(.cache)(/)
But will likely see org.slf4j.api 1.7.2 (x), which is probably OK as it's needed by other slf4j jars in the devstudio rpm install
7. install the rpm feature to update everything in devstudio to latest snapshot version from https://devstudio.redhat.com/10.0/snapshots/updates/
Then I restarted eclipse and I got errors. I noticed the restart is not mentioned in the quide. Was it intended?
[^RPM_Fratures_and_restart.txt]
When I tried it without restart between steps 7 and 8. I got this output after eighth step:
{code}
[lvalach@localhost ldd]$ ls ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/{plugins,features} | egrep -v "org.jboss.tools|org.eclipse.thym|org.jboss.ide|hibernate|com.jboss.devstudio"
/home/lvalach/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/features:
org.eclipse.linuxtools.vagrant.feature_2.1.0.201609141916
/home/lvalach/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/plugins:
org.apache.commons.lang_2.6.0.v201404270220.jar
org.apache.xml.resolver_1.2.0.v201005080400.jar
org.apache.xml.serializer_2.7.1.v201005080400.jar
org.eclipse.jetty.rewrite_9.3.9.v20160517.jar
org.eclipse.linuxtools.vagrant.core_2.0.0.201609141916.jar
org.eclipse.linuxtools.vagrant.docs_2.0.0.201609141916.jar
org.eclipse.linuxtools.vagrant.ui_2.0.0.201609141916.jar
{code}
[^After step 8.txt]
There isn't org.slf4j.api package as we wanted.
> Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4183
> URL: https://issues.jboss.org/browse/JBDS-4183
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 10.2.0.GA
>
> Attachments: After step 8.txt, RPM_Fratures_and_restart.txt, install-thym.png, rh-eclipse46-devstudio10.2.log.20161116-1226_strict.txt
>
>
> Steps to repro:
> 1. install from latest rpm, eg., 10.2.0.20161116.1342.el7
> 2. open Central > Software/Update, scroll down until you find the *Maven Integration for Eclipse JDT APT (m2e-apt)* connector
> 3. Install it. When prompted to restart, shut down Eclipse and check in your ~/.eclipse folder:
> {code}
> $➔ ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/
> total 36K
> -rw-rw-r-- 1 nboldt nboldt 34K Nov 16 10:54 org.slf4j.api_1.7.2.v20121108-1250.jar
> {code}
> But this plugin is already installed here:
> {code}/opt/rh/rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar{code}
> So even though the connector install doesn't install any new m2e-apt stuff (it's already installed too):
> {code}
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.ui_1.3.0.201610261805.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.core_1.3.0.201610261805.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.maven.apt.feature_1.3.0.201610261805
> {code}
> ... the result of this install is to cause use constrain violations and break the devstudio install.
> A bigger problem occurs in JBDS-4150 when installing Thym or Aerogear features, since a second version of org.apache.httpcomponents.httpclient_4.3.6.v201511171540.jar is installed even though there's already one in the /opt/rh/ install footprint.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months