[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=12929277#comment-12929277 ] 

Ondrej Zizka edited comment on WFLY-2426 at 12/6/13 1:02 PM:
-------------------------------------------------------------

Ok after some feedback, let's reconsider how to approach this.
Maybe version.txt is okay to be reused with different format. Would that bring anything?  << Jimmy
The format could be XML as well. But I'd not recommend ISO/IEC 19770-2 as that doesn't solve anything for our use case.
Maybe a POM format could be (mis)used with just G:A:V[:C]?
We could put the info into one file, not using the layer names for version-<layer_name>.<extension>  << Paul, Fernando

* Does the underlying software need to be identified? I.e. if it's SOA, should the file also say it's EAP for the tools which do not know SOA? << Max
* Should a timestamp be included? E.g. to differentiate between release candidates which all have ".GA"
* Is it okay to change the file for layered products? That could be error-prone. Or rather add another file << SOA Productization

Going to get some more feedback from Teams / people interested in this.
                
      was (Author: ozizka):
    Ok after some feedback, let's reconsider how to approach this.
Maybe version.txt is okay to be reused with different format. Would that bring anything?  << Jimmy
The format could be XML as well. But I'd not recommend ISO/IEC 19770-2 as that doesn't solve anything for our use case.
Maybe a POM format could be (mis)used with just G:A:V[:C]?
We could put the info into one file, not using the layer names for version-<layer_name>.<extension>  << Paul, Fernando

Going to get some more feedback from Teams / people interested in this.
                  
> 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