hammett wrote:
- Original Message -
From: "Stephen McConnell" <[EMAIL PROTECTED]>
Rather than move the builder content (and by inference - tools and
plugin) to Merlin, it would make more sense to add a migration tool to
the Fortress package to ensure that meta-info is represented in a co
- Original Message -
From: "Stephen McConnell" <[EMAIL PROTECTED]>
> Rather than move the builder content (and by inference - tools and
> plugin) to Merlin, it would make more sense to add a migration tool to
> the Fortress package to ensure that meta-info is represented in a common
> way
hammett wrote:
- Original Message -
From: "Leo Simons" <[EMAIL PROTECTED]>
<...>
It may be not a standard yet, but lets be practical: how to make it
standard?
My suggestion:
- The current builder package (in impl) should move to Merlin.
The builder package contains the implementation of
- Original Message -
From: "Leo Simons" <[EMAIL PROTECTED]>
<...>
It may be not a standard yet, but lets be practical: how to make it
standard?
My suggestion:
- The current builder package (in impl) should move to Merlin.
- Fortress should implement its own Builder based on what is actu
Leo Simons wrote:
Stephen McConnell wrote:
Leo Simons wrote:
given the decreased likelyhood of the Avalon-Meta package being in
broad use across different containers, I suggest we stop referring to
it as "standard", because its not.
-1
you can't veto a suggestion dude!
But I can type the c
