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

Tue Nov 5 08:31:02 EST 2013

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

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

By the way, I have an identification mechanism in WindRide - based on CRC32 comparison of jars. That came out of necessity to identify any version, since EAP 5, and also AS releases. Can be also applied to other servers, or generally any set of files. It also contains some kind of heuristics to deal with CP's and one-offs, and files replaced by user. The information is then carried in files within the WindRide project, as there was nothing to rely on in the scanned distributions.

Examples: https://github.com/OndraZizka/jboss-migration/tree/master/engine/src/main/resources/fileHashes/as5

Is this a viable alternative, or are you intending to add a spefic file?

> 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/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