<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Max, Rob,<br>
    <br>
    few questions for the requirements.<br>
    <ul>
      <li>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? E.g.<br>
      </li>
      <ul>
        <li>software.base = EAP</li>
        <li>software.layer = SOA</li>
        <li>software.name = JBoss SOA-Platform<br>
        </li>
      </ul>
      <li>Should a timestamp be included? E.g. to differentiate between
        release candidates which all have ".GA"</li>
      <li>Do you care about the format - as long it's well-known
        documented standard? I'm considering either .properties or .xml.
        ISO/IEC 19770-2 was suggested but that seems to be overkill and
        doesn't even match our needs.</li>
      <li>What everything do you expect to be in the file? SW
        identification and version but:</li>
      <ul>
        <li>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" ?<br>
        </li>
        <li>AS vs. EAP - do you need the boolean info whether it is a
          supported product?</li>
      </ul>
    </ul>
    <p>That's all for now,<br>
      looking forward to getting your reply.<br>
      Ondra<br>
    </p>
    <div class="moz-forward-container"><br>
      <br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>Re: [wildfly-dev] PR-5551/5552 - version-base.txt</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Fri, 06 Dec 2013 00:48:45 +0100</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>Ondrej Zizka <a class="moz-txt-link-rfc2396E" href="mailto:ozizka@redhat.com">&lt;ozizka@redhat.com&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
              <a class="moz-txt-link-rfc2396E" href="mailto:wildfly-dev@lists.jboss.org">&lt;wildfly-dev@lists.jboss.org&gt;</a>, Max Rydahl Andersen
              <a class="moz-txt-link-rfc2396E" href="mailto:manderse@redhat.com">&lt;manderse@redhat.com&gt;</a>, Rob Stryker
              <a class="moz-txt-link-rfc2396E" href="mailto:rstryker@redhat.com">&lt;rstryker@redhat.com&gt;</a>, Paul Gier
              <a class="moz-txt-link-rfc2396E" href="mailto:pgier@redhat.com">&lt;pgier@redhat.com&gt;</a>, Knutsen, Aslak
              <a class="moz-txt-link-rfc2396E" href="mailto:aknutsen@redhat.com">&lt;aknutsen@redhat.com&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>Added Paul Gier and Aslak to CC - could you guys please share your opinions.
Let's discuss this before we get to some code freeze and it's late / no 
time to solve this.

Is the arrangement (described in the jira comments) a viable way to 
statically identify (without launching) a server / product / layers added?

Thanks,
Ondra


On 2.12.2013 13:12, Ondrej Zizka wrote:
&gt; Hi all,
&gt;
&gt; there's a request for something for static identification of the server
&gt; in a directory. This comes from JBDS and prehaps other tools (installer,
&gt; upgrader, ...)
&gt; The jira is <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/WFLY-2426">https://issues.jboss.org/browse/WFLY-2426</a>
&gt;
&gt; The discussion on that jira staled, so I created these
&gt; <a class="moz-txt-link-freetext" href="https://github.com/wildfly/wildfly/pull/5551">https://github.com/wildfly/wildfly/pull/5551</a>
&gt; <a class="moz-txt-link-freetext" href="https://github.com/wildfly/wildfly/pull/5552">https://github.com/wildfly/wildfly/pull/5552</a>
&gt; (It's the same thing done in 2 ways.)
&gt;
&gt; I suggest to keep the discussion in that jira WFLY-2426 .
&gt; Is this solution (as described there) acceptable? Even for layered
&gt; stuff? Max + Rob in the CC.
&gt;
&gt; Thanks,
&gt; Ondra
&gt;
&gt;
&gt; _______________________________________________
&gt; wildfly-dev mailing list
&gt; <a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
&gt; <a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a>

_______________________________________________
wildfly-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a>
</pre>
      <br>
    </div>
    <br>
  </body>
</html>