June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19853) GTK3 (only): Erroneous labels in application wizard tree

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19853?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19853: ------------------------------------------ [~snjeza] awesome, it works, thanks! > 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 > > > 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.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19853) GTK3 (only): Erroneous labels in application wizard tree

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19853?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19853: ------------------------------------------ merged and pushed to upstream/master > 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 > > > 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.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19907) Default options to start a Docker container

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19907?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19907: ----------------------------------- Component/s: docker > Default options to start a Docker container > ------------------------------------------- > > Key: JBIDE-19907 > URL: https://issues.jboss.org/browse/JBIDE-19907 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Reporter: Arun Gupta > > Starting a Docker container from Docker Images tab does not have stdin, stdout, stderr attached. Also, TTY is not assigned. > These mimic "-it" options on CLI and are commonly used for interactively running a container. This should be the default in this tooling as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19906) Disabled Finish button for Create Container

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19906?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19906: ----------------------------------- Component/s: docker > Disabled Finish button for Create Container > ------------------------------------------- > > Key: JBIDE-19906 > URL: https://issues.jboss.org/browse/JBIDE-19906 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Reporter: Arun Gupta > Attachments: Screen Shot 2015-06-02 at 10.46.11 PM.png > > > Using JBDS 9.0 nightly + Docker Tooling plugins. > In Docker Images view, select jboss/wildfly:latest image, click on "Create Container" shows the wizard but the Finish button is disabled. > This is because Memory, Memory Swap, Cpu Shares are initialized as 0. Finish button is enabled after 0 value is removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-650) Add the info in the Community docs

by Supriya Bharadwaj (JIRA)

Supriya Bharadwaj created TOOLSDOC-650: ------------------------------------------ Summary: Add the info in the Community docs Key: TOOLSDOC-650 URL: https://issues.jboss.org/browse/TOOLSDOC-650 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Sub-task Reporter: Supriya Bharadwaj Assignee: Misha Ali Priority: Minor Please add the info in the community versions of the documents -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19641: --------------------------------------- [~rob.stryker], so it seems your jars are from EAP 6.1.0.Beta. Last time I tried it (and it failed) I was deploying the big war to EAP 6.4 from JBDS 8.1. So I tried the following: 1. Export big war in JBDS 8.1 2. Start EAP 6.4 3. Deploy big war using jboss-cli from EAP 6.4 - all OK 4. Undeploy 5. Deploy big war using jboss-cli from EAP 6.1 Beta - all OK By "all OK" I mean the deploy command was finished, the server log said the war is deployed and I even tried to download the included big file (JBDS installer) from the browser and it worked (and md5 matched). I was kind of hoping it would fail with the older jboss-cli :-\ > Big war deployment via management API gets stuck > ------------------------------------------------ > > Key: JBIDE-19641 > URL: https://issues.jboss.org/browse/JBIDE-19641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log > > > When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through. > This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18772: ---------------------------------------- [~nickboldt]: I see that for aggregates, we don't rely any more on JOB_NAME to publish, but rather on internal Maven properties. That's IMO a great change! > Include publish steps in pom files > ---------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19907) Default options to start a Docker container

by Arun Gupta (JIRA)

Arun Gupta created JBIDE-19907: ---------------------------------- Summary: Default options to start a Docker container Key: JBIDE-19907 URL: https://issues.jboss.org/browse/JBIDE-19907 Project: Tools (JBoss Tools) Issue Type: Enhancement Reporter: Arun Gupta Starting a Docker container from Docker Images tab does not have stdin, stdout, stderr attached. Also, TTY is not assigned. These mimic "-it" options on CLI and are commonly used for interactively running a container. This should be the default in this tooling as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19906) Disabled Finish button for Create Container

by Arun Gupta (JIRA)

Arun Gupta created JBIDE-19906: ---------------------------------- Summary: Disabled Finish button for Create Container Key: JBIDE-19906 URL: https://issues.jboss.org/browse/JBIDE-19906 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Arun Gupta Attachments: Screen Shot 2015-06-02 at 10.46.11 PM.png Using JBDS 9.0 nightly + Docker Tooling plugins. In Docker Images view, select jboss/wildfly:latest image, click on "Create Container" shows the wizard but the Finish button is disabled. This is because Memory, Memory Swap, Cpu Shares are initialized as 0. Finish button is enabled after 0 value is removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19906) Disabled Finish button for Create Container

by Arun Gupta (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19906?page=com.atlassian.jira.plugi... ] Arun Gupta updated JBIDE-19906: ------------------------------- Attachment: Screen Shot 2015-06-02 at 10.46.11 PM.png Disabled Finish button with default values. > Disabled Finish button for Create Container > ------------------------------------------- > > Key: JBIDE-19906 > URL: https://issues.jboss.org/browse/JBIDE-19906 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Arun Gupta > Attachments: Screen Shot 2015-06-02 at 10.46.11 PM.png > > > Using JBDS 9.0 nightly + Docker Tooling plugins. > In Docker Images view, select jboss/wildfly:latest image, click on "Create Container" shows the wizard but the Finish button is disabled. > This is because Memory, Memory Swap, Cpu Shares are initialized as 0. Finish button is enabled after 0 value is removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2015