[ https://issues.jboss.org/browse/WFLY-2426?page=com.atlassian.jira.plugin.... ] Ondrej Zizka edited comment on WFLY-2426 at 12/6/13 1:32 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 {code} software.base = EAP software.layer = SOA software.name = JBoss SOA-Platform {code} * 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 * ID vs. name - do you want just "eap" or do you expect to have something to present to the user directly, i.e. some "JBoss Enterprise Application Platform" ? * AS vs. EAP - do you need the boolean info whether it is a supported product? 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 * 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 * ID vs. name - do you want just "eap" or do you expect to have something to present to the user directly, i.e. some "JBoss Enterprise Application Platform" ? * AS vs. EAP - do you need the boolean info whether it is a supported product? Going to get some more feedback from Teams / people interested in this. -- 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