[
https://issues.jboss.org/browse/WFLY-2426?page=com.atlassian.jira.plugin....
]
Ondrej Zizka edited comment on WFLY-2426 at 11/6/13 1:51 PM:
-------------------------------------------------------------
Talked to Paul. EAP already has such file, version.txt, but FWIU it is not a
documented/guaranteed format. Support reportedly relies on that (Jimmy).
See JBPAPP6-1044 .
Also, there is a file which is basically what we need,
see
https://github.com/jbossas/jboss-eap/commit/b8f636d9a765fcfe67cf0a8e2ff28...
resp.
https://github.com/jbossas/jboss-eap/blob/b8f636d9a765fcfe67cf0a8e2ff2804...
{code}
JBoss-Product-Release-Name: EAP
JBoss-Product-Release-Version: 6.2.0.GA
JBoss-Product-Console-Slot: eap
{code}
Besides the key names say product, this could be what we need. Just to move it to the root
or bin/. Any other information needed? I was thinking about a field saying
product/project, if useful.
was (Author: ozizka):
Talked to Paul. EAP already has such file, version.txt, but FWIU it is not a
documented/guaranteed format. Support reportedly relies on that (Jimmy).
Also, there is a file which is basically what we need,
see
https://github.com/jbossas/jboss-eap/commit/b8f636d9a765fcfe67cf0a8e2ff28...
resp.
https://github.com/jbossas/jboss-eap/blob/b8f636d9a765fcfe67cf0a8e2ff2804...
{code}
JBoss-Product-Release-Name: EAP
JBoss-Product-Release-Version: 6.2.0.GA
JBoss-Product-Console-Slot: eap
{code}
Besides the key names say product, this could be what we need. Just to move it to the root
or bin/. Any other information needed? I was thinking about a field saying
product/project, if useful.
Easily accessible static information describing the release
-----------------------------------------------------------
Key: WFLY-2426
URL:
https://issues.jboss.org/browse/WFLY-2426
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Server
Reporter: Brian Stansberry
Tools that work with a WF installation need to identify what they are working with before
they can launch or interact with the server. Specifically, they need to know the version.
They likely need to know other information as well, such as the name of the software; e.g.
whether it is WildFly itself or some other project based on WildFly.
This information should be provided in standard format in a text file in a standard
location in the distribution (probably in bin). The text file should be generated as part
of the build.
The solution to this issue should consider the requirements of other
"identities" that may be based on WildFly. See [1] for the definition of an
identity.
The solution to this issue should consider the needs of products based on WildFly and
other non-product identities. For example, can the existing product.conf contain the
necessary information for a product, with some differently named but largely equivalent
file being used in a non-product distribution?
The solution to this issue should consider the implications for the patching tool.
[1]
https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganiz... for
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira