[jboss-jira] [JBoss JIRA] (WFLY-2426) Easily accessible static information describing the release

[Ondrej Zizka (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929690#comment-12929690 ] 

Ondrej Zizka commented on WFLY-2426:
------------------------------------

My favorite option would be having file-per-layer in the root dir but the product.conf & layers.conf could do the job too, as Brian mentioned.
Talked to Rob about the requirements from JBDS side, which are:

   1) Some way to discover the base, and the base's version / name information
   2) Some way to discover the layers, and the name/version information for each layer (the layers as a secondary issue)
   3)  the entire distribution  name / version, like product = JPP 6.1 (based on eap 6.2  with layers x,y,z)

Requested input about product.conf & layers.conf.
                
> 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
>            Assignee: Ondrej Zizka
>              Labels: build, integration, jbds, layers, version
>             Fix For: 8.0.0.CR1
>
>
> 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/LayeredDistributionsAndModulePathOrganization 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