July 2019 - jbosstools-issues - Jboss List Archives

[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, 8 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, 8 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, 8 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, 8 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, 8 months

1
0
0 / 0

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

by Robert Stryker (Jira)

[ https://issues.jboss.org/browse/JBIDE-26741?page=com.atlassian.jira.plugi... ] Robert Stryker commented on JBIDE-26741: ---------------------------------------- I think we're going to need more information here on your project structure and what exactly you are publishing. First, what type of project are you using? Is it a wtp-style faceted project? Or is it a maven project? Do you have m2e-wtp installed? Or are you trying to publish a completed .war file by right-clicking it and using the "make deployable" action? If you're using a standard "Dynamic Web Project", is this issue replicatable with a small simple example project? Can you attach such a project or provide a set of instructions to replicate the issue? A lot of WTP logic depends on the exact structure of the project, so replicating it can be hard without knowing exactly what you're doing. =/ > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24963) Create CDI 2 integration tests

by Zbyněk Červinka (Jira)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26749) New Launcher Application Project Wizard shows error while opening the wizard window (An internal error occurred during: "Loading launcher catalog". java.lang.NullPointerException)

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26749?page=com.atlassian.jira.plugi... ] Zbyněk Červinka commented on JBIDE-26749: ----------------------------------------- I have update on this issue - issue is now fixed. After some testing today the issue has disappeared os OS X 10.14.6 (CodeReady Studio: 12.13.0.AM1-v20190720-1320-B4681-installer-standalone). > New Launcher Application Project Wizard shows error while opening the wizard window (An internal error occurred during: "Loading launcher catalog". java.lang.NullPointerException) > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26749 > URL: https://issues.jboss.org/browse/JBIDE-26749 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.13.x > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Attachments: error.png > > > New Launcher Application Project Wizard shows error while opening the wizard window. > *Error description:* > {color:red}An internal error occurred during: "Loading launcher catalog". > java.lang.NullPointerException{color} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26745) Content.xml not found trying to install from Eclipse marketplace

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26745?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26745: ------------------------------- Fix Version/s: LATER > Content.xml not found trying to install from Eclipse marketplace > ---------------------------------------------------------------- > > Key: JBIDE-26745 > URL: https://issues.jboss.org/browse/JBIDE-26745 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Environment: Eclipse IDE for Enterprise Java Developers. > Version: 2019-06 (4.12.0) > Build id: 20190614-1200 > JBoss AS, WildFly & EAP Server Tools / Remote Systems Integration > > Version: 3.6.2.v20190304-1841 > > (c) Copyright (c) Red Hat, Inc., contributors and others 2004 - 2012. All rights reserved. > Visit http://jboss.org/tools > Reporter: Ariel Barboza > Priority: Major > Fix For: LATER > > Attachments: ErrorLog.PNG, ErrorLog1.PNG, screenshot-1.png, screenshot-2.png, screenshot-3.png > > > When installing Eclipse, when trying to add JBoss tools plug in to add Wildfly server, it gives an installation error, saying a file "Content.xml" does not exist. Verified it was not a proxy issue, went to the directory error mentions and it is not found -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26743) Job jbosstools-install-p2director.install-tests.matrix_master is red for JBossTools

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26743?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26743: ------------------------------- Fix Version/s: 4.13.0.AM1 > Job jbosstools-install-p2director.install-tests.matrix_master is red for JBossTools > ----------------------------------------------------------------------------------- > > Key: JBIDE-26743 > URL: https://issues.jboss.org/browse/JBIDE-26743 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.13.0.AM1 > Reporter: Josef Kopriva > Priority: Major > Fix For: 4.13.0.AM1 > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... is failing for jbosstools, but for CRS is green. > Error: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > {code:java} > [ERROR] INSTALL FAILED > 20:27:40 > 20:27:40 [p2.dir] !ENTRY org.eclipse.equinox.p2.director 4 10054 2019-07-11 14:27:38.048 > 20:27:40 [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency. > 20:27:40 [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2019-07-11 14:27:38.048 > 20:27:40 [p2.dir] !MESSAGE Software being installed: Mylyn Versions Connector: Git 1.17.0.v20180628-1737 (org.eclipse.mylyn.git.feature.group 1.17.0.v20180628-1737) > 20:27:40 -- > 20:27:40 [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2019-07-11 14:27:38.048 > 20:27:40 [p2.dir] !MESSAGE Only one of the following can be installed at once: > 20:27:40 [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2019-07-11 14:27:38.048 > 20:27:40 [p2.dir] !MESSAGE Mylyn Git Connector UI 1.16.0.v20170629-1738 (org.eclipse.mylyn.git.ui 1.16.0.v20170629-1738) > 20:27:40 -- > 20:27:40 [p2.dir] !MESSAGE To: org.eclipse.equinox.p2.iu; org.eclipse.mylyn.git.ui [1.17.0.v20180628-1737,1.17.0.v20180628-1737] > 20:27:40 [p2.dir] Cannot complete the install because of a conflicting dependency. > 20:27:40 [p2.dir] Software being installed: Mylyn Versions Connector: Git 1.17.0.v20180628-1737 (org.eclipse.mylyn.git.feature.group 1.17.0.v20180628-1737) > 20:27:40 [p2.dir] Software currently installed: Mylyn Versions Connector: Git 1.16.0.v20170629-1738 (org.eclipse.mylyn.git.feature.group 1.16.0.v20170629-1738) > 20:27:40 [p2.dir] Only one of the following can be installed at once: > 20:27:40 [p2.dir] Mylyn Git Connector UI 1.16.0.v20170629-1738 (org.eclipse.mylyn.git.ui 1.16.0.v20170629-1738) > 20:27:40 [p2.dir] Mylyn Git Connector UI 1.17.0.v20180628-1737 (org.eclipse.mylyn.git.ui 1.17.0.v20180628-1737) > 20:27:40 -- > 20:27:40 at org.eclipse.equinox.launcher.Main.main(Main.java:1441) > 20:27:40 Caused by: /mnt/hudson_workspace/workspace/jbosstools-install-p2director.install-tests.matrix_master/92a2a6fc/director.xml:62: exec returned: 13 > 20:27:40 at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:645) > 20:27:40 at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:669) > 20:27:40 -- > 20:27:40 Root exception: > 20:27:40 /mnt/hudson_workspace/workspace/jbosstools-install-p2director.install-tests.matrix_master/92a2a6fc/director.xml:62: exec returned: 13 > 20:27:40 at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:645) > 20:27:40 at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:669) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 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