[JBoss JIRA] (JBIDE-19853) GTK3 (only): Erroneous labels in application wizard tree
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19853?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-19853.
----------------------------------
> GTK3 (only): Erroneous labels in application wizard tree
> --------------------------------------------------------
>
> Key: JBIDE-19853
> URL: https://issues.jboss.org/browse/JBIDE-19853
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: gtk2-new-app-wizard-1.png, gtk2-new-app-wizard-2.png, gtk3-new-app-wizard-1.png, gtk3-new-app-wizard-2.png, gtk3-quickstarts-cartridges.png
>
>
> When run in GTK3 the tree in the v2 application wizard is showing completely erroneous labels. The labels even switch content when the tree items are unfolded.
> When running Eclipse using (export SWT_GTK3=0) the tree in the application wizard looks in the following correct way:
> !gtk2-new-app-wizard-1.png!
> unfolding the "Basic Cartridges" produces the following:
> !gtk2-new-app-wizard-2.png!
> Without the above env variable, which makes Eclipse use GTK3, the application wizard looks as follows:
> !gtk3-new-app-wizard-1.png!
> ... and when unfolding "Basic Cartridges" the labels for the 3 main cathegories and all the children change to display the same:
> !gtk3-new-app-wizard-2.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-19853) GTK3 (only): Erroneous labels in application wizard tree
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19853?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-19853.
------------------------------------
Resolution: Done
Currently this issue is "fixed". Please create a new issue to remove the workaround from JBT 4.3.1 (not sure we should do it though if we want to support Mars.0). But we can remove the workaround from 4.4.0 (Neon).
> GTK3 (only): Erroneous labels in application wizard tree
> --------------------------------------------------------
>
> Key: JBIDE-19853
> URL: https://issues.jboss.org/browse/JBIDE-19853
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: gtk2-new-app-wizard-1.png, gtk2-new-app-wizard-2.png, gtk3-new-app-wizard-1.png, gtk3-new-app-wizard-2.png, gtk3-quickstarts-cartridges.png
>
>
> When run in GTK3 the tree in the v2 application wizard is showing completely erroneous labels. The labels even switch content when the tree items are unfolded.
> When running Eclipse using (export SWT_GTK3=0) the tree in the application wizard looks in the following correct way:
> !gtk2-new-app-wizard-1.png!
> unfolding the "Basic Cartridges" produces the following:
> !gtk2-new-app-wizard-2.png!
> Without the above env variable, which makes Eclipse use GTK3, the application wizard looks as follows:
> !gtk3-new-app-wizard-1.png!
> ... and when unfolding "Basic Cartridges" the labels for the 3 main cathegories and all the children change to display the same:
> !gtk3-new-app-wizard-2.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20672) Connector category title is random, when two categories have same ID
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20672?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20672:
------------------------------------
It's a twofold solution...
a) have different category/group ids between the "core" and "EA" listings (I added ".ea"), so that a connector can appear in one or the other.
b) use the SAME connector ids in both plugins, so that when EA is enabled, you get the EA version; when disabled, you get the core version.
As to preventing people from fatfingering in the future, the only thing that prevents it (currently) is looking in the Eclipse console log for warnings about dupe categories/connectors/groups.
> Connector category title is random, when two categories have same ID
> --------------------------------------------------------------------
>
> Key: JBIDE-20672
> URL: https://issues.jboss.org/browse/JBIDE-20672
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Environment: JBDS 9.0.0.CR1
> Reporter: Radim Hopp
> Assignee: Nick Boldt
> Fix For: 4.3.0.CR1
>
>
> Currently,in both central discovery jar and EA discovery jar, we have connector category with same ID, but different title (name).
> {noformat:title=com.jboss.jbds.central.discovery_9.0.0.CR1-v20150913-1206-B111.jar/plugin.xml}
> <connectorCategory
> description="JBoss Developer Studio Integration Stack Tools for use with individual JBoss projects (or products)."
> id="com.jboss.jbds.central.discovery.integration-stack.bundle"
> name="JBoss Developer Studio Integration Stack"
> relevance="90">
> <group id="com.jboss.jbds.central.discovery.integration-stack.bundle-fuse" />
> </connectorCategory>
> {noformat}
> {noformat:title=com.jboss.jbds.central.discovery.earlyaccess_9.0.0.CR1-v20150913-1206-B111.jar}
> <connectorCategory
> description="Early Access JBoss Developer Studio Integration Stack Tools for use with individual JBoss projects (or products)."
> id="com.jboss.jbds.central.discovery.integration-stack.bundle"
> name="JBoss Developer Studio Integration Stack Early Access"
> relevance="90">
> <group id="com.jboss.jbds.central.discovery.integration-stack.bundle-fuse" />
> {noformat}
> Expected behavior is:
> * EA is disabled - Title and description from com.jboss.jbds.central.discovery_9.0.0.CR1-v20150913-1206-B111.jar/plugin.xml is displayed.
> * EA is enabled - Title and description from com.jboss.jbds.central.discovery.earlyaccess_9.0.0.CR1-v20150913-1206-B111.jar is displayed
> Unfortunately, the title&description is shown completely by random.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBTIS-399) Cannot install Fuse/SwitchYard tooling in offline mode
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-399?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-399:
----------------------------------
I've got this in my Beta1f-SNAPSHOT JBTIS TP:
{code}
<!-- GEF, Draw2D -->
<unit id="org.eclipse.draw2d.feature.group" version="3.10.1.201508170204"/>
<unit id="org.eclipse.gef.feature.group" version="3.10.1.201508170204"/>
{code}
I wish I had a deterministic way to find out where this dependency gets puuled in.
> Cannot install Fuse/SwitchYard tooling in offline mode
> ------------------------------------------------------
>
> Key: JBTIS-399
> URL: https://issues.jboss.org/browse/JBTIS-399
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Critical
> Fix For: 9.0.0.Alpha1
>
> Attachments: error.txt, oi1.png, oi2.png, oi3.png
>
>
> Cannot install JBDS-IS 8.0.0.GA early access in offline mode. Note that DV tooling (Teiid Designer and ModeShape) can be installed without any problem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-18672) cannot run ionic tabs (the default) app with cordovasim
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18672?page=com.atlassian.jira.plugi... ]
Ilya Buziuk resolved JBIDE-18672.
---------------------------------
Resolution: Done
> cannot run ionic tabs (the default) app with cordovasim
> -------------------------------------------------------
>
> Key: JBIDE-18672
> URL: https://issues.jboss.org/browse/JBIDE-18672
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.2.0.Final
> Environment: Mac OS X, JavaFX
> Reporter: Max Rydahl Andersen
> Assignee: Ilya Buziuk
> Labels: upstream
> Fix For: 4.3.0.CR1
>
>
> run:
> ionic start ionic-demo
> import ionic-demo
> run as > cordova sim
> try use the app, click back.
> Two issues:
> 1) cordova sim complains about app.appexit not being supported
> 2) when trying to click do not show again I get the following in the cordovasim error log:
> Outstanding resource locks detected:
> ES2 Vram Pool: 51,815,392 used (19.3%), 51,815,392 managed (19.3%), 268,435,456 total
> 84 total resources being managed
> average resource age is 15.1 frames
> 0 resources at maximum supported age (0.0%)
> 16 resources marked permanent (19.0%)
> 17 resources have had mismatched locks (20.2%)
> 17 resources locked (20.2%)
> 30 resources contain interesting data (35.7%)
> 0 resources disappeared (0.0%)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months