[JBoss JIRA] (JBIDE-26741) WEB_INF/lib is not transmitted after full publishing
by nimo stephan (Jira)
nimo stephan created JBIDE-26741:
------------------------------------
Summary: 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
I am using
Eclipse IDE for Enterprise Java Developers.
Version: 2019-06 (4.12.0)
with actual Jboss Tools.
When publising war archives
to Jboss Wildfly 17 Server with "Full Publish",
then 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
[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 updated JBIDE-26740:
---------------------------------
Description:
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.
was:
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.
> 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
[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 updated JBIDE-26740:
---------------------------------
Description:
Actually, with *Jboss Tools* 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.
was:
Actually, 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.
> 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* 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
[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 updated JBIDE-26740:
---------------------------------
Description:
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.
was:
Actually, with *Jboss Tools* 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.
> 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
[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 updated JBIDE-26740:
---------------------------------
Description:
Actually, we can change to automatically *publish* to Wildfly after resource 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.
was:
Actually, we can change to automatically *publishing* to Wildfly after resource 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.
> 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, we can change to automatically *publish* to Wildfly after resource 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
[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 updated JBIDE-26740:
---------------------------------
Description:
Actually, we can change to automatically *publish* to Wildfly-Server after resource 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.
was:
Actually, we can change to automatically *publish* to Wildfly after resource 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.
> 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, we can change to automatically *publish* to Wildfly-Server after resource 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
[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 updated JBIDE-26740:
---------------------------------
Description:
Actually, 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.
was:
Actually, we can change to automatically *publish* to Wildfly-Server after resource 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.
> 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, 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
[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing
by nimo stephan (Jira)
nimo stephan created JBIDE-26740:
------------------------------------
Summary: 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
Actually, we can change the to automatically *publishing* to Wildfly after resource 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
[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 updated JBIDE-26740:
---------------------------------
Description:
Actually, we can change to automatically *publishing* to Wildfly after resource 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.
was:
Actually, we can change the to automatically *publishing* to Wildfly after resource 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.
> 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, we can change to automatically *publishing* to Wildfly after resource 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
[JBoss JIRA] (JBIDE-26694) Server adapter: should be able to freely set a war name
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26694 at 7/15/19 5:30 AM:
-------------------------------------------------------------------
The OpenShift server adapter now has a 2nd page "Deployment" in the server editor. It shows the deployed project. By double clicking into the "Deployment Location" column, one can edit the value and change the name of the war:
!deployment-page-edit-war-name.png!
# EXEC: double click your server in the "Servers" view
# ASSERT: server adapter editor opens up
# EXEC: switch editor page to "Deployment"
# EXEC: click into the cell in the column "Deployment Location" and change the value to what fits your need.
# EXEC: save editor
Result:
Server adapter re-deploys to OpenShift using the new war name.
was (Author: adietish):
The OpenShift server adapter now has a 2nd page "Deployment" in the server editor. It shows the deployed project. By double clicking into the "Deployment Location" column, one can edit the value and change the name of the war:
!deployment-page-edit-war-name.png!
# EXEC: double click your server in the "Servers" view
# ASSERT: server adapter editor opens up
# EXEC: switch editor page to "Deployment"
# EXEC: click into the cell in the column "Deployment Location" and change the value to what fits your need.
# EXEC: save editor
Result:
Server adapter re-deploys to OpenShift using the new war name.
> Server adapter: should be able to freely set a war name
> -------------------------------------------------------
>
> Key: JBIDE-26694
> URL: https://issues.jboss.org/browse/JBIDE-26694
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: server_adapter
> Fix For: 4.13.0.AM1
>
> Attachments: console-output-1.png, console-output-2.png, deployment-page-edit-war-name.png, server-adapter-configuration.png, switch-location.png
>
>
> For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
> Steps:
> # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
> # ASSERT: *websocket-chat* application is imported into your workspace
> # ASSERT: server adapter *jboss-webserver31-tomcat* is created
> # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
> # EXEC: start the server adapter
> # ASSERT: RSync is executed and the output is visible in the "Console"
> Result:
> If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
> !console-output-1.png!
> Expected result:
> I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
> Currently, to achieve this I have to do the following:
> # EXEC: create the following xml snippet (notice the *outputName* property for the module)
> and make sure it reads as follows:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <deployment>
> <local>
> <module id="org.eclipse.jst.jee.server:websocket-chat">
> <property key="tempLocation" value="" />
> <property key="location" value="" />
> <property key="outputName" value="ROOT" />
> </module>
> </local>
> </deployment>
> {code}
> # EXEC: html-encode, join it into a single line and copy it (into the clipboard)
> # EXEC: open the properties for the server adapter and hit "Switch Location"
> !switch-location.png!
> # ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
> !server-adapter-configuration.png!
> # EXEC: open the file with the *XML Editor*
> # EXEC: in your *XML Editor*: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
> <list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
> </server>
> {code}
> # EXEC: Save the editor and restart the server
> Result:
> Syncing now happens into a folder *ROOT*
> !console-output-2.png!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months