]
Jean-Francois Denise closed WFCORE-1738.
----------------------------------------
Resolution: Won't Do
The way to go is for the CLI users to take into account the content of headers. The header
says that the server should be restarted. This is what a user should do prior to make
requests to the server.
I think that this issue can be closed. Feel free to re-open.
JF
Hint when versions are out-of-date pending restart
--------------------------------------------------
Key: WFCORE-1738
URL:
https://issues.jboss.org/browse/WFCORE-1738
Project: WildFly Core
Issue Type: Feature Request
Components: CLI, Patching
Reporter: Marek Kopecký
Assignee: Jean-Francois Denise
Priority: Optional
I have a minor usability suggestion. It's merely informational but I think helpful.
When I was in the CLI tool to apply a version update patch (7.0.0 -> 7.0.1), I
wasn't yet aware that I needed to restart the server for it to take effect. So when I
afterward typed "version" to confirm the expected version bumps... well, they
did not. I was specifically looking to confirm a change in both fields "JBoss AS
release" and "JBoss AS product". With that said, it would be useful to add
something to the output indicating the information being displayed will no longer be
true.
Illustrated example. Notice the asterisks:
{code}
JBOSS_HOME: C:\dev\jboss-eap-7
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"(*)
JBoss AS product: JBoss EAP 7.0.0.GA(*)
JAVA_HOME: c:\java\jdk1.8.0_45
java.version: 1.8.0_45
java.vm.vendor: Oracle Corporation
java.vm.version: 25.45-b02
os.name: Windows 7
os.version: 6.1
(*) Versions subject to change after patch takes effect at restart.
{code}