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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on WFLY-2426:
-----------------------------------

How would this change for distributions that have 1 base and multiple layers installed on it?  I've lost the link to the community page with the matrix, but it's my understanding that distributions aren't limited to one layer and that some may have multiple layers. 

Would this file then be updated somehow (and how?) if a distribution contained 1 layer but was upgraded to have a second layer? 

Is the layer tag assuming that there's only 1 layer, or only 1 primary layer? Is it possible that there might be multiple layers without any one being "in charge"? If that's possible, then it seems a mistake to assume only 1 layer. 
                
> 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