July 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-743) [GTK3.24] Compare editor button has no image [EBZ#549117]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-743?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-743: --------------------------------- Sprint: devex #170 Aug 2019 Assignee: Eric Williams > [GTK3.24] Compare editor button has no image [EBZ#549117] > --------------------------------------------------------- > > Key: ERT-743 > URL: https://issues.jboss.org/browse/ERT-743 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: 4.13_M3, SWT, bzira > > Running Eclipse (any recent version newer than 4.8) on GTK > 3.24.4 has a missing icon in the compare editor "copy changes" button. > The bug is a result of this GTK patch: https://gitlab.gnome.org/GNOME/gtk/commit/d82edf0c915d103d3426008618d6c54... > GTK versions <= 3.24.4 are unaffected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26715) Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M1

by stephane bouchet (Jira)

[ https://issues.jboss.org/browse/JBIDE-26715?page=com.atlassian.jira.plugi... ] stephane bouchet updated JBIDE-26715: ------------------------------------- Attachment: (was: p2diff_log_jbosstools_2019-07-29_14-12.txt) > Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M1 > ---------------------------------------------------------------------- > > Key: JBIDE-26715 > URL: https://issues.jboss.org/browse/JBIDE-26715 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.12.0.Final > Reporter: Jeff MAURY > Assignee: stephane bouchet > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26715) Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M1

by stephane bouchet (Jira)

[ https://issues.jboss.org/browse/JBIDE-26715?page=com.atlassian.jira.plugi... ] stephane bouchet updated JBIDE-26715: ------------------------------------- Attachment: p2diff_log_jbosstools_2019-07-29_14-12.txt > Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M1 > ---------------------------------------------------------------------- > > Key: JBIDE-26715 > URL: https://issues.jboss.org/browse/JBIDE-26715 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.12.0.Final > Reporter: Jeff MAURY > Assignee: stephane bouchet > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: p2diff_log_jbosstools_2019-07-29_14-12.txt > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26751) Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26751?page=com.atlassian.jira.plugi... ] Zbyněk Červinka commented on JBIDE-26751: ----------------------------------------- [~odockal] *Red Hat CodeReady Studio* Version: 12.13.0.AM1 Build id: AM1-v20190720-1320-B4681 Build date: 20190720-1320 > Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file > -------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26751 > URL: https://issues.jboss.org/browse/JBIDE-26751 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Environment: OS X 10.14.6 > Reporter: Zbyněk Červinka > Priority: Major > Attachments: example_of_context_menu_which_is_present.png, missing_context_menu.png > > > When running the BeansXMLCompletionTestCDI20.class, the Content Assist item in the Edit menu is being checked. See the "missing_context_menu.png" image in the attachment to see the situation and the missing Content Assist item in the Edit menu. Then see the "example_of_context_menu_which_is_present.png" - here is captured the situation where the Content Assist item is present. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26751) Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26751?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-26751: --------------------------------------- [~zcervink] What version of codereadystudio was this reproduced on? > Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file > -------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26751 > URL: https://issues.jboss.org/browse/JBIDE-26751 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Environment: OS X 10.14.6 > Reporter: Zbyněk Červinka > Priority: Major > Attachments: example_of_context_menu_which_is_present.png, missing_context_menu.png > > > When running the BeansXMLCompletionTestCDI20.class, the Content Assist item in the Edit menu is being checked. See the "missing_context_menu.png" image in the attachment to see the situation and the missing Content Assist item in the Edit menu. Then see the "example_of_context_menu_which_is_present.png" - here is captured the situation where the Content Assist item is present. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing

by nimo stephan (Jira)

[ https://issues.jboss.org/browse/JBIDE-26740?page=com.atlassian.jira.plugi... ] nimo stephan edited comment on JBIDE-26740 at 7/26/19 6:20 PM: --------------------------------------------------------------- Could you make a FR (Feature Request) at the WTP level, as you are better involved in this and know what has to be changed. It makes sense that "Every change in deployment should trigger a wildfly restart automatically."..especially while developing. Having an option for this would be good. Doing the restart manually is awkward.. was (Author: nimo22): Could you make a FR (Feature Request) at the WTP level, as you are better involved in this and know what has to be changed. It makes sense that "Every change in deployment should trigger a wildfly restart automatically." Having an option for this would be good. Doing the restart manually is awkward.. > add option to Wildfly-Overview to "auto-restart" after publishing > ----------------------------------------------------------------- > > Key: JBIDE-26740 > URL: https://issues.jboss.org/browse/JBIDE-26740 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.12.0.Final > Reporter: nimo stephan > Priority: Critical > > Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published. > Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing

by nimo stephan (Jira)

[ https://issues.jboss.org/browse/JBIDE-26740?page=com.atlassian.jira.plugi... ] nimo stephan commented on JBIDE-26740: -------------------------------------- Could you make a FR (Feature Request) at the WTP level, as you are better involved in this and know what has to be changed. It makes sense that "Every change in deployment should trigger a wildfly restart automatically." Having an option for this would be good. Doing the restart manually is awkward.. > add option to Wildfly-Overview to "auto-restart" after publishing > ----------------------------------------------------------------- > > Key: JBIDE-26740 > URL: https://issues.jboss.org/browse/JBIDE-26740 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.12.0.Final > Reporter: nimo stephan > Priority: Critical > > Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published. > Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26741) WEB_INF/lib is not transmitted after full publishing

by nimo stephan (Jira)

[ https://issues.jboss.org/browse/JBIDE-26741?page=com.atlassian.jira.plugi... ] nimo stephan edited comment on JBIDE-26741 at 7/26/19 6:10 PM: --------------------------------------------------------------- +1.First, what type of project are you using?+ It's a maven project from a maven archetype (weld-jee). +2. Do you have m2e-wtp installed?+ yes, along with actual "eclipse jee" and actual "jboss tools" I click on "publish to server" and the exloded war is deployed but not its lib-folder. +3. If you're using a standard "Dynamic Web Project"+ No. It's a typical maven project (wildfly-jee-archetype), nothing special. was (Author: nimo22): +1.First, what type of project are you using?+ It's a maven project from a maven archetype (weld-jee). +2. Do you have m2e-wtp installed?+ yes, along with actual "eclipse jee" and actual "jboss tools" I click on "publish to server" and it's all the exloded war is deployed but not the lib-folder. +3. If you're using a standard "Dynamic Web Project"+ No. It's a typical maven project (wildfly-jee-archetype), nothing special. > WEB_INF/lib is not transmitted after full publishing > ---------------------------------------------------- > > Key: JBIDE-26741 > URL: https://issues.jboss.org/browse/JBIDE-26741 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.12.0.Final > Reporter: nimo stephan > Priority: Major > > I am using > Eclipse IDE for Enterprise Java Developers. > Version: 2019-06 (4.12.0) > with actual Jboss Tools. > > When publising war archives > to "Wildfly 17 Server" with *"Full Publish"* (or "Incremental Publish"), > the *WEB_INF/lib* folder is *not* transferred. > I guess, it s a bug.. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26741) WEB_INF/lib is not transmitted after full publishing

by nimo stephan (Jira)

[ https://issues.jboss.org/browse/JBIDE-26741?page=com.atlassian.jira.plugi... ] nimo stephan commented on JBIDE-26741: -------------------------------------- +1.First, what type of project are you using?+ It's a maven project from a maven archetype (weld-jee). +2. Do you have m2e-wtp installed?+ yes, along with actual "eclipse jee" and actual "jboss tools" I click on "publish to server" and it's all the exloded war is deployed but not the lib-folder. +3. If you're using a standard "Dynamic Web Project"+ No. It's a typical maven project (wildfly-jee-archetype), nothing special. > WEB_INF/lib is not transmitted after full publishing > ---------------------------------------------------- > > Key: JBIDE-26741 > URL: https://issues.jboss.org/browse/JBIDE-26741 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.12.0.Final > Reporter: nimo stephan > Priority: Major > > I am using > Eclipse IDE for Enterprise Java Developers. > Version: 2019-06 (4.12.0) > with actual Jboss Tools. > > When publising war archives > to "Wildfly 17 Server" with *"Full Publish"* (or "Incremental Publish"), > the *WEB_INF/lib* folder is *not* transferred. > I guess, it s a bug.. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing

by Robert Stryker (Jira)

[ https://issues.jboss.org/browse/JBIDE-26740?page=com.atlassian.jira.plugi... ] Robert Stryker commented on JBIDE-26740: ---------------------------------------- Unfortunately, JBoss Tools has no ability to modify the "Publishing" section of the editor. It is automatically added by WTP webtools. A feature request like this would need to be made at the WTP level. > add option to Wildfly-Overview to "auto-restart" after publishing > ----------------------------------------------------------------- > > Key: JBIDE-26740 > URL: https://issues.jboss.org/browse/JBIDE-26740 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.12.0.Final > Reporter: nimo stephan > Priority: Critical > > Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published. > Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 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 July 2019