[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21674:
----------------------------------------
As the author of this feature, I'm very happy to see that you like and trust it that much to really enable it by default in JBoss Tools ;)
A very quick overlook makes it seems OK to me.
However, is this something we want in JBoss Tools (that will change behaviour of all Eclipse IDE user that have JBoss Tools installed), or is it something we would just push in JBDS package? Can you please bring this question to the jbosstools-dev mailing-list with a poll, and a reminder explaining how they can test the Hierarchical view locally?
> Enable hierarchical view by default in Project Explorer
> -------------------------------------------------------
>
> Key: JBIDE-21674
> URL: https://issues.jboss.org/browse/JBIDE-21674
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Reporter: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
>
> Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects).
> After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-21674:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
> Enable hierarchical view by default in Project Explorer
> -------------------------------------------------------
>
> Key: JBIDE-21674
> URL: https://issues.jboss.org/browse/JBIDE-21674
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Reporter: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
>
> Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects).
> After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBTIS-554) Correct typo in earlyaccess devstudio plugin.xml
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-554:
--------------------------------
Summary: Correct typo in earlyaccess devstudio plugin.xml
Key: JBTIS-554
URL: https://issues.jboss.org/browse/JBTIS-554
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 9.0.0.Beta1
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 9.0.0.Beta1
SOA legacy connector descriptor is accidentally outside the extension
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21674:
-----------------------------------------------
[~xcoulon] [~mickael_istria] please take a look at the pull request.
> Enable hierarchical view by default in Project Explorer
> -------------------------------------------------------
>
> Key: JBIDE-21674
> URL: https://issues.jboss.org/browse/JBIDE-21674
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Reporter: Xavier Coulon
>
> Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects).
> After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21670) Remove ImageStreamTag from WatchManager
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21670?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-21670:
----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/957 (was: https://github.com/jbosstools/jbosstools-openshift/pull/955)
> Remove ImageStreamTag from WatchManager
> ---------------------------------------
>
> Key: JBIDE-21670
> URL: https://issues.jboss.org/browse/JBIDE-21670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
>
> Watch of ImageStreamTags is unsupported by the server and causes:
> {{
> [DEBUG] 2016-02-09 10:39:33,901 com.openshift.internal.restclient.WatchClient - WatchSocket Error
> org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314)
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241)
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163)
> at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
> [DEBUG] 2016-02-09 10:39:33,902 com.openshift.internal.restclient.WatchClient - WatchSocket Error
> org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314)
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241)
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163)
> at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
> }}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month