[JBoss JIRA] (JBIDE-24246) Add Fuse Tooling dependencies to JBT/devstudio Oxygen-based TPs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24246?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24246:
------------------------------------
Further discussion has resulted in the need to have a .target file that includes a partial collection of the JBT plugins too:
{code}
org.jboss.ide.eclipse.as.classpath.core
org.jboss.ide.eclipse.as.dmr
org.jboss.ide.eclipse.as.wtp.core
org.jboss.ide.eclipse.as.wtp.ui
org.jboss.tools.as.runtimes.integration
org.jboss.tools.as.test.core
org.jboss.tools.common
org.jboss.tools.common.jdt.debug
org.jboss.tools.common.validation
org.jboss.tools.foundation.core
org.jboss.tools.foundation.ui
org.jboss.tools.jmx.core
org.jboss.tools.jmx.ui
org.jboss.tools.jmx.jvmmonitor.ui
org.jboss.tools.jmx.jvmmonitor.core
org.jboss.tools.jmx.local
org.jboss.tools.maven.core
org.jboss.tools.runtime.core
org.jboss.tools.stacks.core
org.jboss.tools.usage{code}
Is this the complete list of deps, [~rob.stryker][~lhein] ?
> Add Fuse Tooling dependencies to JBT/devstudio Oxygen-based TPs
> ---------------------------------------------------------------
>
> Key: JBIDE-24246
> URL: https://issues.jboss.org/browse/JBIDE-24246
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: fuse-tooling, target-platform, updatesite
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Lars Heinemann
>
> Need a list of features/plugins to move from the JBTIS/JBDSIS target platforms to the JBT/devstudio target platforms.
> Affected files:
> * https://github.com/jbosstools/jbosstools-target-platforms/blob/4.70.x/jbo...
> * https://github.com/jbosstools/jbosstools-target-platforms/blob/4.70.x/jbd...
> Similar changes will also be needed in the JBTIS/devstudioIS target platforms once this content has moved. cc: [~pleacu]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (TOOLSDOC-456) Generate Release Notes doc for JBDS 7.1.1.GA
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-456?page=com.atlassian.jira.plug... ]
Michelle Murray closed TOOLSDOC-456.
------------------------------------
> Generate Release Notes doc for JBDS 7.1.1.GA
> --------------------------------------------
>
> Key: TOOLSDOC-456
> URL: https://issues.jboss.org/browse/TOOLSDOC-456
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Components: Release Notes
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Priority: Blocker
> Fix For: 4.1.2
>
> Original Estimate: 6 hours
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> Doc sections:
> 1. Introduction to Red Hat JBoss Developer Studio
> 1.1. About Red Hat JBoss Developer Studio
> 1.2. Use Cases of JBoss Developer Studio
> 2. About this Release
> 3. New Features
> 4. Resolved Issues
> 5. Known Issues
> 6. Apply this Release
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBIDE-24271) Runtime search dialog has too many labels
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24271?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-24271:
-----------------------------------
Fix Version/s: 4.4.4.AM3
Assignee: Rob Stryker
Resolution: Done
Pushed to master / maint
> Runtime search dialog has too many labels
> -----------------------------------------
>
> Key: JBIDE-24271
> URL: https://issues.jboss.org/browse/JBIDE-24271
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.4.4.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM3
>
> Attachments: JBIDE-24271.png
>
>
> WHile investigating JBIDE-24230 it became clear to me the runtime search dialog had very weird things going on. There were clearly too many labels and it made no sense what exactly was going on. My attempts to update one label were in fact updating a different label. It turns out, multiple labels were created and stored in the same variable after some they had values set on them. This led to a very weird appearance.
> Screenshot to come.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23869:
-------------------------------------
upstream issue
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.4.4.AM3
>
> Attachments: image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-23869:
--------------------------------
Sprint: devex #128 February 2017, devex #130 April 2017 (was: devex #128 February 2017)
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.4.4.AM3
>
> Attachments: image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months