migrating xml schema definitions from v2 to v3 ?
Cantor, Scott
cantor.2 at osu.edu
Thu Feb 28 10:19:08 EST 2013
On 2/27/13 10:16 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>I am leaning towards co-located, because these files provide a
>configuration reference hopefully useful to deployers.
That might also be the place to put any code we need to add related to
getting schema processing to work sanely (i.e. not relying on remote
lookups or schema location).
The downside I see is versioning of components, given the need to touch
two modules, but I think our intent was not to do individual versioning of
the modules within a parent project anyway?
-- Scott
More information about the dev
mailing list