That's all for now,
looking forward to getting your reply.
|Subject:||Re: [wildfly-dev] PR-5551/5552 - version-base.txt|
|Date:||Fri, 06 Dec 2013 00:48:45 +0100|
|From:||Ondrej Zizka <email@example.com>|
|To:||firstname.lastname@example.org <email@example.com>, Max Rydahl Andersen <firstname.lastname@example.org>, Rob Stryker <email@example.com>, Paul Gier <firstname.lastname@example.org>, Knutsen, Aslak <email@example.com>|
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: > Hi all, > > there's a request for something for static identification of the server > in a directory. This comes from JBDS and prehaps other tools (installer, > upgrader, ...) > The jira is https://issues.jboss.org/browse/WFLY-2426 > > The discussion on that jira staled, so I created these > https://github.com/wildfly/wildfly/pull/5551 > https://github.com/wildfly/wildfly/pull/5552 > (It's the same thing done in 2 ways.) > > I suggest to keep the discussion in that jira WFLY-2426 . > Is this solution (as described there) acceptable? Even for layered > stuff? Max + Rob in the CC. > > Thanks, > Ondra > > > _______________________________________________ > wildfly-dev mailing list > firstname.lastname@example.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev _______________________________________________ wildfly-dev mailing list email@example.com https://lists.jboss.org/mailman/listinfo/wildfly-dev